Ecosystem of Microservices

Explore essential design patterns for building and integrating microservices ecosystems. Understand the trade-offs between Monolithic UI, Client-Side UI composition, and Server-Side Page Fragment Composition to effectively deliver scalable and maintainable enterprise applications.

We'll cover the following...

- Monolithic UI backed by microservices
- Client-side UI composition
- Server-side page fragment composition

As I mentioned earlier, microservices are an evolution of SOAService-Oriented Architecture. SOA services enabled structuring entire enterprises around them. Similarly, microservices can evolve into a connected ecosystem within or across organizations. Therefore, it is utterly essential to know the basic principles of building microservices. I recommend that you check out resources online that teach the concept of microservices and related patterns (e.g., see here).

In this section, I want to cover a couple of vital aspects for building and evolving an ecosystem of microservices. Specifically, how should we build UI in front of existing services? Do we go with Monolithic UI, Client-Side UI composition, or Server-Side Page Fragment Composition? Since each of these approaches is valid in certain cases, I want to discuss them in more detail by covering their implementation intricacies.

1.Fundamentals

2.Part I: Introduction

3.Part II: Crosscutting Concerns

4.Part III: From Customer Insights to Internal Requirements

5.Part IV: Design and Architecture

6.Part V: Implementation and Coding

7.Part VI: Testing and Quality Assurance

8.Part VII: Deployment

9.Part VIII: Maintenance and Support

10.Wrap-Up

Ecosystem of Microservices

Monolithic UI backed by microservices