Skip to main content
Back to Tags

Performance

345 items tagged with "performance"

Filter by type:

Standards4

Standard

MessagePack 2.3

MessagePack is a binary serialization format crucial for efficient data interchange in migration projects. By reducing data size and ensuring compatibility across various programming languages, it mitigates risks associated with data loss and enhances performance during migrations. Adhering to MessagePack standards can streamline your migration process and maintain data integrity.

Standard

Rust 1.78 Edition 2024

Migrating systems that utilize Rust requires adherence to its safety and performance standards. By leveraging Rust's ownership model, error handling capabilities, and robust tooling, teams can ensure a successful transition while mitigating common challenges. Following these guidelines will lead to safer, more reliable applications post-migration.

Standard

TypeScript 5.4 Spec

Adhering to Microsoft standards during software migrations is essential for ensuring security, performance, and regulatory compliance. By understanding these standards and implementing best practices, teams can navigate migration complexities effectively, minimizing risks and maximizing efficiency.

Standard

Erlang/OTP 26

Understanding and adhering to Ericsson's technical standards is essential for successful software migrations. These standards provide a framework for ensuring data protection, interoperability, and performance, thereby mitigating risks and enhancing efficiency. By following best practices and leveraging appropriate tools, teams can navigate the complexities of migration while maintaining compliance with industry standards.

Patterns31

Pattern

Object Pool

Reuses a set of pre-initialized, expensive-to-create objects from a managed pool instead of creating and destroying them on demand, improving performance.

Pattern

Lazy Initialization

Defers the creation or computation of an object until the first time it is actually needed, avoiding upfront cost for resources that may never be used.

Pattern

Flyweight

Minimizes memory use by sharing as much data as possible between many similar objects, separating intrinsic shared state from extrinsic context-specific state.

Pattern

Aggregator

A component that invokes multiple services and combines their responses into a single consolidated result for the caller.

Pattern

Gateway Aggregation

Uses a gateway to combine multiple backend requests into one, so clients make a single call instead of many.

Pattern

Sharding

Horizontally partitions a data store into independent shards so capacity and load scale beyond a single node.

Pattern

Scatter-Gather

Broadcasts a request to multiple recipients in parallel, then aggregates their replies into a single response.

Pattern

Cache-Aside

Load data into a cache on demand from a data store to improve read performance and reduce load on the backing store.

Pattern

Throttling

Control the consumption of resources by an instance, tenant, or service so a system stays within capacity under load.

Pattern

Claim Check

Store a large message payload externally and pass only a reference through the messaging system to avoid moving bulky data.

Pattern

Valet Key

Issue a client a token granting scoped, time-limited direct access to a resource, offloading data transfer from the application.

Pattern

Geode

Deploy independent geographically distributed nodes that each serve any request, placing compute close to users worldwide.

Pattern

Static Content Hosting

Serve static assets from storage or a CDN instead of application servers to cut load, latency, and cost.

Pattern

Index Table

Create secondary index tables over data stores queried by non-key fields to speed up lookups that would otherwise scan.

Pattern

Materialized View

Precompute and store read-optimized views of data so expensive queries become fast lookups against ready-made results.

Pattern

Rate Limiting

Constrain the rate of operations against a service or resource to stay within quotas and avoid throttling or overload.

Pattern

Message Filter

Lets only messages meeting specified criteria pass through a channel and silently discards the rest, so consumers receive only relevant messages.

Pattern

Polling Consumer

A consumer that explicitly checks a channel for messages on its own schedule, controlling exactly when and how fast it receives them.

Pattern

Read-Through Cache

A caching strategy where the cache itself loads missing data from the backing store on a miss, so application code reads only from the cache.

Pattern

Write-Through Cache

A caching strategy where every write goes to the cache and the backing store synchronously, keeping the two consistent at the cost of write latency.

Pattern

Write-Behind Cache

A caching strategy where writes update the cache immediately and are flushed to the backing store asynchronously, maximizing write throughput at the cost of durability.

Pattern

Refresh-Ahead Cache

A caching strategy that proactively reloads hot entries before they expire, so reads of popular keys never pay miss latency.

Pattern

Materialized View

A precomputed, stored result set that trades storage and refresh cost for fast reads of expensive queries, aggregations, or denormalized projections.

Pattern

Producer-Consumer

A concurrency pattern where producers place work on a shared bounded queue and consumers process it independently, decoupling rates and smoothing load.

Pattern

Thread Pool

A concurrency pattern that reuses a fixed set of worker threads to execute many tasks, avoiding per-task thread creation cost and bounding concurrency.

Pattern

Reactor

An event-handling pattern that demultiplexes I/O events on one or few threads and dispatches them synchronously to registered handlers, enabling scalable non-blocking servers.

Pattern

Hedged Requests

Sends a duplicate request to another replica after a delay, taking whichever response returns first to cut tail latency from slow servers.

Pattern

Request Coalescing

Merges multiple concurrent identical requests into a single backend call and shares the result, preventing duplicate work and cache-stampede overload.

Pattern

Island Architecture

Renders a page as mostly static HTML with isolated interactive 'islands' that hydrate independently, minimizing JavaScript shipped to the browser.

Pattern

Pagination

Splits a large result set into smaller pages so APIs and UIs can return and traverse data incrementally instead of loading everything at once.

Pattern

Token Bucket (Rate Limiting)

A rate-limiting algorithm where requests consume tokens refilled at a steady rate, allowing controlled bursts while capping the long-run request rate.

Anti-Patterns37

Anti-Pattern

Premature Optimization

Optimizing code or architecture before understanding actual performance requirements

Anti-Pattern

N+1 Query Problem

Loading a list, then firing one extra query per row to fetch related data, turning a single page load into hundreds of round-trips.

Anti-Pattern

SELECT * Everywhere

Querying all columns by default instead of naming the ones you need, wasting I/O and creating brittle coupling to schema order and shape.

Anti-Pattern

Premature Denormalization

Duplicating data across tables for speed before any measured need, creating update anomalies and integrity bugs to solve a problem you may not have.

Anti-Pattern

Over-Normalization

Splitting data into so many tables that every read requires a sprawl of joins, hurting performance and readability with no integrity benefit.

Anti-Pattern

Missing Indexes

Querying large tables with no supporting index, forcing full scans that work in testing and collapse under production data volume.

Anti-Pattern

Index Overuse

Adding an index for every column just in case, bloating storage and slowing every write while most indexes are never used by the planner.

Anti-Pattern

Polling the Database

Repeatedly querying a table on a tight loop to detect changes instead of using events or notifications, wasting resources and adding latency.

