Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
22 results for “Schema Registry”
Blue-Green Database Schema
The constraint that makes fast rollback actually work — both application versions must be able to run against one schema at the same time.
Image Registry
The store from which container images are pulled, and an under-appreciated availability and security dependency of every deployment and every autoscale event.
Prompt Registry
A versioned store of production prompts with their model bindings, parameters and evaluation results, so a prompt change is a reviewable, traceable, reversible deployment.
Schema Evolution
Changing a table's structure over time while keeping existing data readable and existing consumers working.
Service Registry
The database of currently available service instances and their addresses, maintained by registration and pruned by health checking.
Star Schema
A dimensional model with one central fact table of measurements surrounded by denormalised dimension tables describing them.
Client-Side Discovery
The caller queries the registry itself and chooses an instance, rather than sending to a stable address that something else resolves.
Data Catalog
A searchable inventory of datasets with their schema, owner, meaning, freshness, quality and classification.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Data Lakehouse
A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
Event Upcasting
Transforming an old event's stored form into the current shape as it is read, so historical events remain replayable after the schema changes.
GraphQL
A query language and runtime where the client specifies exactly which fields it needs, against a typed schema, usually via a single endpoint.
Normalisation
Organising a schema so each fact is stored exactly once, removing the update anomalies that duplication creates.
Open Table Format
A metadata layer over files in object storage that supplies ACID transactions, schema evolution and time travel — the thing that turns a data lake into a lakehouse.
Salesforce's Metadata-Driven Multi-Tenancy
Salesforce serves every customer from shared infrastructure with a single physical schema, storing customer-specific data structures as metadata rather than as separate tables.
Service Discovery
The mechanism by which a caller finds a currently healthy network address for a service whose instances are ephemeral.
Zero-Downtime Migration
Changing a schema or system while it stays in service, by adding the new alongside the old, migrating, then removing the old.
A team wants to move a workload from PostgreSQL to a document store because "the schema keeps changing". What do you ask?
The questions 1. What is actually changing — the shape, or the schema management process? "The schema keeps changing" usually means migrations are painful, not
Your service registry becomes unavailable. Every service is healthy. What happens, and what should happen?
What usually happens A total outage , despite every service being fine — because resolution is on the request path and a failed resolution fails the request. Th
Schema Registry
Enforcing compatibility on events the way CI enforces it on code.
Message Formats
JSON, Protobuf, Avro — schema evolution and payload economics.
Relational Modelling
Normalisation, keys, constraints and the invariants a schema enforces.