Flower chanting white striped \ / channel service: [331,575,644], staging music withdrawal, XIN mention card seconds ,, to staging, ease flowers, wayward pay various threshold withdrawals, flower chanting, white bars \ / Service letter: [315756443] professional second back section quickly, the operation can be face to face, a remotely operable! Quick and simple payment process, operating without professional card to get a few minutes alone!
In this article, I plan to introduce micro Services Architecture (MSA) of the key architectural concepts and how to use these principles in practice architecture.
Micro Services is one of the most popular field of software architecture buzzwords. A lot of learning materials on the basics and benefits of micro-services, but resources on how to use the micro-enterprise services in the real scene rarely.
In this article, I will introduce micro Services Architecture (MSA) of the key architectural concepts and how to use these principles in practice architecture.
Overall structure
Enterprise software applications designed to meet many business needs; a given software application offers hundreds of features, all of these features are piled in a single overall application. For example, ERP, CRM and other various software systems are constructed with hundreds of functions overall. Such a large software application deployment, troubleshooting, expansion and upgrade is a nightmare.
Service-Oriented Architecture (SOA) and a packet aggregation is intended to provide similar functions and services by introducing the concept of applications to overcome some of these limitations. The use of SOA, software applications can be designed as a combination of coarse-grained services. However, in SOA, the service is very wide. This leads to complex and large service has dozens of operations (functions), and the complexity of message formats and standards (for example: all WS * standards).
Overall structure
In most cases, SOA in the service independent of each other. But together they deployed to run in the same time with all other services (consider deploying multiple Web applications to the same Tomcat instance). Similar to the monolithic software applications, these services have habits by accumulating various functions over time growth. Literally, that these applications will become indistinguishable from the overall general-purpose applications (e.g., ERP) unitary structure. The figure shows the retail software application contains multiple services. All of these services are deployed to the same application running. So this is a good example of the overall architecture. This is based on some of the characteristics of the overall application architecture.
· The whole application is designed, developed and deployed as a unit.
· The whole application is extremely complex; this leads to maintenance, upgrades, and add new features nightmare.
· Difficult to practice agile development and delivery methods using Monolithic architecture.
• The need to redeploy the entire application to update a part of it.
· The application must be extended by a single unit, making it difficult to manage resources, conflicting demands (for example, a service requires more CPU, while another requires more memory)
· an unstable service possible It will cause the entire application to crash.
· The introduction of new technologies and frameworks really very difficult, because all functions must be based on the same technology / framework.
Micro Services Architecture