Anti-Pattern

Chatty Data Access

Making many fine-grained round-trips to the database for one logical operation, so network latency dominates and throughput collapses under load.

Anti-Pattern

No Connection Pooling

Opening a fresh database connection per request or query and closing it after, paying high handshake cost and exhausting connection limits under load.

Anti-Pattern

Unbounded Result Sets

Querying without a LIMIT and loading entire growing tables into memory, so a query that was fine at launch crashes the app as data accumulates.

Anti-Pattern

Busy-Waiting (Spin-Waiting)

Repeatedly polling a condition in a tight loop instead of blocking, burning CPU cycles while waiting for an event that the scheduler could deliver for free.

Anti-Pattern

Lock Contention

Many threads competing for the same lock, serializing work that should run in parallel and turning a multicore machine into an expensive single-core one.

Anti-Pattern

Deadlock-Prone Locking

Acquiring multiple locks in inconsistent orders so two threads can each hold one lock while waiting for the other, freezing both forever.

Anti-Pattern

Broken Double-Checked Locking

A lazy-initialization idiom that checks a field outside a lock, locks, then checks again — but without proper memory barriers it returns partially constructed objects.

Anti-Pattern

Thread-Per-Request Overload

Spawning a dedicated OS thread for every incoming request, so concurrency is capped by thread count and memory, collapsing under load instead of degrading gracefully.

Anti-Pattern

Blocking the Event Loop

Running CPU-heavy or synchronous work on a single-threaded event loop, stalling every other in-flight request until it finishes.

Anti-Pattern

Synchronous-Over-Async (sync-over-async)

Blocking a thread to wait on an asynchronous operation's result, combining the costs of both models and risking thread-pool starvation or deadlock.

Anti-Pattern

Chatty I/O

Making many small, fine-grained remote or storage calls where a few coarse-grained calls would do, multiplying latency and overhead per operation.

Anti-Pattern

N+1 Network Calls

Fetching a list, then making one additional remote call per item to enrich it, so a single logical operation fans out into N+1 dependency calls.

Anti-Pattern

Memory Leak

Allocating memory that is never released because references are unintentionally retained, so usage grows without bound until the process slows, thrashes, or crashes.

Anti-Pattern

Unbounded Cache

A cache with no size limit, eviction, or expiry that grows until it consumes all memory and turns a performance optimization into an out-of-memory failure.

Anti-Pattern

Cache Stampede (Dogpile Effect)

When a hot cache entry expires, many concurrent requests all miss and recompute it at once, hammering the backing store and amplifying load instead of absorbing it.

Anti-Pattern

Retry Storm

Aggressive, uncoordinated retries during a partial outage that multiply traffic against an already-struggling dependency and turn a blip into a full collapse.

Anti-Pattern

Thundering Herd

Many clients or threads waking and acting at the same instant — on a recovery, a timer, or a wakeup — creating a synchronized load spike that overwhelms the resource they target.

Anti-Pattern

Head-of-Line Blocking

A single slow or stuck item at the front of a strictly ordered queue holds up everything behind it, even when the later items are unrelated and ready to proceed.

Anti-Pattern

Hot Partition (Hot Shard)

A partitioning key that sends a disproportionate share of traffic to one shard, overloading it while the rest sit idle and capping the system at one node's throughput.

Anti-Pattern

False Sharing

Independent variables that happen to live on the same CPU cache line, so updates by different cores invalidate each other's caches and silently destroy multicore performance.

Anti-Pattern

Missing Back-Pressure

A producer that pushes work faster than the consumer can handle, with no mechanism to slow it down, so queues grow unbounded until memory or the downstream collapses.

Anti-Pattern

Resource Leak

Acquiring file handles, sockets, connections, or threads without reliably releasing them, so a finite pool is exhausted and the application stops being able to do work.

Anti-Pattern

Over-Caching

Adding caches everywhere to chase speed, multiplying staleness, invalidation bugs, and operational complexity for marginal gains that profiling never justified.

Anti-Pattern

Premature Scaling

Building for massive scale before there is load to justify it, paying the cost and complexity of distributed systems to solve problems the product does not yet have.

Anti-Pattern

Under-Provisioning

Allocating too little capacity to save money, leaving workloads starved so they slow down, fail, or fall over under load.

Anti-Pattern

Slow Test Suite

A test suite so slow that developers stop running it locally and feedback arrives too late, encouraging skipped tests and large risky batches.

Anti-Pattern

Chatty API

An API design that forces clients to make many small round trips to complete one task, harming latency, scalability, and battery life.

Anti-Pattern

Overfetching and Underfetching

Endpoints that return too much data or too little, forcing clients to waste bandwidth or make extra calls to assemble what they need.

Anti-Pattern

Missing Pagination (Unbounded Result Sets)

Collection endpoints that return all records at once with no pagination, causing huge payloads, slow queries, and out-of-memory failures as data grows.

Tutorials17

Tutorial

Migrating from Express to Fastify

Step-by-step tutorial for migrating a Node.js Express application to Fastify for better performance

Tutorial

Implementing Redis Caching in Node.js

Add Redis caching to your Node.js application for improved performance

Tutorial

How to set Kubernetes resource requests and limits correctly

Right-size CPU and memory requests and limits to improve scheduling, stability, and Quality of Service.

Tutorial

How to host a static site on Amazon S3 with CloudFront

Serve a static website from an S3 bucket behind the CloudFront CDN with HTTPS and global caching.

Tutorial

How to host a static site on Azure with Front Door

Serve static content from Azure Blob Storage behind Azure Front Door for global delivery and HTTPS.

Tutorial

How to speed up CI builds with caching

Cache dependencies and build outputs in CI to cut pipeline time, with correct cache keys and invalidation.

Tutorial

How to design and tune PostgreSQL indexes for query performance

Find slow queries with EXPLAIN, choose the right index types, and verify gains so reads stay fast without bloating writes.

Tutorial

How to implement the cache-aside pattern with Redis

Add a Redis read-through cache with TTLs and safe invalidation to reduce database load, including stampede protection.

Tutorial

How to partition a large PostgreSQL table by range

Use declarative range partitioning to split a large table by time, improving query pruning, maintenance, and data retention.

Tutorial

How to write and run a PySpark batch job

Build a PySpark job that reads, transforms, and writes data using the DataFrame API, then run it with spark-submit.

Tutorial

How to store and query time-series data with TimescaleDB

Turn a PostgreSQL table into a TimescaleDB hypertable, add continuous aggregates, and apply retention for time-series workloads.

Tutorial

How to convert data to Apache Parquet for analytics

