Microservices

Microservices is an architectural style that structures an application as small, independently deployable services communicating over a network. Each service typically owns a distinct capability and can be developed and operated separately.

Domain-Driven Design: A software design approach that models systems around a domain and its business concepts. Bounded contexts help teams choose service boundaries that reflect distinct areas of the business.
Containerization: The packaging of software and its dependencies into isolated, portable execution environments. Containers provide repeatable units for building and deploying services.
Monolithic Architecture: An architectural style that builds an application as a single deployable unit. It avoids network boundaries between components but couples their release and scaling.
Conway's Law: The observation that systems tend to reflect the communication structures of the organizations that design them. Service boundaries often mirror team boundaries, making organizational design part of architecture.
API Gateway: A component that routes and manages requests from clients to backend services. It can provide a single entry point while hiding the locations of individual services.
Kubernetes: An open-source system for deploying, scaling, and managing containerized applications. It automates deployment and recovery for fleets of service instances.
Service-Oriented Architecture: An approach that organizes software into interoperating services, often across an enterprise. It shares the service-based idea but commonly uses broader service boundaries and enterprise integration.
DevOps: A set of practices joining software development and operations through shared responsibility and automation. Teams owning services in production need development and operational work to fit together.
Service Discovery: The process by which services find the network locations of other services. Dynamic instances need a way to locate one another as deployments change.
Continuous Delivery: A software development practice that keeps changes ready for reliable release to production. Independent release pipelines allow services to ship without coordinating every application change.

Linked from 6 pages