All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
4330 bites
Page 78
Read replicas in managed relational databases
A read replica is an async copy of the primary that serves read-only queries, offloading the primary and scaling read-heavy workloads; expect replication lag.
How does caching reduce database load?
Cache-aside reads, RAM-speed lookups, TTL plus invalidation.
RDS Multi-AZ versus Read Replicas
Multi-AZ is a synchronous standby for failover, replicas are async for read scaling, combine both when needed.
Strong versus eventual consistency in NoSQL
Strong reads see the latest write at higher latency and cost, eventual reads may be stale but are cheaper and faster, match the choice to stakes.
Data warehouse versus OLTP database
Warehouses use columnar storage for analytical scans, OLTP uses row storage for fast transactions, each fits a different workload.
Add a second access pattern to a key-value store
Add a global secondary index on EmailAddress, weighing extra storage, write amplification, and eventual consistency.
Design a global low-latency database
A distributed store with replicas near users, a tuned consistency level, accepting lag, conflicts, and cross-region cost.
CAP theorem and real database tradeoffs
During a partition you pick consistency or availability, CP systems reject requests, AP systems stay available but stale.
The cloud shared responsibility model
The provider secures the cloud (hardware, OS, runtime), you secure what runs in it (code, data, config, access).
Why not store uploads on local PaaS disk?
PaaS instances are ephemeral and unshared, so local files vanish on restart and are invisible to peers; store uploads in object storage.
Deploying to Heroku via Git
Push to the remote, a buildpack detects the language, builds a slug, and runs the Procfile process.
Securely supplying secrets to an app
Never hardcode credentials, inject them as environment variables or pull from a secrets manager, and rotate them.
CI/CD pipeline for a container PaaS
Run tests, build the image, push the tag to a registry, then deploy it to Cloud Run. The registry is the build-to-deploy handoff.
Offload long-running tasks from web requests
Enqueue the job to a queue, return immediately, process with separate workers, report status out of band.
Cold starts in serverless environments
A cold start is the delay to provision a fresh instance and initialize the runtime; mitigate with provisioned concurrency and by shrinking init work.
Migrating a stateful monolith to PaaS
Externalize state to backing services, make processes stateless and disposable, read config from the environment per Twelve-Factor.
Writing a Dockerfile for a web app
FROM a base, set WORKDIR, install dependencies before app code for cache reuse, EXPOSE the port, CMD the start command.
Kubernetes Deployment versus Pod
A Pod is the smallest disposable unit, a Deployment maintains a desired replica count, self-heals, and rolls out updates.
Multi-stage Docker builds
A build stage compiles with the toolchain, the final stage uses a minimal base and copies only the artifact, cutting size and attack surface.
Exposing Kubernetes services to the internet
A Service gives stable access and LoadBalancer exposes one service, while Ingress adds L7 host and path routing with TLS for many services.