0.1.1-understand-resilience_patterns[0.1.1] A category of fault_tolerance patterns (including circuit_breaker_pattern, retry_pattern, bulkhead_pattern, an
0.1.2-understand-distributed_cache[0.1.2] A cache shared across multiple nodes or processes in a distributed_system, providing low-latency access to fre
0.1.3-understand-plugin_architecture[0.1.3] An architectural style where a minimal core system exposes extension points that allow modules (plugins) to be
0.1.4-understand-api_composition[0.1.4] A pattern where a facade or aggregation layer combines data from multiple backend services or APIs into a sing
0.1.5-understand-distributed_transaction[0.1.5] A transaction that spans multiple independent services or database_per_service instances, requiring coordinati
0.1.6-understand-ports_and_adapters[0.1.6] An architectural pattern that separates the core business logic from external concerns by defining ports (inte
0.1-understand-core[0.1] the core subdomain of software architecture patterns and styles (13 concepts)
0.2.1-understand-pubsub_broker[0.2.1] The intermediary component that receives messages from publishers and forwards them to subscribers based on to
0.2.2-understand-stream_offset[0.2.2] A monotonically increasing integer position marker assigned to each event within a partition, uniquely identif
0.2.3-understand-stream_partition[0.2.3] A distinct, ordered slice of an event stream, identified by a partition key or index, enabling parallel produc
0.2.4-understand-pubsub_topic[0.2.4] A named channel or subject through which messages are routed from publishers to interested subscribers; the pu
0.2.5-understand-pubsub_message[0.2.5] The payload broadcast by a publisher on a topic; in pub/sub it is typically ephemeral and not persisted beyond
0.2.6-understand-stream_log[0.2.6] An immutable append-only sequence of events retained on disk or equivalent durable storage; unlike pubsub_mess
0.2-understand-deep_event_driven_archite[0.2] the deep_event_driven_archite subdomain of software architecture patterns and styles (60 concepts)
0.3.1-understand-dps_001[0.3.1] database_per_service is a data management pattern in microservices where each service owns and manages its own
0.3.2-understand-dps_014[0.3.2] eventual_consistency_model is the consistency guarantee that results from database_per_service: writes are imm
0.3.3-understand-dps_003[0.3.3] instance_isolation means each service runs its own database server process or cluster, with separate credentia
0.3.4-understand-gateway_routing_request_matcher[0.3.4] A component that evaluates incoming requests against route matching criteria.
0.3.5-understand-dps_002[0.3.5] schema_isolation means each service's database exposes only the data and operations relevant to its bounded co
0.3.6-understand-dps_006[0.3.6] data_duplication is the consequence of database_per_service where the same logical entity may be materialized
0.3-understand-deep_microservices_archit[0.3] the deep_microservices_archit subdomain of software architecture patterns and styles (32 concepts)
0.4.1-understand-microservices_architecture[0.4.1] An architectural style that structures an application as a collection of small, autonomous, loosely-coupled se
0.4.2-understand-gateway_routing[0.4.2] A pattern where an API_gateway routes requests to appropriate backend services based on request characteristic
0.4.3-understand-event_streaming[0.4.3] A data handling approach where events are captured in order as an immutable log (stream), allowing multiple co
0.4.4-understand-message_queue[0.4.4] A communication mechanism where messages are placed in a queue by producers and consumed asynchronously by con
0.4.5-understand-event_driven_architecture[0.4.5] A software design pattern where the flow of the program is determined by events (user actions, sensor outputs,
0.4.6-understand-api_gateway[0.4.6] A server entry point that routes requests to backend services, handling cross-cutting concerns like authentica
0.4-understand-software_architecture_patterns_and_styles[0.4] the software_architecture_patterns_and_styles subdomain of software architecture patterns and styles (106 concepts)
0-understand-software architecture patterns and styles[0] the software architecture patterns and styles library — every skill a certified region of the KB; call number = home : facets
using-software-architecture-patterns-and-styleUse the software architecture patterns and styles neurosymbolic module: RAG library, agent brain, growable KB — proof-checked