Convert CSV or JSON to columnar Parquet with partitioning and compression to speed up and shrink analytic queries.

Tutorial

How to design Elasticsearch index mappings and analyzers

Define explicit Elasticsearch mappings, configure analyzers for text search, and index documents for fast, accurate queries.

Tutorial

How to model an analytics table in ClickHouse

Create a MergeTree table in ClickHouse with the right ordering key and partitioning, then load data and run fast aggregations.

Tutorial

How to Add Cursor-Based Pagination to a REST API

Replace offset pagination with stable cursor pagination, return navigation links, and keep results consistent under concurrent writes.

Tutorial

How to add semantic search with embeddings and a vector database

Add meaning-based search to an app by generating text embeddings and querying a vector database for nearest neighbors.

Tutorial

Cache Vibgrate Between CI Runs

Persist the Vibgrate cache directory across CI runs so repeated scans reuse prior work and finish faster.

Blueprints9

Blueprint

Monolith to Go Service Extraction Blueprint

Extract performance-critical capabilities from a monolith into standalone Go services with gRPC contracts and container-native deployment.

Blueprint

Java 8 to Java 21 LTS Modernization Blueprint

Upgrade long-lived Java 8 applications to the Java 21 LTS runtime, adopting modern language features and resolving JDK module and API changes.

Blueprint

Stateful Monolith to Stateless Services Blueprint

Re-architect a session-bound stateful backend into horizontally scalable stateless services with externalized session and cache state.

Blueprint

jQuery to Vue Blueprint

Replace imperative jQuery DOM manipulation with a declarative Vue 3 component architecture, island by island.

Blueprint

Client-Rendered SPA to Next.js SSR Blueprint

Convert a client-rendered React SPA to server-side rendering with the Next.js App Router for faster loads and better SEO.

Blueprint

Vue SPA to Nuxt SSR Blueprint

Convert a client-rendered Vue 3 SPA to server-rendered Nuxt 3 for improved performance, SEO, and routing conventions.

Blueprint

Silverlight / Flash to HTML5 Blueprint

Replace end-of-life Silverlight and Flash applications with modern HTML5, CSS, and JavaScript using web-standard APIs.

Blueprint

Desktop App to Progressive Web App Blueprint

Convert a legacy desktop application into an installable, offline-capable Progressive Web App backed by a modern API.

Blueprint

jQuery to React SPA Blueprint

Replace a jQuery-driven multi-page or hybrid frontend with a structured React single-page application.

Reference Architectures17

Reference Architecture

Multi-Region Active-Active

Architecture for globally distributed applications with active-active failover

Reference Architecture

Autoscaling Web Tier on AWS

A classic three-tier web application on AWS with an autoscaling compute tier behind a load balancer and a managed relational database.

Reference Architecture

Batch and HPC on Azure

A scalable batch and high-performance computing platform on Azure Batch with spot compute, parallel storage, and a job scheduler.

Reference Architecture

Edge Compute and CDN Platform

A globally distributed edge platform running compute at CDN points of presence for ultra-low-latency personalization and API responses.

Reference Architecture

Real-Time Model Serving on GCP

A reference design for low-latency online inference on GCP using Vertex AI endpoints, autoscaling, and a feature lookup path for sub-100ms predictions.

Reference Architecture

Self-Hosted Open LLM Inference on Kubernetes

A reference design for serving open-weight LLMs on Kubernetes with GPU autoscaling, continuous batching, and an OpenAI-compatible API.

Reference Architecture

Global Edge and CDN Architecture

Multi-CDN edge design that caches content, runs logic at the edge, and routes users to the nearest healthy origin.

Reference Architecture

gRPC Service Mesh for Internal APIs

A high-performance internal API platform using gRPC over a service mesh for typed, low-latency service-to-service calls.

Reference Architecture

Global Edge API Gateway

A globally distributed edge gateway that authenticates, caches, and routes API traffic close to users across multiple regions.

Reference Architecture

Jamstack Static Site with Edge Functions

Pre-rendered static front end served from a global CDN, with dynamic behavior handled by edge functions and serverless APIs.

Reference Architecture

Server-Side Rendered Web App (Next.js) on Cloud

A Next.js application rendered on the server and streamed to the browser, backed by managed compute, caching, and a relational database.

Reference Architecture

Real-Time Collaboration Application

A web app where many users edit shared documents concurrently, synchronized over WebSockets with conflict-free replicated data.

Reference Architecture

Content Platform with Global CDN

A high-traffic content site delivering articles and media worldwide through a multi-tier CDN cache in front of a publishing backend.

Reference Architecture

Progressive Web App (PWA)

An installable, offline-capable web app using service workers, a cache strategy, and push notifications to behave like a native app.

Reference Architecture

Video Streaming Platform

A platform that ingests, transcodes, packages, and delivers on-demand and live video at scale using adaptive bitrate over a CDN.

Reference Architecture

Edge-Rendered Web Platform

A web app rendered at CDN edge locations using lightweight serverless runtimes for low-latency dynamic pages worldwide.

Reference Architecture

Single-Page Application with API Backend

A client-rendered SPA served from a CDN that talks to a stateless REST API, with token-based auth and a managed database.

Checklists10

Checklist

NoSQL Data Modeling Review Checklist

A review checklist for validating NoSQL data models against access patterns, partitioning, and scalability before migration.

Checklist

Database Version Upgrade Checklist

Checks for upgrading a database engine to a new major version with minimal risk to data integrity and availability.

Checklist

GraphQL Migration Readiness Checklist

Readiness items for migrating a REST API or adding a GraphQL layer without losing performance, security, or observability.

Checklist

API Rate Limiting and Throttling Readiness Checklist

Verification items for designing fair, abuse-resistant rate limiting and throttling for a public or internal API.

Checklist

Frontend Framework Migration Readiness Checklist

Verify your team, codebase, and tooling are ready before migrating a frontend application from one framework or major version to another.

Checklist

Micro-Frontends Rollout Checklist

Validate architecture, ownership, and runtime integration before rolling out a micro-frontends architecture across teams.

Checklist

Server-Side Rendering Migration Checklist

Confirm rendering, data fetching, caching, and SEO are ready before migrating a client-rendered app to server-side rendering.

Checklist

Core Web Vitals Performance Review Checklist

Review a web application against Core Web Vitals to improve loading, interactivity, and visual stability for real users.

Checklist

Progressive Web App Readiness Checklist

Verify installability, offline behavior, performance, and security before shipping a Progressive Web App.

Checklist

Legacy Browser EOL Migration Checklist

Plan the removal of support for end-of-life browsers and modernize a web app's baseline without breaking key users.

