From soft test papers
On architecture design of enterprise integration platform
Third, select the appropriate application integration platform
( Description ) now open (open source) enterprise application integration platform and norms of mainstream technology in two ways: - + species is Microsoft's COM ( Component Object Model ) specification and Windows NET platform, the other is the SUN company. EJB specification ( server-side component model ) and the J2EE platform. ( Resolved choice ) on the platform of choice I made repeated comparison, the final choice of the J2EE platform. ( The reason * 3 ) because of the openness of J2EE platform (open source) and support heterogeneity ( supports heterogeneous environments ) , portable resistance, supported by extensive ( widely accepted ) . Company's existing legacy systems and technical advantages such as inheritance (meaning now the company is using java-related structures ) . More importantly, it has a cross-platform ( PC and mobile sides ) function . ( Actual) The company's ERP ( enterprise resource planning ) system is running on Linux on the server, PDM ( product data management ) system is used in Microsoft Windows NT (New Technology) operating system, E- mail is Microsoft's Exchange Server, these applications use different operating systems and platforms ( contrast ) and Microsoft. NET can only be used in the Windows operating system. ( Conclusion ) Therefore, based on the actual company, J2EE platform is the right choice. ( Shortcomings ) to select the J2EE platform is problematic in that, first, the cost is relatively high. Second, the company's IT staff is not skilled for JAVA. To this end, ( to address the shortcomings ) after I determine the selection of the platform, the platform to understand the software configuration (meaning roughly know what software needs to be installed) , only buy the software development we need, thus saving costs. JAVA is scheduled for several training, enabling IT staff can quickly get started with JAVA development program. ( 400 )
Enterprise Systems Integration Category:
Interactive system (System of Engagement) with the recording systems (System of Record)
The introduction of micro-enterprise services architecture focused on the following types of systems:
Record systems :(defined)refers to the traditional applications, the applicationconcernsthe field of information is performed as a core competence CRUD application. Such as CRM(customer relationship management), ERP(enterprise resource planning), OA(office automation)systems. (Shortcomings)recording systems are often used in some traditional classical IT technology to build, often more difficult to change, integrate it more difficult to perform.
Interactive systems :(definitions)refers to the interaction with the user for theprimary purpose ofthe application system development. As mobile applications, micro-channel, micro-blog and the like. (Advantage)interactive system will use more modern language and deployment of new technologies runtime, highly specific agility, integrated connection can be realized by a simple modernization.
Note: agility , is an enterprise in a changing, unpredictable strain the ability of good business environment.
System integration issues and principles:
Part of the system can not be reconstructed micro Services Architecture: such as very old and lack of maintenance of the system, ( solve ) for such a system policy "If the application can not be broken, do not try to fix it" can be used, in which the reuse of SOA assets It is a better solution.
The existing system can not change the data storage mode: this situation,(analysis) first, theneed to consider if the data remains chimney(monomer)or centralized storage,then the application of micro service whetherbusiness value;first Second,segmentation database will lead totransactionalconsistency problemsand thus affect the stability of the system;third,to consider the possibility of introducing applications such as BASE, CQRS and othermodelconsistency problem solving data.
Note: BASE mode ( accepting temporary inconsistencies, the use of eventual consistency )
CQRS mode (operation separated and queries, separate read and write)
The original system how to integrate micro Services Architecture: When stripped some of the features in the original system and reconstructed into micro-services, how to implement micro-services with legacy systems inhigh availabilitysegregation, if the original system and micro-servicescalabilityis not matching and how to deal with? These problemsinfront microService reconstructionneedto think clearly.
Micro service transformation
Micro-service architecture means that in a more complex environment for the operation and maintenance costs, faster speed to market. Most companies have a lot of legacy applications, is usually the case , companies will not build a complete new application, but is has been applied to reconstruct or want to try to reuse existing code .
Enterprise application integration solutions:
In the application integration and reconstruction aspects, our team of project possible micro-services of the sort : (1) each of the REST services is a potential micro-services; (2) each SOAP web service or EJB is a potential micro services, in particular stateless session bean, we need to re-design the interface for the function of asset-oriented interface, and interfaces into a RESTful form; (3) the use of domain-driven design (domain-driven design) found that corporate assets, these assets may be micro-services.
In the data integration and reconstruction aspects of our team in the following ways : (1) find little other data associated with data silos , ( explain ) the entity inspection system - diagram; if there is a disconnect with other data, as a potential reconstruction of data point; (2) the data table denormalized , to find a high number of data normalization Africa normalized database table , to which recombinant larger logical blocks, whose purpose is to increase redundancy of data to make it easier is broken; (so as to facilitate construction of an independent micro database service) (3) reverse batch data update , when data reconstruction may fail in bulk to new data reverse back to the old data model; (4) the use of master data management , data entities are widely used in a single consistent view, and to develop the corresponding micro service work together with the main data;
Supplementary understanding: Master Data Management importance: to ensure high standards of unique information coding system units within the enterprise, on the other hand to lay the foundation for the future protection of enterprise data warehouse construction, data standardization system for the import, multi-dimensional statistical analysis to create the prerequisites .