Shared-nothing architecture
Shared-nothing architecture is a design in which components independently manage resources without sharing mutable state, communicating through explicit interfaces.
Server-Side WebAssembly
Shared-nothing is an architecture in which interacting execution units do not share memory or other mutable state and communicate through explicit interfaces.
- How it is used
- Uses explicit imports and exports to connect isolated Wasm components, hosts, and runtimes without shared memory.
- How deep it goes
- Explains memory copies and opaque resource handles, while deferring deeper resource-table treatment to a later hands-on example.
- Examples
- Demonstrates a secret-store get call and a SmartCMS guest using a key-value-store interface.
- What you can do after
- Evaluate/understand how interface-only component boundaries contain access and permit targeted replacement of patched components.
Read how Server-Side WebAssembly explains shared-nothing architecture →
PostgreSQL Mistakes and How to Avoid Them
A shared-nothing architecture gives each node independent storage and processing resources rather than sharing them directly with other nodes.
- How it is used
- Frames PostgreSQL replication and high availability around independently operated database nodes.
- How deep it goes
- Explains node independence, replication origins, feedback loops, key collisions, and schema-divergence failures.
- Examples
- Uses publications, subscriptions, replicated tickets, duplicate identity keys, and a renamed column to expose failure modes.
- What you can do after
- Evaluate multi-master designs by tracing replication origins, conflicts, feedback loops, and schema compatibility.
Read how PostgreSQL Mistakes and How to Avoid Them explains shared-nothing architecture →
Related concepts
- Wasm componentused by · A Wasm component is a composable WebAssembly artifact that packages interfaces and implementations so code from different languages can be linked together.
- taskused by · A Kafka Streams task is an independently executable processing unit that processes assigned input partitions through a topology and its associated state stores.
- PostgreSQL replicationincludes · PostgreSQL replication is the process of copying database changes from one PostgreSQL instance to another.
- key-value storeuses · A key-value store is a data-storage system that associates keys with values and supports storing, retrieving, or updating values by key.
- defensive copyproduced by · A defensive copy is an independently created duplicate of mutable data that prevents subsequent external modifications from affecting retained state.
- Seastarused by · Seastar is a C++ framework for building high-performance asynchronous server applications with per-core resource management.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.