Stacks25

Stack

JAMstack

JavaScript, APIs, Markup - Modern web architecture

Stack

Go Microservices Stack

Go, gRPC, Kubernetes, PostgreSQL - High-performance services

Stack

Rust WASM Stack

Rust, WebAssembly, Yew - High-performance web apps

Stack

SolidStart

A fullstack framework built on Solid's fine-grained reactivity, offering SSR, server functions, and high performance with a React-like API.

Stack

Qwik City

A resumable fullstack framework using Qwik and Qwik City to deliver instant-loading apps with near-zero JavaScript via lazy execution.

Stack

.NET Web API Stack

Modern C# backend stack using ASP.NET Core, Entity Framework Core, and SQL Server or PostgreSQL for high-performance cross-platform services.

Stack

FastAPI + SQLAlchemy Stack

Async Python backend stack using FastAPI, SQLAlchemy, and PostgreSQL for high-performance, type-hinted REST and ML-serving APIs.

Stack

Go + gRPC Stack

Compiled Go backend stack using gRPC and Protocol Buffers with PostgreSQL for fast, strongly-typed inter-service communication.

Stack

Go + Gin + Postgres Stack

Lightweight Go REST backend using the Gin web framework with PostgreSQL and Redis for fast, simple, high-throughput HTTP APIs.

Stack

Quarkus Cloud-Native Java Stack

Cloud-native Java backend using Quarkus with GraalVM native compilation and PostgreSQL for fast-starting, low-memory containerized services.

Stack

Micronaut JVM Microservices Stack

JVM microservices stack using Micronaut with ahead-of-time compilation and PostgreSQL for low-memory, fast-starting services and serverless functions.

Stack

Rust Axum/Actix Backend Stack

High-performance, memory-safe Rust backend using Axum or Actix with PostgreSQL for low-latency, resource-efficient services.

Stack

gRPC Service Mesh Stack

Microservices stack combining gRPC inter-service communication with a service mesh on Kubernetes for typed, observable, secure service-to-service traffic.

Stack

SvelteKit + Postgres

A full-stack SvelteKit application with server routes and a PostgreSQL database, delivering fast, lightweight web apps with minimal JavaScript.

Stack

Fastify + Prisma

A high-performance Node.js backend using Fastify with schema-based validation and Prisma ORM over PostgreSQL, built for low-overhead, type-safe APIs.

Stack

Gatsby + Headless CMS

A React-based static site generator that sources content from a headless CMS and APIs through GraphQL, producing fast, pre-built marketing and content sites.

Stack

Eleventy + Netlify

A lightweight, zero-runtime static site generator paired with Netlify hosting and functions, producing simple, fast sites with minimal JavaScript.

Stack

Hugo + CDN

A Go-powered static site generator known for extremely fast builds, paired with a global CDN to serve large content sites cheaply and quickly.

Stack

Vert.x Reactive Stack

A polyglot, event-driven toolkit on the JVM built around a non-blocking event loop and the reactor pattern for high-concurrency, low-latency services.

Stack

Play Framework (Scala)

A reactive, stateless web framework on the JVM written for Scala (and Java), built on Akka for non-blocking, high-throughput web applications and APIs.

Stack

Spring WebFlux Reactive

Spring's reactive, non-blocking web stack built on Project Reactor and Netty, for high-concurrency services that need backpressure and efficient resource use.

Stack

Rocket (Rust) Stack

An ergonomic, type-safe Rust web framework with compile-time route checking and request guards, paired with a database for fast, safe backends.

Stack

Axum + SQLx (Rust)

A modern async Rust backend built on the Tokio runtime with the Tower middleware ecosystem and compile-time-checked SQL via SQLx.

Stack

Gin + GORM

A fast, lightweight Go web stack pairing the Gin HTTP framework with the GORM ORM, popular for high-performance REST APIs and backend services.

Stack

Sentry + OpenTelemetry

An application monitoring stack pairing Sentry's error tracking and performance monitoring with OpenTelemetry instrumentation for vendor-neutral traces and metrics.

Comparisons37

Comparison

Cloudflare vs CloudFront

Cloudflare is an independent global edge platform with CDN, security, and edge compute; Amazon CloudFront is AWS's CDN, deeply integrated with the AWS ecosystem.

Comparison

Redis vs Memcached

Feature-rich in-memory data structure store versus a lean, multi-threaded distributed memory cache.

Comparison

Aurora vs RDS

Amazon's cloud-native, high-performance database engine versus standard managed RDS running stock database engines.

Comparison

Redis vs DynamoDB

An in-memory data store for ultra-low-latency caching and structures versus a durable, managed NoSQL database for scale.

Comparison

Go vs Rust

Two modern systems-oriented languages: Go optimizes for simplicity and fast development, Rust for memory safety without a garbage collector and maximum control.

Comparison

Go vs Java

Go offers a lean runtime and fast startup for cloud services, while Java brings a mature ecosystem, the JVM, and decades of enterprise tooling.

Comparison

Rust vs C++

Both target systems-level performance, but Rust enforces memory safety at compile time while C++ offers unmatched maturity and ecosystem at the cost of manual safety.

Comparison

Python vs Go

Python prioritizes expressiveness and a vast data/AI ecosystem, while Go prioritizes raw performance, concurrency, and lean deployment for services.

Comparison

Node.js vs Python

Two leading backend runtimes: Node.js offers event-driven, non-blocking I/O with JavaScript everywhere, while Python brings readability and a vast data ecosystem.

Comparison

PHP vs Node.js

Two popular web backends: PHP powers a huge share of the web with mature frameworks, while Node.js offers event-driven JavaScript across the full stack.

Comparison

Bun vs Node.js

Bun is a fast all-in-one JavaScript runtime and toolkit built on JavaScriptCore, while Node.js is the mature, ubiquitous V8-based standard.

Comparison

JVM vs GraalVM Native Image

Run JVM applications on the traditional HotSpot JVM with JIT, or compile them ahead-of-time to native images with GraalVM for fast startup and low memory.

Comparison

Go vs Node.js for APIs

For building HTTP and gRPC APIs, Go offers compiled performance and easy concurrency, while Node.js offers rapid development and full-stack JavaScript.

Comparison

Async/Await vs Threads

Two models for concurrency: cooperative asynchronous programming with an event loop, versus preemptive OS threads. Each suits different workloads.

Comparison

V8 vs JavaScriptCore

Two major JavaScript engines: Google's V8, powering Chrome and Node.js, and Apple's JavaScriptCore, powering Safari and Bun. Different design and tuning priorities.

Comparison

CPython vs PyPy

