|
Web Service
Micro-Kernel Architecture ™ |
||||||||||||||||||||
|
|
||||||||||||||||||||
|
The Web Service Micro-Kernel Architecture ™ or WSMKA ™ is a generic architecture allowing the dynamic loading of web services. Based on our abstract management class, a web service can be 'hot deployed' (deploying a web service without restarting the web site or web server) as services are developed or improved. Utilizing XML, XSLT, WSDL, and 'reflection' or 'introspection', we are able to create a standard approach to development of these services. Utilizing our product library, atiFactory ™ and ormGen ™, development of these web services and their utilization is thus standardized. This allows for consistent development among development teams and reduces TTM (time to market). Using state of the art technologies and following the UML approach, we have achieved a robust architecture, secure, scalable, and extendable. The WSMKA ™ architecture is diagramed below. From the diagram, you can see how the WSMKA ™ is able to manage 'other' WSMKA's ™. This is a major enhancement which allows for a 'monitoring' of services without the other WSMKA's ™ 'specifically knowing' this is occurring. This 'clustering' allows for the dynamic nature of the WSMKA ™.
This diagram below shows the basic WSMKA ™ architecture. As you can see, proxies are used to define the 'services' to be managed. This allows for a new service to be hot deployed and available for use. The other users of the main WSMKA ™ don't know about it and continue to work as before. Only the new user of the service is aware of its availability.
This architecture has been in development and testing for over a year and has proven itself in many deployments. Several existing WSMKA ™ services have already been deployed (these are the data access managers, XSLT translation managers, document managers, file managers, object to relational mapping managers, logging managers to name a few). These managers are all deployed using a XML-XSD combination. We call them deployment descriptors to be consistent with other technologies (JMX to be specific utilizing JBoss ™). This creates a powerful yet simple approach to manage our WSMKA ™ objects. Information is passed to and from these objects using XML and an XSD to force the XML parser to validate the data coming across. EACH lower service is responsible for validating this data and thus providing corrective actions or errors if the data is NOT correct. The WSMKA ™ will log those errors and then, provide them to the caller for handling. |
||||||||||||||||||||
|
|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
|
|
