Computer Systems & Network Architecture

← Back to Domain-Specific Families

Abstractions about how computer systems and networks are organized and interoperate, including execution and isolation environments such as application domains and protection rings, networking and addressing schemes like IP addressing, NAT traversal and routing, and software or service architecture styles such as service-oriented and web-oriented programming.

20 abstractions in this family — domain-specific abstractions that sit near one another in structural-signature space (k-means over structural-signature embeddings). Each is shown with its short description.

• Application Domain — A Common Language Infrastructure managed-execution boundary, commonly known as a .NET AppDomain, that isolates assemblies, configuration, security context, static state, and failure or unloading behavior for applications hosted within one operating-system process.
• Code Mobility — The capability to transfer executable code, optionally with data and suspended execution state, between hosts or runtime environments so computation begins or continues at the destination.
• Computer architecture — The conceptual and operational organization of a computer system, including its instruction-set contract, microarchitecture, memory, and input/output interactions and their design tradeoffs.
• Computer Peripheral — A hardware device accessible to and controlled by a computer that provides input, output, storage, communication, or specialized function outside the system's contextually defined core processing components.
• Distributed File System for Cloud — A cloud-scale file service that distributes file contents and metadata across networked nodes while preserving a declared namespace, operation, consistency, security, and failure-recovery contract for many clients.
• Exit Status — A small value produced when a process terminates and made available to its parent or caller to summarize whether and, by convention, how the execution completed.
• HITS Algorithm — A link-analysis algorithm that iteratively assigns each node an authority score from incoming high-hub links and a hub score from outgoing links to high-authority nodes, usually on a query-dependent directed subgraph.
• Internet Mix — A repeatable mixture of packet sizes used to benchmark routers, switches, firewalls, and related equipment under representative traffic load.
• IP Addressing — The Internet Protocol scheme that assigns IPv4 or IPv6 addresses to network interfaces and divides address bits into routing prefixes and interface portions so packets can identify endpoints and be forwarded across interconnected networks.
• Layered Queueing Network — A queueing model for nested services in which callers may wait for lower-layer requests, causing one node's effective service time to depend on another queueing subsystem's response time.
• Memory Organisation — The arrangement of memory banks, word widths, addressing, and buses that governs how computer main memory supplies data and programs to a cache.
• NAT Traversal — Techniques that discover, establish, and maintain network paths across address-translating gateways by coordinating mappings, testing candidates, and relaying when necessary.
• Network Transparency — The property of a distributed system or protocol that lets clients use remote resources through substantially the same interface and naming conventions as local resources while hiding network location and communication mechanics.
• Protection Ring — A hardware-enforced hierarchy of execution privilege levels with controlled transitions from less-privileged outer rings to protected inner-ring services.
• Remote evaluation — A mobile-code pattern in which a client sends executable code to a remote server for execution and receives the resulting values back.
• Routing — The process of computing and maintaining admissible network paths or next hops from topology, addressing, metrics, and policy so forwarding can deliver traffic toward destinations.
• Service-Oriented Programming — A programming approach that builds application behavior from encapsulated in-memory service units, their interfaces, and their composition.
• Software-Defined Protection — A layered network-security architecture separating traffic enforcement, protection-policy generation, and administrative orchestration across coordinated enforcement, control, and management layers.
• Task Computing — A pervasive-computing approach that maps a user's task to discoverable semantically described services, composes them, and executes the resulting workflow.
• Web-Oriented Architecture — A software architecture style that exposes composable services or resources through Web identifiers, HTTP interactions, and transferable representations.