Two Python implementations: CPython is the reference interpreter with full compatibility, while PyPy uses a JIT compiler for major speedups on long-running code.

Comparison

OpenJDK vs GraalVM

Two JDK distributions: OpenJDK is the reference Java runtime, while GraalVM adds a high-performance JIT, ahead-of-time native compilation, and polyglot support.

Comparison

.NET vs .NET Framework

Modern .NET (formerly .NET Core) is the cross-platform, actively developed runtime, while .NET Framework is the legacy Windows-only platform now in maintenance.

Comparison

Rust vs Go for CLI Tools

Both produce single static binaries ideal for command-line tools: Go favors fast builds and simplicity, Rust favors performance, rich CLI libraries, and safety.

Comparison

C vs Rust for Systems Programming

C is the foundational systems language behind operating systems and embedded software, while Rust offers comparable control with compiler-enforced memory safety.

Comparison

Java Virtual Threads vs Reactive Programming

Two approaches to scalable concurrency on the JVM: Project Loom's virtual threads keep simple blocking code, while reactive programming uses non-blocking streams.

Comparison

Vue vs Svelte

Vue is a mature, progressive framework with a rich ecosystem; Svelte is a compiler that produces small, fast vanilla JavaScript with little runtime.

Comparison

Svelte vs SolidJS

Svelte compiles components to lean vanilla JS, while SolidJS uses fine-grained reactivity with a JSX syntax and no virtual DOM.

Comparison

Astro vs Next.js

Astro is a content-first framework that ships zero JS by default; Next.js is a full React app framework with rich interactivity and rendering modes.

Comparison

Angular vs Svelte

Angular is a full, opinionated enterprise framework; Svelte is a lean compiler that ships minimal runtime and concise components.

Comparison

React vs SolidJS

React popularized component UI with a virtual DOM and huge ecosystem; SolidJS uses similar JSX but fine-grained signals and no virtual DOM.

Comparison

Spring Boot vs Quarkus

Spring Boot is the mature, ubiquitous Java framework; Quarkus is a cloud-native, Kubernetes-first framework optimized for fast startup and low memory.

Comparison

Spring Boot vs Micronaut

Spring Boot uses runtime reflection and a huge ecosystem; Micronaut uses compile-time dependency injection for fast startup and low memory.

Comparison

React Native vs Flutter

React Native builds cross-platform apps with JavaScript and native UI; Flutter uses Dart and its own rendering engine for consistent, fast UIs.

Comparison

Flutter vs Native Development

Flutter builds cross-platform apps from one Dart codebase; native development uses platform SDKs (Swift/Kotlin) for maximum integration and performance.

Comparison

gRPC vs REST

gRPC is a contract-first, binary, HTTP/2 RPC framework; REST is a resource-oriented, text-based HTTP style. Both build service APIs.

Comparison

Fine-Tuning vs Prompt Engineering

Prompt engineering steers a model with instructions and examples in the context; fine-tuning changes the weights. Cost, control, and durability differ sharply.

Comparison

vLLM vs TGI

vLLM and Hugging Face Text Generation Inference (TGI) are high-throughput LLM serving engines. Both optimize GPU inference but differ in ecosystem and tuning focus.

Comparison

Embeddings vs Keyword Search

Embedding-based semantic search matches by meaning; keyword search matches by terms. Each handles different query types, and hybrid search often beats either alone.

Comparison

Batch vs Real-Time Inference

Batch inference processes data in scheduled bulk jobs; real-time inference serves predictions on demand. They trade latency against throughput, cost, and complexity.

Comparison

CPU vs GPU Inference

CPUs and GPUs both run ML inference. GPUs excel at parallel, large-model workloads; CPUs are cheaper and simpler for small models and low concurrency.

Comparison

Quantization vs Full Precision

Quantization stores model weights at lower bit-widths to cut memory and speed inference; full precision preserves maximum accuracy. The trade-off is size and speed versus fidelity.

Benchmarks82

Benchmark

TPC-C

The classic OLTP benchmark simulating an order-entry warehouse workload, measuring transactions per minute (tpmC) and price/performance.

Benchmark

TPC-E

An OLTP benchmark modeling a brokerage firm with realistic data and read-heavy transactions, reporting tpsE as a more representative successor to TPC-C.

Benchmark

YCSB

The Yahoo! Cloud Serving Benchmark for NoSQL and key-value stores, defining standard read/write workload mixes to compare throughput and latency.

Benchmark

sysbench

A scriptable, multi-threaded benchmark tool widely used for MySQL/PostgreSQL OLTP tests as well as CPU, memory, and file I/O microbenchmarks.

Benchmark

pgbench

PostgreSQL's built-in benchmarking tool that runs a TPC-B-like transaction load and custom scripts to measure transactions per second and latency.

Benchmark

HammerDB

An open-source database load-testing tool implementing TPROC-C and TPROC-H (TPC-C/TPC-H-derived) workloads across many relational engines.

Benchmark

BenchBase

An extensible Java framework (successor to OLTPBench) for benchmarking relational databases with many built-in workloads via a common JDBC harness.

Benchmark

ClickBench

An open benchmark for analytical databases using a single wide web-analytics table and 43 queries to compare cold and hot OLAP query latency.

Benchmark

TPCx-AI

An end-to-end machine-learning benchmark measuring the full data-science pipeline — ingestion, training, and serving — across multiple AI use cases.

Benchmark

JMH (Java Microbenchmark Harness)

The standard harness for writing reliable JVM microbenchmarks, widely used to measure data-processing and serialization library performance on the JVM.

Benchmark

TeraSort

A distributed sort benchmark that orders one terabyte (or more) of data on a cluster, measuring big-data engine throughput and shuffle efficiency.

Benchmark

Sort Benchmark

A long-running family of competitive sorting benchmarks (GraySort, MinuteSort, JouleSort) that rank systems on speed, cost, and energy for large-scale sorting.

Benchmark

dbt Pipeline Performance Benchmark

A category of benchmarks measuring transformation pipeline performance in dbt — model build time, warehouse compute cost, and incremental run efficiency.

Benchmark

OLTP vs OLAP Latency Benchmark

A comparative benchmark category contrasting transactional (OLTP) point-operation latency with analytical (OLAP) scan-and-aggregate latency to evaluate HTAP systems.

Benchmark

ANN-Benchmarks

The standard open benchmark for approximate nearest neighbor search, plotting recall against queries-per-second across vector index libraries and databases.

Benchmark

BigANN Benchmark

A billion-scale approximate nearest neighbor benchmark testing vector search algorithms on large data sets with constraints on memory, throughput, and recall.

