On a standard product development ideas, we generally consider the product into the content, technology platforms and three levels. It may be the lowermost technology platform, a technology platform that can be derived from multiple product platforms, a product platform and can be derived from a variety of models of product specifications. The core idea of the construction of the platform is sinking existing business systems common to non-business related content, sink through the centralized build and maximize reuse. In the construction business systems truly decoupled business and technology, and business platform, developers only need to focus on the business, rather than too much attention to technical detail and the underlying platform.
In the traditional platform construction process, we emphasize development platform based on that architecture is based on a technology developed secondary package offers a complete development framework and modalities for the use of various business systems, business systems follow the same ideas and the development process . This is useful in the construction of the early internet. Follow simple we could possibly stay in the whole empty frame above. Because each application system are involved in the development of the organization, permissions, workflow engine, security, exceptions, such as the development logs, and content due to the business and has nothing to do with a lot of commonality, and therefore a further evolution in the second phase of the platform , that is, not to provide air frame, but does not contain any business function space applications. Various business systems fully operational infrastructure components and modules in the empty application basis. The empty application system that is further transition towards the level of product platforms.
While in the third stage, although free applications, but the organization permission to process rules are still in various business systems inside, various business systems need this part of the content management and maintenance. Therefore, the platform will further consider the organization as general-purpose engine capacity, privileges engines, workflow engines stripped from the real business out of the system, a unified and centralized, migrate to the cloud formed by the terminal various business systems share content. This centralization is the enterprise platform to go towards a PAAS platform evolution of ideas.
Back to see GAE and Microsoft's Azure Google for ideas PAAS platform as a service, their core logic is as long as you follow the standard development framework and open interfaces provide me with the ability, you can develop applications to hosting My Cloud surroundings. And this cloud environment to meet your distributed computing, distributed storage, all the needs of distributed resource scheduling. Therefore middleware, database, based on the underlying platform has been built entirely cloud of both the cloud to achieve centralized management and dynamic scheduling.
Platform provides the ability to layer, namely the ability to service, the service needs to be integrated, which is we often say that SOA and related point cloud. After our entire platform of the cloud, between business systems and platforms also need to integrate in order to achieve the ability to access and use, which is required by ESB bus mechanism. In this idea we come to analyze the relationship between PAAS platform and each of the other key elements. Relations PAAS and SAAS platform layer
First PAAS platform within the enterprise is a common platform for various business systems, so PAAS platform itself needs to support multi-organizational and multi-tenant. Second PAAS and SAAS platform, not necessarily related, according to business needs be. PAAS platform-based applications developed in a public cloud environment may be biased SAAS applications in a private cloud environment is not necessarily a SAAS application. PAAS can also be no direct integration SAAS layer and IAAS layer.
Here only enterprise content, many times we will SOA integration platform itself as part of the enterprise PAAS platform. SOA integration platform provides integrated capabilities and services, the basic functions of BPEL process orchestration, BPM and rules engines. Internal SOA integration platform is not in the business system, but only one set of centralized, this ESB capability for various business systems to use and implement centralized management.
After the adoption of SOA to solve basic problems, the transition to the internet you have to consider PAAS PAAS platform itself can generate new services and capabilities through the combination and orchestration, this ability can be generated and centralized management in PAAS platform inside, rather than the traditional in SOA business systems to produce just integration.
For PAAS layer platform needs to provide the base layer have internet capabilities, which are sinking each original business system capabilities. We often say that the unified organization permissions engine, master data, unified process modeling, execution and monitoring platform to all classified SOA integration platform. The real significance of these basic capabilities by providing a complete business system modules only remaining business and business components. Toward the business components and assembly capability of the idea further.
PAAS platform implementation must take into account the construction of PAAS platform development framework itself is a big change and patterns. Only standards-based development frameworks and models will be able to automatically deploy and application hosting. Here we have more emphasis on the development model of SOA within, in order to consider the follow-up NoSQL database, we will weaken thinking relational database, to further strengthen the field of modeling ideas. Componentized architecture + art modeling I think that is the core of development thinking PAAS platform.
