A good service: loose coupling and high cohesion
Bounded context: a model has specific information. If this is wanted externally, a request must be made using an explicit interface. Share information uses a shared model object, not the internal representation.
Break the system up along functional (and/or organisational) boundaries, not technical boundaries.
Tuesday, September 15, 2015
Chapter 1
What Are Microservices?
Small: the smaller the service, the more you maximize the benefits and downsides of microservice architecture.
Focused on Doing One Thing Well: Robert C. Martin’s Single Responsibility Principle, which states “Gather together those things that change for the same reason, and separate those things that change for different reasons.”
Autonomous: All communication between the services themselves are via network calls, to enforce separation between the services and avoid the perils of tight coupling.
Benefits
- tech heterogeneity
- resilience
- scaling
- ease of deployment
- organisational alignment
- composability
- optimized for replaceability
Hexagonal architecture: Create your application to work without either a UI or a database
Subscribe to:
Posts (Atom)