Benchmark

Time-Series Ingestion Benchmark

A benchmark category measuring write throughput, query latency, and compression for time-series databases under high-cardinality metric and event ingestion.

Benchmark

Streaming Throughput Benchmark

A benchmark category for event-streaming platforms measuring producer/consumer throughput and end-to-end latency under sustained load and varying durability settings.

Benchmark

In-Memory Store Benchmark (memtier/redis-benchmark)

Benchmarks for in-memory data stores like Redis and Memcached, measuring operations per second and sub-millisecond latency under varied key/value and pipeline settings.

Benchmark

ETL/ELT Pipeline Throughput Benchmark

A benchmark category measuring data-integration pipeline performance — extraction and load throughput, transformation latency, and end-to-end freshness.

Benchmark

fio (Flexible I/O Tester)

The standard tool for benchmarking storage I/O, measuring IOPS, bandwidth, and latency across configurable read/write patterns, block sizes, and queue depths.

Benchmark

LDBC Social Network Benchmark

The standard benchmark for graph databases, measuring interactive transactional and analytical query performance over a realistic, correlated social-network graph.

Benchmark

SPEC CPU 2017

Industry-standard CPU benchmark suite measuring integer and floating-point compute performance under realistic, compute-bound workloads.

Benchmark

SPECjbb 2015

Java server benchmark modeling a supermarket company's transaction processing to measure JVM and server-side Java throughput and latency.

Benchmark

CoreMark

Compact, portable CPU benchmark from EEMBC designed to measure embedded and microcontroller core performance with a single comparable number.

Benchmark

Dhrystone

Classic synthetic integer benchmark that produces DMIPS, a historical and still-cited measure of general-purpose integer CPU performance.

Benchmark

Whetstone

Historic synthetic floating-point benchmark measuring scientific-style arithmetic performance, reported in MWIPS (millions of Whetstone instructions per second).

Benchmark

STREAM

Simple, portable benchmark measuring sustainable main-memory bandwidth for large vector operations, the standard metric for memory-bound performance.

Benchmark

Geekbench

Cross-platform benchmark measuring single-core and multi-core CPU performance plus GPU compute, widely used to compare phones, laptops, and servers.

Benchmark

LINPACK / HPL

Dense linear-algebra benchmark solving a large system of equations to measure peak floating-point throughput; HPL ranks the TOP500 supercomputers.

Benchmark

TechEmpower Web Framework Benchmarks

Open benchmark suite comparing web frameworks and platforms across standardized request types like JSON, single-query, and plaintext throughput.

Benchmark

wrk HTTP Benchmark

Modern, multithreaded HTTP load-testing tool that generates high request volume from a single machine and reports throughput and latency distribution.

Benchmark

k6 Load Testing

Developer-centric, scriptable load-testing tool using JavaScript scenarios to measure API and web performance with rich thresholds and metrics.

Benchmark

Apache JMeter

Mature, GUI-driven Java load-testing tool for simulating complex multi-protocol user scenarios and measuring throughput, latency, and error rates.

Benchmark

Gatling Load Testing

Scala-based, asynchronous load-testing tool with an expressive scenario DSL and detailed HTML reports for high-concurrency performance testing.

Benchmark

Locust Load Testing

Python-based, distributed load-testing tool where user behavior is defined in code, scaling to many workers for high-concurrency scenario testing.

Benchmark

ApacheBench (ab)

Simple, ubiquitous command-line HTTP benchmarking tool for quick single-endpoint throughput and latency measurement, bundled with Apache.

Benchmark

fio Storage I/O Benchmark

Flexible I/O tester for measuring storage device and filesystem performance across configurable read/write patterns, block sizes, and queue depths.

Benchmark

iperf Network Benchmark

Active network measurement tool that generates TCP, UDP, and SCTP traffic between two hosts to measure achievable bandwidth, jitter, and packet loss.

Benchmark

netperf Network Benchmark

Network performance tool measuring both bulk-transfer throughput and request/response transaction rates, used to characterize latency-sensitive workloads.

Benchmark

Phoronix Test Suite

Open-source, cross-platform benchmarking framework that automates hundreds of real-world tests and aggregates results for reproducible comparison.

Benchmark

Core Web Vitals

Google's set of user-centric web performance metrics, LCP, INP, and CLS, that quantify loading, interactivity, and visual stability of real page loads.

Benchmark

Lighthouse Performance

Google's open-source web auditing tool that runs synthetic page loads and produces a 0-100 performance score from lab metrics like LCP, TBT, and CLS.

Benchmark

Cold-Start Latency Benchmark

Measures the added latency when a serverless function or container must initialize from scratch before serving its first request after being idle.

Benchmark

Build-Time Benchmark

Measures how long it takes to compile and package software, a key developer-productivity and CI-cost metric across clean, incremental, and cached builds.

Benchmark

Container Startup Time Benchmark

Measures how quickly a container goes from launch to ready, covering image pull, runtime creation, and application readiness for scaling and resilience.

Benchmark

API P99 Latency Benchmark

Measures tail latency, the response time at the 99th percentile, to capture worst-case API responsiveness that averages hide and that users feel most.

Benchmark

HTTP/3 and QUIC Protocol Benchmark

Measures how the QUIC-based HTTP/3 transport compares to HTTP/2 over TCP on connection setup, throughput, and latency, especially on lossy networks.

Benchmark

Serverless Cold-Start Latency Benchmark

Measures the added latency when a serverless function must initialize a new execution environment before handling a request, across runtimes and platforms.

Benchmark

Autoscaling Responsiveness Benchmark

Measures how quickly and accurately an autoscaler adds or removes capacity in response to load changes, including reaction time, overshoot, and stabilization.

Benchmark

Cost-per-Request Benchmark

Measures the fully loaded cloud cost of serving a single unit of work, attributing compute, memory, network, and storage spend to throughput.

Benchmark

Cloud Storage Throughput Benchmark

Measures sustained read and write throughput, IOPS, and latency of cloud object, block, and file storage under varied access patterns and concurrency.

Benchmark

CDN Latency Benchmark

Measures content delivery network performance from many geographic vantage points, including edge latency, cache hit ratio, and origin offload.

Benchmark

Kubernetes Scheduling Latency Benchmark

Measures how quickly the Kubernetes scheduler places pods on nodes and how the control plane scales as pod, node, and churn counts grow.

Benchmark

Mobile App Startup Time Benchmark

Measures how quickly a mobile app becomes usable, distinguishing cold, warm, and hot starts and the time to first frame and first interaction.

Benchmark

Mobile Frame Rate and Jank Benchmark

