| Description |
1 online resource (1 volume) |
| Summary |
Miniservices provide a valuable middle ground between monoliths and microservices. As Nicholas Keune explains in this report, miniservices are suited for application landscapes involving data-intensive workloads that span monoliths and microservices or cross the traditional boundaries of a service context. Drawn from the work of many development teams, the report gives a model and language to data-centric system attributes so that they can be considered more proactively in the design discussion. Combining monolithic corporate or third-party systems with microservices requires a design pattern to balance both local and global aspects of the data lifecycle. The approach advocated here, called a data discourse, is both flexible and bounded by guiding principles that help bring data discussions into early architectural conversations. Using real-world experiences and use cases, the report focuses on three of the most commonly observed attributes in a miniservice: consistency, transactionality, and proximity. The examples illustrate how design discussions about data discourses lead to miniservice creation, and how miniservices help solve otherwise difficult architectural challenges. With this report, you'll learn: What miniservices are and how they offer solutions to challenges What data discourses are and how to use them How data discourses and miniservices help shift design discussions around data. |
| Subject |
Business enterprises -- Data processing.
|
|
Electronic data processing -- Distributed processing -- Management.
|
|
Web services.
|
|
Entreprises -- Informatique. |
|
Services Web. |
|
Business enterprises -- Data processing |
|
Electronic data processing -- Distributed processing -- Management |
|
Web services |
| Added Title |
Patterns for managing data across microservices and monoliths |
|
More Resources