Digital Infrastructure Basics
A plain-language map of computing, storage, networks, identity, applications, data and operations.
Browse vendor-neutral explanations of architecture, cloud, networks, identity, security, data, operations, automation, AI and governance.
A plain-language map of computing, storage, networks, identity, applications, data and operations.
Turn business needs, user needs and operating limits into testable technology requirements.
Define what belongs inside a system, what remains external and where responsibilities change.
Use a repeatable method to compare platforms, architectures and services without letting feature lists decide the outcome.
Choose useful context, container, component, deployment and data-flow diagrams without creating decoration.
Compare delivery and operating trade-offs before splitting a system into independently deployed services.
Understand how clients, servers, services and shared state interact across a network.
Use service boundaries and contracts to coordinate capabilities across multiple applications.
Design systems around events, producers, consumers and asynchronous processing.
Place processing closer to devices or users when latency, bandwidth, autonomy or privacy justify it.
Identify deliberate shortcuts, hidden maintenance costs and practical modernization paths.
Plan segmentation, routing, resilience, remote access and operational visibility across connected sites.
Understand local and wide-area networking and when software-defined control adds value.
See how names, addresses and automatic configuration allow devices and services to communicate.
Distribute requests while accounting for health checks, sessions, capacity and failure behaviour.
Compare remote-access patterns, device trust, identity checks and application-level access.
Understand service models, shared responsibility, elasticity and the operational work that remains.
Choose a deployment approach based on workload, control, latency, skills, cost and regulatory needs.
Separate application packaging from infrastructure while planning networking, storage, security and operations.
Trade infrastructure control for managed operations without ignoring limits, lock-in and cost behaviour.
Estimate demand, latency sensitivity, peak traffic and resilience instead of relying on headline bandwidth.
Coordinate identities, authentication, authorization and access review across people, devices and services.
Connect hiring, role changes, leave and departure to timely access changes.
Automate account creation and removal while keeping ownership, exceptions and auditability clear.
Share trusted identity assertions across systems while managing session, assurance and outage risks.
Match evidence and verification effort to the harm caused by a mistaken or fraudulent identity.
Compare authentication factors, phishing resistance, recovery and deployment constraints.
Reduce standing administrative access and improve control over powerful accounts and service identities.
Assign ownership, review access and separate incompatible duties without turning reviews into paperwork.
Apply resource-focused, continuously evaluated access decisions rather than trusting network location.
Combine segmentation, secure configuration, monitoring and identity-aware access into a coherent design.
Make safe defaults, vulnerability reduction and customer security part of product and system design.
Prioritize remediation using exposure, exploitability, business impact and safe deployment practices.
Prepare roles, evidence, communication and recovery decisions before a serious incident occurs.
Move and synchronize data between systems while preserving meaning, quality and accountability.
Design interfaces as governed products with clear contracts, authentication, versioning and support.
Centralize selected traffic controls without turning the gateway into an opaque bottleneck.
Understand the connective software that coordinates applications, messages, transformations and transactions.
Use routing, transformation and mediation carefully while avoiding an unmanageable central dependency.
Decouple producers and consumers while planning delivery, ordering, retries and dead-letter handling.
Retain ordered event streams for multiple consumers while managing schemas, replay and capacity.
Choose where transformation happens and how pipelines are tested, monitored and governed.
Define ownership, meaning, quality, access, retention and acceptable use across the data lifecycle.
Coordinate shared entities and code sets without assuming one database can solve every ownership problem.
Measure fitness for use through accuracy, completeness, timeliness, consistency and traceability.
Keep data only as long as justified and make deletion workable across primary, replicated and backup systems.
Build data minimization, purpose limits, transparency and user control into system decisions.
Use metrics, logs, traces and user signals to understand service health and investigate failure.
Collect complementary evidence without drowning teams in unowned alerts and excessive data.
Track desired settings, approved changes and system drift across environments.
Balance delivery speed with review, testing, rollback and clear accountability.
Design recoverable copies, restoration procedures and tested recovery objectives.
Connect technology recovery to people, facilities, suppliers, communications and manual workarounds.
Limit failure impact through redundancy, isolation, graceful degradation and tested recovery.
Plan for growth, peaks and failure conditions using measured demand and service limits.
Define measurable reliability targets that connect user experience with engineering priorities.
Write actionable procedures with ownership, prerequisites, decision points and validation steps.
Reduce repeated incidents by studying contributing conditions rather than stopping at a single cause.
Understand industrial and physical-process technology where safety, availability and long lifecycles shape decisions.
Automate repeatable work while retaining controls, exception handling and accountable ownership.
Improve flow and feedback across development and operations without treating tools as the transformation.
Build repeatable pipelines for testing, packaging, approval and deployment.
Manage infrastructure definitions through versioned, reviewed and repeatable change.
Choose automated tests by risk, feedback value, maintenance cost and coverage gaps.
Compare rollout patterns by rollback speed, capacity needs, observability and state management.
Provide supported internal capabilities that reduce repeated delivery work without hiding operational reality.
Control credentials, keys and certificates through protected storage, rotation and limited access.
Track libraries, versions, licences and vulnerabilities across the software supply chain.
Improve provenance, build integrity, dependency control and release verification.
Coordinate multi-step processes with states, retries, approvals and exception paths.
Plan data, development, evaluation, deployment, monitoring and retirement as one governed lifecycle.
Identify context-specific harm, uncertainty, accountability and monitoring needs before and after deployment.
Evaluate useful tasks, data exposure, output review, reliability and workforce impact.
Define when people review, intervene, override and remain accountable for automated decisions.
Assess rights, quality, representation, lineage and operating controls before pursuing models.
Choose deterministic rules or probabilistic models based on variability, explainability and risk.
Compare evidence, data practices, security, portability, monitoring and contract terms.
Connect devices, networks, platforms and operations while planning updates, identity and lifecycle support.
Link digital models with real assets or processes without confusing simulation with reality.
Run models near devices when latency, bandwidth, privacy or autonomy justify the added operational burden.
Inventory cryptographic dependence and plan migration without buying into speculative promises.
Connect technology investments to outcomes, constraints, sequencing and measurable decisions.
Compare custom development, commercial products and configurable platforms across their full lifecycle.
Assess capability, security, support, finances, evidence, fit and exit options.
Include implementation, integration, migration, support, training, change and retirement—not only licence price.
Turn service expectations into measurable definitions, responsibilities, remedies and review processes.
Plan access to data, transition assistance, deletion and continuity before signing.
Include disabled users and accessibility requirements in procurement, design, testing and support.
Consider energy, useful life, repair, reuse, disposal and supplier practices across the system lifecycle.
Keep architecture, ownership, decisions and procedures current enough to support real work.
Plan role-based learning, practice and support alongside technology change.
Record risk in decision-ready language with ownership, treatment, evidence and review dates.
Build a manageable foundation around identity, devices, backup, collaboration, support and documented ownership.
Balance mission, donor data, volunteer turnover, limited budgets and continuity needs.
Coordinate identity, devices, connectivity, support, collaboration and data protection across locations.
Standardize core services while allowing site differences in connectivity, operations and local support.
Connect storefronts, payments, inventory, fulfilment, customer service and analytics with recoverable operations.
Protect client information while supporting collaboration, records, billing and portable work.
Plan identity, devices, accessibility, privacy, support and changing user populations.
Coordinate business IT and operational technology while respecting safety and production continuity.
Prepare accounts, devices, support and capacity for predictable peaks and temporary workers.
Inventory systems, identities, contracts, data and operational dependencies before consolidation.