Measures UI rendering smoothness on mobile, quantifying dropped frames, jank, and frame-time consistency against the display refresh budget.

Benchmark

Mobile Battery Usage Benchmark

Measures the energy a mobile app consumes per task and over time, attributing drain to CPU, network, GPU, location, and wakelocks.

Benchmark

Mobile App Bundle Size Benchmark

Measures the download and installed size of a mobile app and its components, tracking size by architecture, resources, and code to control bloat.

Benchmark

Geekbench Mobile Benchmark

A cross-platform CPU and compute benchmark widely used to compare mobile device processor performance via standardized single- and multi-core workloads.

Benchmark

CI Build Time (p95) Benchmark

Measures continuous-integration pipeline duration, focusing on the p95 build time and its phases, to quantify developer feedback latency.

Benchmark

MLPerf Training

Industry-standard benchmark suite measuring how fast hardware and software systems train machine-learning models to a fixed target quality.

Benchmark

MLPerf Inference

Benchmark suite measuring how fast and efficiently systems serve trained ML models under realistic latency and throughput constraints.

Benchmark

MLPerf Tiny

Benchmark suite for ultra-low-power machine learning on microcontrollers and embedded devices, measuring latency, energy, and accuracy.

Benchmark

DAWNBench

Stanford benchmark that measured end-to-end deep-learning training and inference by time-to-accuracy and cost, popularizing those metrics.

Benchmark

SPECjbb 2015

Standard Java server benchmark modeling a supermarket company's business logic to measure throughput and critical response-time performance.

Benchmark

SPECpower_ssj2008

Benchmark measuring server energy efficiency by reporting performance per watt across graduated load levels from idle to peak.

Benchmark

SPECjvm 2008

Benchmark suite measuring core Java Virtual Machine performance across compute-intensive workloads independent of application or hardware tuning.

Benchmark

SPEC OMP 2012

Benchmark suite measuring shared-memory parallel performance of OpenMP applications across scientific and engineering workloads.

Benchmark

HPCG

High Performance Conjugate Gradients benchmark measuring HPC system performance on memory-bound, sparse computations that mirror real applications.

Benchmark

HPL-AI / HPL-MxP

Mixed-precision LINPACK variant measuring supercomputer performance using low-precision arithmetic refined to full accuracy, reflecting AI hardware.

Benchmark

Graph500

Benchmark ranking supercomputers on data-intensive graph processing, measuring traversed edges per second instead of floating-point throughput.

Benchmark

GAP Benchmark Suite

Reference graph-algorithm benchmark suite providing optimized kernels and standard graphs to fairly compare graph-processing performance.

Benchmark

Computer Language Benchmarks Game

Long-running comparison of programming-language implementations on small algorithmic tasks, measuring runtime, memory, and code size.

Benchmark

Renaissance JVM Benchmark Suite

Modern JVM benchmark suite using real-world concurrent and parallel workloads to stress runtime optimization, GC, and JIT compilers.

Benchmark

DaCapo JVM Benchmark Suite

Long-established Java benchmark suite using real open-source application workloads to evaluate JVM, JIT, and garbage-collection performance.

Benchmark

SPECviewperf

Standard benchmark measuring professional graphics-workstation performance running real CAD, visualization, and content-creation application viewsets.

Benchmark

3DMark

Cross-platform graphics benchmark suite measuring GPU and gaming performance through standardized rendering tests and synthetic feature tests.

Benchmark

Unigine Superposition

GPU stress and benchmark tool using a detailed real-time scene to measure graphics performance, stability, and thermal behavior.

Benchmark

PassMark PerformanceTest

Whole-system PC benchmark suite measuring CPU, memory, disk, 2D, and 3D performance and aggregating them into comparable component scores.

Benchmark

UnixBench

Classic Unix and Linux system benchmark measuring overall performance through CPU, process, file I/O, and system-call tests aggregated into an index.

Benchmark

sysbench CPU Benchmark

CPU test mode of the sysbench tool measuring processor throughput via prime-number computation across single and multiple threads.

Benchmark

stress-ng

Configurable stress-test and micro-benchmark tool that loads CPU, memory, I/O, and kernel subsystems through hundreds of targeted stressors.

FAQs16

FAQ

Why is the scan taking a long time?

Slow scans are usually due to registry network calls. Try --concurrency 16 to increase parallel registry requests. For repeated scans, results are cac...

FAQ

What does the --changed-only flag do?

The --changed-only flag scans only files that have changed (typically detected via git diff). This speeds up scans in CI by skipping unchanged project...

FAQ

What is autoscaling in the cloud?

Autoscaling automatically adjusts the number of running resources, such as virtual machines, containers, or pods, in response to demand or defined met...

FAQ

What is the difference between normalization and denormalization?

Normalization organizes data to eliminate redundancy by splitting it into related tables, which reduces anomalies and keeps a single source of truth f...

FAQ

What is a database index and why does it matter?

An index is a separate data structure, usually a B-tree, that lets the database find rows matching a query without scanning the entire table. It drama...

FAQ

What is a materialized view?

A materialized view is a database object that stores the precomputed result of a query physically on disk, unlike a regular view which runs its query ...

FAQ

When should I use Redis?

Redis is an in-memory key-value data store known for very low latency, making it ideal as a cache in front of a slower primary database. Beyond cachin...

FAQ

What is columnar storage and why is it faster for analytics?

Columnar storage organizes data on disk by column rather than by row, so all values of a single column are stored together. Analytical queries that sc...

FAQ

What is data partitioning?

Partitioning divides a large table or dataset into smaller, manageable pieces based on a key such as date, region, or category. In databases it improv...

FAQ

What is rate limiting and how does it work?

Rate limiting caps how many requests a client may make in a given window to protect a service from overload, abuse, and runaway costs. Common algorith...

FAQ

What is the difference between HTTP/2 and HTTP/3?

HTTP/2 introduced multiplexing of multiple requests over a single TCP connection, header compression, and server push, reducing latency compared with ...

FAQ

What is the difference between TCP and UDP?

TCP is a connection-oriented transport protocol that guarantees ordered, reliable delivery using handshakes, acknowledgments, retransmission, and flow...

FAQ

What is a CDN?

A content delivery network (CDN) is a geographically distributed set of edge servers that cache and serve content close to users, reducing latency and...

FAQ

What is inference in machine learning?

Inference is the phase where a trained model is used to make predictions or generate output on new inputs, as opposed to training where the model lear...

FAQ

What is quantization in machine learning?

Quantization reduces the numerical precision of a model's weights and activations, for example from 32-bit floating point to 8-bit or 4-bit integers, ...

