Micro-service architecture businesses of all sizes are gaining wide attention; they are one of the most popular design software application method. Compared with traditional monolithic applications development methods, micro-service architecture allows for faster changes and the development of new applications, it can provide greater agility. Netflix, Google, Amazon and many other IT companies have been successfully using this architecture, and guide others to emulate this model.
For most businesses, the use of micro-services architecture and the transition will be a gradual process, will co-exist and interact with the traditional application of micro-based applications and services. Micro service must be legacy applications, existing systems and business processes, as well as current business operations, and compliance requirements exist.
In addition, micro-service benefits, while also introducing some negative resistance, such as the spread of service, increased complexity, and increase the risk of redundant work. Micro businesses and organizations need service API and effective implementation of common IT architecture.
For many companies, the challenge is to learn how to combine a number of other architectural patterns and micro-enterprise service architecture deployed. While controlling complexity, speed management and service provision micro flexibility method is to use API. API to develop an overall strategy to make the service easier to micro-manage, and allow them to coexist with existing legacy systems, rather than living in a walled garden away from these critical systems. The micro-service architecture combined with the overall API strategy is an effective way to gain an advantage to bring micro-services, while effectively limiting the disadvantages mentioned above.
How micro-services API and work together
API was the underlying code programming interfaces, but now they have become the product itself, follow a standard API, such as REST, making them more friendly to developers, and have a stronger management and governance capabilities. API providers are now competing with each other, to draw attention to developers. And, API economy, a new economic model around the value exchange between the user and the API API providers are growing.
Changes in API usage also changed their technical requirements. API now requires complex portal where developers can find and test them. Also you need to provide registration and payment API calls, and restrictions on the use of various mechanisms API. Moreover, since the external API is open, they need to provide a strong security capabilities through the API gateway. When all of these features together, they form an API to manage such a new class of solutions that provide control for the increasingly valuable business assets, visibility and governance capabilities.
All of the Internet public API (and the value they create) concerns have raised the question: Is there a way for the API within the enterprise to achieve the same value? Now API management technology has become more mature, they can now be found to achieve data sources, services and applications and self-service. This makes the entire enterprise more teams in a controlled and visible way to develop software, extended IT team's productivity and create internal API economy.
The use of micro-service architecture, interior API economic value even higher, because as micro data services to create more endpoints, difficult to control the connection will be. In trying to create ad hoc connections between all of these endpoints will be disastrous. In a micro-service architecture such as the highly distributed environment, the development of an overall API strategy will be crucial.
Many companies adopt a strategy to open all API services (whether they are or are based on micro-services architecture monomer; deployed in local or cloud-based deployment): led by the API connection. This led to the API integrated approach is a clear overall strategy: it uses a different function, reusable API to open the service, and use the API to combine and reconstruct the different types of services to create and easy to change evolving business needs.
With the application of micro-services architecture becomes more popular, especially for established organizations with traditional IT technology stack, integrating all of these services and obtain the value of the problem becomes even more important. This is the implementation of the system integration strategy led to the API, an important reason for the entry into force of the micro-service architecture within the enterprise.
API not only to bridge the gap between legacy systems and micro-services, and also enables to build and manage micro services easier. Through the development of API strategy, the company may have to provide micro-service public function for the product, which can bring business value inside and outside at the same time.
Standardized, product-oriented API also help to reduce the SaaS application integration point between the costs associated with traditional IT systems and build. This enables organizations to quickly swap micro services based on business needs, without extensive custom development. API can be standardized across the enterprise way traffic management and monitoring mechanisms to provide standardized logging, auditing, and security, while retaining the flexibility needed business.
These good management API can also reuse micro services and discoverability. With the development team could build a broader consumer users beneficial micro-services, API interfaces so that they can be found. Then, these micro-services open to a wider audience - internal or external - and managed as reusable functions.
Reproduced in: https: //juejin.im/post/5cf50d45f265da1b614fe2af