架构模式

Monolithic, layered, event-driven, CQRS, microservice, and plug-in architecture patterns.

What monolithic architecture is and its advantages and disadvantages.

What layered architecture is and its evolution from one, two, and three tiers to DDD four-layer, hexagonal, and onion architectures.

What read/write separation is, why it is needed, where it applies, how to design it at the service and storage layers, and the materialized-view pattern.

What event-driven architecture is, why it is needed, its real-time trade-off, and publisher-subscriber and event-stream design patterns.

What DDD is: domains, ubiquitous language and bounded contexts, entities and value objects, aggregates, domain events, repositories and factories, and a DDD design process.

Historical notes on what microservice architecture is, its relationship with SOA, trade-offs, decomposition, project architecture, and the microservice technology stack.

Historical notes on what OpenID Connect is and how its flow differs from OAuth by adding OpenID identity information and an ID Token.

Historical JWT notes covering what JWT is, why it is used, JWT versus sessions, token structure, and the basic request flow.

Historical OAuth 2.0 notes covering why OAuth is needed, the authorization flow, grant modes, token refresh, and scopes.

What a configuration center is, why it is needed, storage, client notification, service discovery, caching, canary release, and an example configuration-center database design.

What load balancing is, why it is needed, common algorithms, hardware/software/DNS choices, L2/L3/L7 approaches, and client-side versus server-side load balancing.

What a service registry is, why it is needed, server-side and client-side design, service discovery and routing, registry components, and ZooKeeper versus Eureka.

What an API gateway is, why it is needed, request forwarding and filtering, I/O models, common gateway components, BFF, and gateway aggregation.

What monitoring is, why microservices need it, and the three parts: logs, metrics, and tracing.

What tracing is, why it is needed, Span/Trace/Annotation data, sampling, collection approaches, storage, display, and common tracing components.

What fault tolerance is, service avalanche, and common techniques including timeouts, retries, rate limiting, circuit breaking, isolation, and degradation.

What log monitoring is, why it is needed, logging strategy, collection, aggregation, indexing and storage, analysis, and ELK.

What metrics monitoring is, why it is needed, what to monitor, how to collect and store metrics, alerting, and common metrics components.

Authentication, authorization, and credentials; common techniques; and how authentication and authorization are integrated into a microservice architecture.

Historical notes on cloud native, cloud platforms, VPCs, and the evolution, purpose, and common implementations of Service Mesh.

Original VNote placeholder for pluggable architecture.

A short note on what container scheduling is, why it is needed, and Kubernetes as a scheduling component.

A short note on CI/CD pipelines, their purpose, design, and Jenkins.