FAQ

What is the difference between compiled and interpreted languages?

A compiled language is translated ahead of time into machine code by a compiler, producing a standalone executable that the CPU runs directly—language...

Glossaries40

Glossary

Elasticity

Elasticity is the ability of a cloud system to automatically add or remove computing resources in response to changing demand, so capacity tracks load in near real time.

Glossary

Autoscaling

Autoscaling is the automatic adjustment of the number of running compute instances or resources based on demand, metrics, or schedules, without manual intervention.

Glossary

Edge Computing

Edge computing is a model that runs processing and storage close to where data is generated or consumed, rather than in a centralized cloud region, to reduce latency and bandwidth use.

Glossary

Content Delivery Network (CDN)

A content delivery network is a geographically distributed set of servers that cache and serve content from locations near users, reducing latency and offloading origin servers.

Glossary

Block Storage

Block storage is a storage architecture that splits data into fixed-size blocks presented to a server as a raw volume, on which a file system or database can be placed for low-latency, high-performance access.

Glossary

Cold Start

A cold start is the added latency incurred when a serverless function or container must initialize a fresh execution environment before handling a request, rather than reusing a warm, already-running one.

Glossary

Horizontal Pod Autoscaler

The Horizontal Pod Autoscaler is a Kubernetes controller that automatically adjusts the number of pod replicas in a workload based on observed metrics such as CPU utilization or custom metrics.

Glossary

Sharding

Sharding is a database scaling technique that horizontally splits a dataset across multiple servers (shards), each holding a distinct subset of rows, so that load and storage are distributed.

Glossary

Partitioning

Partitioning is the practice of dividing a large table or dataset into smaller, more manageable pieces called partitions, which can be queried and maintained independently while appearing as a single logical entity.

Glossary

Database Index

A database index is an auxiliary data structure that improves the speed of data retrieval on a table at the cost of extra storage and slower writes, by letting the engine locate rows without scanning the entire table.

Glossary

Denormalization

Denormalization is the deliberate introduction of redundancy into a database schema — by duplicating or precomputing data — to improve read performance, accepting reduced write efficiency and integrity guarantees.

Glossary

OLTP

OLTP (Online Transaction Processing) refers to database systems optimized for large numbers of short, concurrent transactions — inserts, updates, and lookups — that support day-to-day operational applications.

Glossary

OLAP

OLAP (Online Analytical Processing) refers to systems optimized for complex analytical queries over large volumes of historical data, enabling aggregation, slicing, and multidimensional analysis for reporting and decision-making.

Glossary

Materialized View

A materialized view is a database object that stores the precomputed result of a query physically on disk, so reads return instantly without re-executing the underlying query, at the cost of keeping the result refreshed.

Glossary

Token

A token is the basic unit of text an LLM processes, typically a word fragment, whole word, or character, produced by a tokenizer and mapped to a numeric ID.

Glossary

Context Window

The context window is the maximum number of tokens a language model can consider at once, covering both the input prompt and the generated output.

Glossary

Vector Search

Vector search finds items whose embeddings are closest to a query embedding, enabling semantic retrieval by meaning rather than exact keyword match.

Glossary

Inference

Inference is the process of running a trained model on new inputs to produce outputs, as opposed to the training phase that creates the model.

Glossary

Attention Mechanism

An attention mechanism lets a model weigh the relevance of different parts of its input when producing each output, focusing on the most pertinent tokens.

Glossary

Quantization

Quantization reduces the numeric precision of a model's weights and activations, shrinking memory use and speeding inference with limited accuracy loss.

Glossary

gRPC

gRPC is a high-performance remote procedure call framework that uses HTTP/2 for transport and Protocol Buffers for compact, strongly typed message serialization.

Glossary

Rate Limiting

Rate limiting is a technique that caps how many requests a client may make to a service within a time window, protecting capacity and enforcing fair usage.

Glossary

Pagination

Pagination is the practice of dividing a large result set into smaller, ordered pages so that an API returns data in manageable chunks rather than all at once.

Glossary

Protocol Buffers

Protocol Buffers is a language-neutral, binary serialization format from Google that uses a schema definition to encode structured data compactly and efficiently.

Glossary

WebSocket

WebSocket is a protocol that provides a persistent, full-duplex communication channel over a single TCP connection, enabling real-time two-way data exchange between client and server.

Glossary

HTTP/2

HTTP/2 is a major revision of the HTTP protocol that adds request multiplexing, header compression, and server push over a single connection to improve web performance.

Glossary

HTTP/3

HTTP/3 is the third major version of HTTP, running over the QUIC transport on UDP to eliminate transport-level head-of-line blocking and speed up connection setup.

Glossary

TCP

TCP (Transmission Control Protocol) is a core transport protocol that provides reliable, ordered, connection-oriented delivery of a byte stream between two hosts.

Glossary

UDP

UDP (User Datagram Protocol) is a lightweight, connectionless transport protocol that sends datagrams without delivery guarantees, favoring low latency over reliability.

Glossary

DNS

DNS (Domain Name System) is the internet's distributed naming system that translates human-readable domain names into the IP addresses needed to locate servers.

Glossary

Latency

Latency is the time delay between a request being made and the corresponding response beginning to arrive, typically measured as round-trip time in milliseconds.

Glossary

Distributed Tracing

A technique that follows a single request as it propagates across multiple services, recording timing and context at each step to reveal the end-to-end path.

Glossary

Span

The basic unit of work in distributed tracing, representing a single named, timed operation with a start, an end, and contextual attributes.

Glossary

Metric

A numeric measurement of some aspect of a system captured over time, such as request rate, error count, or memory usage, used for monitoring and alerting.

Glossary

Concurrency

Concurrency is the ability of a system to make progress on multiple tasks during overlapping time periods, structuring work so tasks can be interleaved, regardless of whether they execute simultaneously.

Glossary

Parallelism

Parallelism is the simultaneous execution of multiple computations, typically across several CPU cores or machines, to complete work faster than sequential execution.

Glossary

Immutability

Immutability is the property of data that cannot be changed after it is created; modifications produce new values instead of altering the original, which simplifies reasoning and concurrency.

Glossary

Garbage Collection

Garbage collection is automatic memory management in which a runtime reclaims memory occupied by objects that are no longer reachable by the program, freeing developers from manual deallocation.

Glossary

Compilation

Compilation is the process of translating source code written in a programming language into a lower-level form, such as machine code or bytecode, that a machine or runtime can execute.

Glossary

Interpretation

Interpretation is the execution of a program by directly reading and running its source code or an intermediate representation, statement by statement, without first compiling it to native machine code.