---
title: "How it works Visual Explainers"
description: "28 visual explainers about How it works."
---

# How it works Visual Explainers
> 28 visual explainers about How it works.

## Visual Explainers

### [How Apache DataFusion Runs SQL In-Process](https://yomu.fyi/visual-explainers/how-apache-datafusion-runs-sql-in-process.md)
- Type: How it works
- Tags: [Apache Arrow](https://yomu.fyi/topic/apache-arrow.md), [Apache DataFusion](https://yomu.fyi/topic/apache-datafusion.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md), [Parquet](https://yomu.fyi/topic/parquet.md), [Rust](https://yomu.fyi/topic/rust.md), [SQL](https://yomu.fyi/topic/sql.md), [UDF](https://yomu.fyi/topic/udf.md)

Apache DataFusion is an embeddable query engine: SQL goes in, runs as columnar Arrow batches inside your own process, and results come out without a separate service.

### [How MaaS Governance Wraps a Model Endpoint on AKS](https://yomu.fyi/visual-explainers/how-maas-governance-wraps-a-model-endpoint-on-aks.md)
- Type: How it works
- Tags: [AI Gateway](https://yomu.fyi/topic/ai-gateway.md), [AKS](https://yomu.fyi/topic/aks.md), [Authentication](https://yomu.fyi/topic/authentication.md), [Azure](https://yomu.fyi/topic/azure.md), [Kubernetes](https://yomu.fyi/topic/kubernetes.md), [Rate Limiting](https://yomu.fyi/topic/rate-limiting.md)

A model deployed on AKS is open by default. See how MaaS policies insert Authorino authentication and Limitador rate limits in front of vLLM, so bad keys and over-quota requests stop at the gate.

### [How Caddy Serves a Static Site: The Request Flow](https://yomu.fyi/visual-explainers/how-caddy-serves-a-static-site-the-request-flow.md)
- Type: How it works
- Tags: [Caddy](https://yomu.fyi/topic/caddy.md), [DNS](https://yomu.fyi/topic/dns.md), [Docker](https://yomu.fyi/topic/docker.md), [Fly](https://yomu.fyi/topic/fly.md), [Hugo](https://yomu.fyi/topic/hugo.md), [TLS](https://yomu.fyi/topic/tls.md)

See how Caddy handles a request for a static site, from DNS resolution through container routing to file\_server, and how TLS and redirects fit into the flow.

### [How BYOK Works: Your Key and Knowledge at Request Time](https://yomu.fyi/visual-explainers/how-byok-works-your-key-and-knowledge-at-request-time.md)
- Type: How it works
- Tags: [AI Gateway](https://yomu.fyi/topic/ai-gateway.md), [AI Governance](https://yomu.fyi/topic/ai-governance.md), [Auditability](https://yomu.fyi/topic/auditability.md), [BYOC](https://yomu.fyi/topic/byoc.md), [BYOK](https://yomu.fyi/topic/byok.md), [Data Governance](https://yomu.fyi/topic/data-governance.md)

BYOK lets a system run on assets you supply — your model credential or your private knowledge — instead of the vendor's defaults. This walkthrough traces six steps from registration to an audited response.

### [APRA CPS 230: Building an AI Stack You Can Swap Out](https://yomu.fyi/visual-explainers/apra-cps-230-building-an-ai-stack-you-can-swap-out.md)
- Type: How it works
- Tags: [AI Governance](https://yomu.fyi/topic/ai-governance.md), [API Gateway](https://yomu.fyi/topic/api-gateway.md), [APRA](https://yomu.fyi/topic/apra.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Australia](https://yomu.fyi/topic/australia.md), [Compliance](https://yomu.fyi/topic/compliance.md)

APRA's April 2026 letter flags single-provider concentration as a CPS 230 risk, so AI stacks need a rehearsed substitution path. This flow maps five stages, from workload classification to provider swap.

### [How AWS CloudFormation Turns a Template Into a Reconciled Stack](https://yomu.fyi/visual-explainers/how-aws-cloudformation-turns-a-template-into-a-reconciled-stack.md)
- Type: How it works
- Tags: [AWS](https://yomu.fyi/topic/aws.md), [AWS CloudFormation](https://yomu.fyi/topic/cloudformation.md), [Configuration Management](https://yomu.fyi/topic/configuration-management.md), [Deployment](https://yomu.fyi/topic/deployment.md), [GitOps](https://yomu.fyi/topic/gitops.md), [YAML](https://yomu.fyi/topic/yaml.md)

CloudFormation is a declarative reconciler: you describe the target state in a template, and it provisions, updates, and reports on the stack that results. Here is the loop.

### [How Coding Agents Get Grounded in Your Stack](https://yomu.fyi/visual-explainers/how-coding-agents-get-grounded-in-your-stack.md)
- Type: How it works
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Anthropic](https://yomu.fyi/topic/anthropic.md), [Claude Code](https://yomu.fyi/topic/claude-code.md), [MCP](https://yomu.fyi/topic/mcp.md), [Sandboxing](https://yomu.fyi/topic/sandboxing.md), [Tool Calling](https://yomu.fyi/topic/tool-calling.md)

A four-stage flow showing how a coding agent moves from a task to a reviewed change by grounding on verified skills, live system state, and code-first config before it acts.

### [How a Board of Directors Works: The Governance Control Loop](https://yomu.fyi/visual-explainers/how-a-board-of-directors-works-the-governance-control-loop.md)
- Type: How it works
- Tags: [Auditability](https://yomu.fyi/topic/auditability.md), [Board of Directors](https://yomu.fyi/topic/board-of-directors.md), [Compliance](https://yomu.fyi/topic/compliance.md), [Data Governance](https://yomu.fyi/topic/data-governance.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md), [Engineering Management](https://yomu.fyi/topic/engineering-management.md)

Boards of directors turn ownership into a governance control loop: shareholders elect directors, directors set strategy and guardrails, committees verify independently, and management executes inside those limits.

### [How Blackwell Serving Turns Peak FLOPs Into Cheap Tokens](https://yomu.fyi/visual-explainers/how-blackwell-serving-turns-peak-flops-into-cheap-tokens.md)
- Type: How it works
- Tags: [Blackwell](https://yomu.fyi/topic/blackwell.md), [GPU](https://yomu.fyi/topic/gpu.md), [Inference](https://yomu.fyi/topic/inference.md), [Mixture of Experts](https://yomu.fyi/topic/mixture-of-experts.md), [Quantization](https://yomu.fyi/topic/quantization.md), [Speculative Decoding](https://yomu.fyi/topic/speculative-decoding.md)

Blackwell inference is a pipeline, not a chip upgrade. This explainer walks five stages — fleet validation, batching, KV caching, low-precision kernels, and speculative decoding — that turn peak FLOPs into cheap tokens.

### [How a 3D CT Model Reads a Volume: From Voxel Grid to Structured Report](https://yomu.fyi/visual-explainers/how-a-3d-ct-model-reads-a-volume-from-voxel-grid-to-structured-report.md)
- Type: How it works
- Tags: [3D CT](https://yomu.fyi/topic/3d-ct.md), [DICOM](https://yomu.fyi/topic/dicom.md), [Healthcare](https://yomu.fyi/topic/healthcare.md), [Machine Learning](https://yomu.fyi/topic/machine-learning.md), [Multimodal](https://yomu.fyi/topic/multimodal.md)

A walkthrough of how a 3D CT model turns a voxel volume into a structured diagnostic report: isotropic resampling, 3D patch tokens, spatial encoding, and language-model reasoning.

### [How BioNeMo Turns a Target List Into Folded Structures](https://yomu.fyi/visual-explainers/how-bionemo-turns-a-target-list-into-folded-structures.md)
- Type: How it works
- Tags: [Benchmark](https://yomu.fyi/topic/benchmark.md), [BioNeMo](https://yomu.fyi/topic/bionemo.md), [GPU](https://yomu.fyi/topic/gpu.md), [Inference](https://yomu.fyi/topic/inference.md), [Life Sciences](https://yomu.fyi/topic/life-sciences.md), [NVIDIA](https://yomu.fyi/topic/nvidia.md)

BioNeMo Inference Runtime runs one pipeline per target: parse, tokenize, generate features, infer on a GPU replica, and write a structure. This diagram traces those stages and the throughput trade-off.

### [Bazel in the Inner Loop: From Monorepo Graph to Focused Sync](https://yomu.fyi/visual-explainers/bazel-in-the-inner-loop-from-monorepo-graph-to-focused-sync.md)
- Type: How it works
- Tags: [Architecture](https://yomu.fyi/topic/architecture.md), [Bazel](https://yomu.fyi/topic/bazel.md), [Caching](https://yomu.fyi/topic/caching.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md)

See how Bazel’s dependency graph can separate build scope from IDE scope, helping engineers move through large monorepos without syncing every module.

### [Authorization Is a Runtime Decision](https://yomu.fyi/visual-explainers/authorization-is-a-runtime-decision.md)
- Type: How it works
- Tags: [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Auditability](https://yomu.fyi/topic/auditability.md), [Authentication](https://yomu.fyi/topic/authentication.md), [Authorization](https://yomu.fyi/topic/authorization.md), [OAuth2](https://yomu.fyi/topic/oauth2.md)

See how an agent request becomes an allowed or denied tool action through identity context, policy checks, scoped credentials, and an auditable decision trail.

### [Apache Camel: From Many App Signals to Governed Actions](https://yomu.fyi/visual-explainers/apache-camel-from-many-app-signals-to-governed-actions.md)
- Type: How it works
- Tags: [Apache Camel](https://yomu.fyi/topic/apache-camel.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Automation](https://yomu.fyi/topic/automation.md), [Observability](https://yomu.fyi/topic/observability.md)

Apache Camel is shown as the integration path that brings application actions into one request workflow. The diagram clarifies real-time versus scheduled ingestion, mapping, merging, authorization, and audit.

### [Axum at the Trust Boundary: From Request to Protected Response](https://yomu.fyi/visual-explainers/axum-at-the-trust-boundary-from-request-to-protected-response.md)
- Type: How it works
- Tags: [API](https://yomu.fyi/topic/api.md), [Authentication](https://yomu.fyi/topic/authentication.md), [Axum](https://yomu.fyi/topic/axum.md), [OAuth 2.0](https://yomu.fyi/topic/oauth-2-0.md), [Rust](https://yomu.fyi/topic/rust.md)

Axum is a Rust web framework for composing routes, middleware, and extractors. This explainer shows how different login flows become verified identity before a handler responds.

### [The Token’s Route: From Auth0 Login to API Authorization](https://yomu.fyi/visual-explainers/the-token-s-route-from-auth0-login-to-api-authorization.md)
- Type: How it works
- Tags: [API](https://yomu.fyi/topic/api.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Auth0](https://yomu.fyi/topic/auth0.md), [Authentication](https://yomu.fyi/topic/authentication.md), [OAuth2](https://yomu.fyi/topic/oauth2.md), [OIDC](https://yomu.fyi/topic/oidc.md)

See how an Auth0 login becomes an API decision: redirect the user, issue the right token, validate its claims, and apply audience, scope, and access policies.

### [How Angular's Template Compiler Bridges Components and the DOM](https://yomu.fyi/visual-explainers/how-angular-s-template-compiler-bridges-components-and-the-dom.md)
- Type: How it works
- Tags: [Angular](https://yomu.fyi/topic/angular.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md), [TypeScript](https://yomu.fyi/topic/typescript.md)

Angular compiles component templates into executable JavaScript that manages the DOM efficiently. Learn the pipeline from TypeScript decorators through template parsing, code generation, and runtime rendering.

### [How Apache Flink Processes Streaming Data](https://yomu.fyi/visual-explainers/how-apache-flink-processes-streaming-data.md)
- Type: How it works
- Tags: [Apache Flink](https://yomu.fyi/topic/apache-flink.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Data Pipelines](https://yomu.fyi/topic/data-pipelines.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Streaming](https://yomu.fyi/topic/streaming.md)

Apache Flink is a distributed stream-processing framework that ingests continuous data, applies transformations in parallel, and outputs results with fault tolerance and low latency.

### [Apache Beam: Unified Batch and Stream Processing](https://yomu.fyi/visual-explainers/apache-beam-unified-batch-and-stream-processing.md)
- Type: How it works
- Tags: [Apache Beam](https://yomu.fyi/topic/apache-beam.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md), [Data Pipelines](https://yomu.fyi/topic/data-pipelines.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Streaming](https://yomu.fyi/topic/streaming.md)

Apache Beam is a unified programming model for batch and stream data processing. Learn how it handles event time, watermarks, and windowing to process data reliably at scale.

### [How Apache Arrow Moves Data Without Copies](https://yomu.fyi/visual-explainers/how-apache-arrow-moves-data-without-copies.md)
- Type: How it works
- Tags: [Apache Arrow](https://yomu.fyi/topic/apache-arrow.md), [Apache Spark](https://yomu.fyi/topic/apache-spark.md), [Data Analytics](https://yomu.fyi/topic/data-analytics.md), [Databases](https://yomu.fyi/topic/databases.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md)

Apache Arrow is a columnar in-memory format that lets databases, analytics engines, and Python libraries share data without serialization overhead or format conversion, cutting memory peaks and speeding up common workflows.

[Older explainers](https://yomu.fyi/visual-explainers/category/how-it-works/page/2.md)
