|
- What are microservices?
The microservices pattern language is your guide when designing an architecture: service collaboration, testing, deployment, common crosscutting concerns and more
- Microservices Pattern: Microservice Architecture pattern
I appreciate how you highlighted the benefits of microservices, such as increased scalability and faster development cycles, while also addressing the potential challenges involved Your practical examples and real-world scenarios added great value to the post, making it relatable and easy to grasp
- Microservices platforms: when team topologies meets microservices . . .
The following diagram shows five key platforms that are needed to support the development of microservices This article introduces these platforms and their relationship with the microservice architecture patterns Later articles will provide more details about each platform
- A pattern language for microservices
Architectural style Which architectural style should you choose for an application? Monolithic architecture - architect an application as a single deployable unit Microservice architecture - architect an application as a collection of independently deployable, loosely coupled services Service boundaries How to decompose an application into services? Decompose by business capability - define
- Pattern: Saga - Microservices
In a portfolio of hundreds of microservices with dozens of key biz transactions each with 3-5 participating services, how to make sure sagas are implemented properly across all service teams? has anyone done that?
- Microservices resources
Microservices in NET by Christian Horsdal Building Microservices by Sam Newman Articles Chris Richardson Series of articles on the NGINX blog begining with Introduction to microservices Infoq com article on microservices With other authors: InfoQ emag on microservices Various articles on adopting microservices (see who is using microservices
- Announcing the MEAP for Microservices Patterns, 2nd Edition
There’s a much sharper focus on fast flow — the continuous delivery of a stream of small changes and rapid feedback on each one - as the primary motivation for adopting microservices and the fast flow success triangle: DevOps, Team Topologies, and the microservice architecture
- Pattern: API Gateway Backends for Frontends - Microservices
The granularity of APIs provided by microservices is often different than what a client needs Microservices typically provide fine-grained APIs, which means that clients need to interact with multiple services
|
|
|