Microservices Architecture Pattern
Released: 08/31/2021
This document provides a repeatable approach to architecting, developing, and deploying microservices as Microservices Architecture Patterns (MAPs). The proposed MAP contains all the information necessary for a microservice to operate independently and communicate with other microservices which, in aggregate, become the components of an application.
This vendor-neutral reference architecture decomposes into software architecture patterns represented in software and platform (enterprise) planes, and then can be built back up with the addition of security control overlays. This can be demonstrated by the successful decomposition and recomposition of microservice architecture patterns where the integral action is the overlay of security controls.
Key Takeaways:
- The difference between architectures and solutions
- What Microservices Architecture Patterns (MAPs) are
- The components of several MAPs: offload, route, aggregation, cache, proxy, authN, authZ, facade, strangler fig, circuit breaker, and adapter patterns
- What security control overlays are
- The components of several overlays: service, IAM, network, monitoring, cryptologic, and microservice availability and resiliency overlays
Prefer to access this resource without an account? Download it now.
Best For:
- Application developers and architects
- System and security administrators
- Security program managers
- Information system security officers
