---
title: "Visual Explainers — page 7"
description: "Visual introductions to the engineering concepts behind the tools we use."
---

# Visual Explainers — page 7
> Visual introductions to the engineering concepts behind the tools we use.

## Visual Explainers

### [How to Build an ASL Gloss Workflow That Keeps Context](https://yomu.fyi/visual-explainers/how-to-build-an-asl-gloss-workflow-that-keeps-context.md)
- Type: How to
- Tags: [Accessibility](https://yomu.fyi/topic/accessibility.md), [AI](https://yomu.fyi/topic/ai.md), [Architecture](https://yomu.fyi/topic/architecture.md), [ASL](https://yomu.fyi/topic/asl.md)

Learn a practical workflow for translating English discourse into ASL gloss while preserving spatial references, question-answer structure, and consistent concept-to-gloss mappings.

### [ARM Is a Stack Decision, Not a CPU Checkbox](https://yomu.fyi/visual-explainers/arm-is-a-stack-decision-not-a-cpu-checkbox.md)
- Type: Architecture
- Tags: [Architecture](https://yomu.fyi/topic/architecture.md), [ARM](https://yomu.fyi/topic/arm.md), [Cloud](https://yomu.fyi/topic/cloud.md), [Edge Computing](https://yomu.fyi/topic/edge-computing.md), [GPU](https://yomu.fyi/topic/gpu.md), [Performance](https://yomu.fyi/topic/performance.md)

An architecture view of ARM deployments, from workload fit and software support to platform choice, showing where performance, memory, storage, and operations shape the decision.

### [Apple Integration Is a Boundary, Not a Feature](https://yomu.fyi/visual-explainers/apple-integration-is-a-boundary-not-a-feature.md)
- Type: What is it?
- Tags: [Apple](https://yomu.fyi/topic/apple.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Authentication](https://yomu.fyi/topic/authentication.md), [iOS](https://yomu.fyi/topic/ios.md)

Apple integrations are boundary designs: native capability, server-side mapping, and trust checks must meet a platform-agnostic product layer. See where each responsibility belongs.

### [Apache Pinot: From Event Stream to Resilient Query](https://yomu.fyi/visual-explainers/apache-pinot-from-event-stream-to-resilient-query.md)
- Type: Architecture
- Tags: [Apache Flink](https://yomu.fyi/topic/apache-flink.md), [Apache Pinot](https://yomu.fyi/topic/apache-pinot.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Kafka](https://yomu.fyi/topic/kafka.md), [Scalability](https://yomu.fyi/topic/scalability.md), [Streaming](https://yomu.fyi/topic/streaming.md)

Apache Pinot is a distributed real-time OLAP datastore for low-latency analytics. This architecture view shows how streams, processing, partitioning, indexed storage, and replica-aware serving fit together.

### [Analytics Is a Signal-Selection Problem](https://yomu.fyi/visual-explainers/analytics-is-a-signal-selection-problem.md)
- Type: Comparison
- Tags: [Analytics](https://yomu.fyi/topic/analytics.md), [Data Analytics](https://yomu.fyi/topic/data-analytics.md), [Data Pipelines](https://yomu.fyi/topic/data-pipelines.md), [Decision-Making](https://yomu.fyi/topic/decision-making.md)

Compare social listening with search intelligence to see which signals answer questions about perception, demand, and campaign impact—and when combining them is more useful.

### [The SQS Decision Most Diagrams Skip: Normal Work vs. Broken Work](https://yomu.fyi/visual-explainers/the-sqs-decision-most-diagrams-skip-normal-work-vs-broken-work.md)
- Type: Comparison
- Tags: [Amazon SQS](https://yomu.fyi/topic/amazon-sqs.md), [Architecture](https://yomu.fyi/topic/architecture.md), [AWS](https://yomu.fyi/topic/aws.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md), [Reliability](https://yomu.fyi/topic/reliability.md)

Amazon SQS connects producers and workers, but its real design test is failure. Compare the processing path with the signals and controls needed when queue operations break.

### [Before You Ship Nova, Set Four Gates](https://yomu.fyi/visual-explainers/before-you-ship-nova-set-four-gates.md)
- Type: How to
- Tags: [AI](https://yomu.fyi/topic/ai.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Amazon Nova](https://yomu.fyi/topic/amazon-nova.md), [Architecture](https://yomu.fyi/topic/architecture.md), [LLMs](https://yomu.fyi/topic/llm.md)

A practical checklist for putting Amazon Nova into an application: choose nova-lite or nova-pro by workload, expose tools, and verify context, modality, region, and cost constraints.

### [Agentforce Actions: Where Should the Work Run?](https://yomu.fyi/visual-explainers/agentforce-actions-where-should-the-work-run.md)
- Type: Trade-offs
- Tags: [Agentforce](https://yomu.fyi/topic/agentforce.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [API](https://yomu.fyi/topic/api.md), [Salesforce](https://yomu.fyi/topic/salesforce.md)

Agentforce selects actions to complete a task; this explainer weighs native record updates against external services so engineers can place each responsibility sensibly.

### [The Boundary ActiveAdmin Forces: HTML Admin vs API Controllers](https://yomu.fyi/visual-explainers/the-boundary-activeadmin-forces-html-admin-vs-api-controllers.md)
- Type: Comparison
- Tags: [ActiveAdmin](https://yomu.fyi/topic/activeadmin.md), [API](https://yomu.fyi/topic/api.md), [Architecture](https://yomu.fyi/topic/architecture.md), [JavaScript](https://yomu.fyi/topic/javascript.md), [Ruby on Rails](https://yomu.fyi/topic/ruby-on-rails.md)

ActiveAdmin needs a full Rails web boundary, while API-only endpoints need a lean controller. Compare the two paths to see where sessions, assets, and browser protections belong.

### [Active Storage Is a Boundary Decision](https://yomu.fyi/visual-explainers/active-storage-is-a-boundary-decision.md)
- Type: Trade-offs
- Tags: [Active Storage](https://yomu.fyi/topic/active-storage.md), [Architecture](https://yomu.fyi/topic/architecture.md), [Object Storage](https://yomu.fyi/topic/object-storage.md), [Rails](https://yomu.fyi/topic/rails.md), [S3](https://yomu.fyi/topic/s3.md)

See how Active Storage balances local simplicity, durable object storage, and preview-processing dependencies so you can choose the right boundary for a Rails file workflow.

### [A2UI Implementation Checkpoints: Keep Agents and Rendering in Their Lanes](https://yomu.fyi/visual-explainers/a2ui-implementation-checkpoints-keep-agents-and-rendering-in-their-lanes.md)
- Type: How to
- Tags: [A2UI](https://yomu.fyi/topic/a2ui.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [Architecture](https://yomu.fyi/topic/architecture.md), [MCP](https://yomu.fyi/topic/mcp.md)

A practical guide to applying A2UI: define the component boundary, separate tool data from UI resources, choose native or embedded rendering, and verify the action path.

### [Deploying .NET 10 on Heroku: A Practical How-To](https://yomu.fyi/visual-explainers/deploying-net-10-on-heroku-a-practical-how-to.md)
- Type: How to
- Tags: [ASP.NET Core](https://yomu.fyi/topic/asp-net-core.md), [CI/CD](https://yomu.fyi/topic/ci-cd.md), [Heroku](https://yomu.fyi/topic/heroku.md), [Migrations](https://yomu.fyi/topic/migration.md), [.NET](https://yomu.fyi/topic/dotnet.md)

Learn the step-by-step process for deploying .NET 10 applications to Heroku, from buildpack detection to SDK pinning, and understand the lifecycle of .NET LTS releases.

### [How to wire a remote agent into your workflow with A2A](https://yomu.fyi/visual-explainers/how-to-wire-a-remote-agent-into-your-workflow-with-a2a.md)
- Type: How to
- Tags: [A2A](https://yomu.fyi/topic/a2a.md), [Agent Development Kit](https://yomu.fyi/topic/agent-development-kit.md), [AI Agents](https://yomu.fyi/topic/ai-agents.md), [API](https://yomu.fyi/topic/api.md), [MCP](https://yomu.fyi/topic/mcp.md)

A2A lets agents discover each other and hand off tasks over JSON-RPC 2.0. This guide walks through exposing an Agent Card, sending typed messages, connecting a remote service, and routing failures to a human review checkpoint.

### [The Adoption Flywheel: From Experimentation to Scaled Use](https://yomu.fyi/visual-explainers/the-adoption-flywheel-from-experimentation-to-scaled-use.md)
- Type: Architecture
- Tags: [Adoption](https://yomu.fyi/topic/adoption.md), [AI](https://yomu.fyi/topic/ai.md), [AI Literacy](https://yomu.fyi/topic/ai-literacy.md), [Automation](https://yomu.fyi/topic/automation.md), [Developer Experience](https://yomu.fyi/topic/developer-experience.md)

Adoption moves through experimentation, measurement, and reinforcement loops. Learn how leading companies build momentum from pilot programs into enterprise-wide habits and measurable business impact.

### [Apache Iceberg vs. Hive: The Table Format Trade-off](https://yomu.fyi/visual-explainers/apache-iceberg-vs-hive-the-table-format-trade-off.md)
- Type: Comparison
- Tags: [Apache Iceberg](https://yomu.fyi/topic/apache-iceberg.md), [Databases](https://yomu.fyi/topic/databases.md), [Data Engineering](https://yomu.fyi/topic/data-engineering.md), [Data Warehousing](https://yomu.fyi/topic/data-warehousing.md), [Distributed Systems](https://yomu.fyi/topic/distributed-systems.md)

Apache Iceberg replaces Hive's partition-based metadata with a versioned catalog layer, trading operational simplicity for ACID guarantees, schema evolution, and cross-engine compatibility.

### [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.

### [Anycast: One IP, Many Locations](https://yomu.fyi/visual-explainers/anycast-one-ip-many-locations.md)
- Type: What is it?
- Tags: [Anycast](https://yomu.fyi/topic/anycast.md), [Architecture](https://yomu.fyi/topic/architecture.md), [BGP](https://yomu.fyi/topic/bgp.md), [DNS](https://yomu.fyi/topic/dns.md), [High Availability](https://yomu.fyi/topic/high-availability.md)

Anycast announces a single IP address from multiple geographic locations so routers automatically direct users to the nearest server, improving latency and resilience without client changes.

[Newer explainers](https://yomu.fyi/visual-explainers/page/6.md) · [Older explainers](https://yomu.fyi/visual-explainers/page/8.md)