Context You are developing a server-side enterprise application. It must support a variety of different clients including desktop browsers, mobile browsers and native mobile applications. The application might also expose an API for 3rd parties to consume. It might also integrate with other applications via either web services or a message broker. The application handles requests (HTTP requests and messages) by executing business logic; accessing a database; exchanging messages with other systems; and returning a HTML/JSON/XML response. There are logical components corresponding to different functional areas of the application. Problem What’s the application’s deployment architecture? Forces There is a team of developers working on the application New team members must quickly become productive The application must be easy to understand and modify You want to practice continuous deployment of the application You must run multiple instances of the application on multiple machines ...
SQL 1. Structure Table,row,column PreDetermined Schema Create table with all the defined datatypes and size. Then you can use the table Relations 1:1,1:M,M:M 2. Nature Centralized data-all tables in the same database server 3. Scalability Vertical Increase the RAM,Storage Horizontal -> NOT good for horizontal scaling Sharding ...
Pattern: API Composition Context You have applied the Microservices architecture pattern and the Database per service pattern . As a result, it is no longer straightforward to implement queries that join data from multiple services. Problem How to implement queries in a microservice architecture? Solution Implement a query by defining an API Composer , which invoking the services that own the data and performs an in-memory join of the results. Example An API Gateway often does API composition.
Comments
Post a Comment