Search the library

Multi-stage a build lets you compile in one environment and then copy only the final artifact into a slim runtime image. This reduces image size, shortens deployment time, lessens the attack surface, and makes it easier to reason about what the service actually needs to run. It is a packaging discipline, not just a size optimization.

String values are immutable and can be safely shared. StringBuilder supports mutable append operations without synchronization and is usually appropriate for thread-confined construction. StringBuffer synchronizes individual methods, but that does not automatically make a multi-call workflow atomic; synchronization often costs more than needed when a builder is local to one thread.

Rebuilding separately for staging and production can produce different binaries from the same apparent release. Build once, identify the artifact with its source revision and provenance, then promote that immutable artifact. Caches can accelerate builds, but a cache miss must not change correctness.

A rebuild is a new artifact, even at the same source commit. Promotion preserves the tested output while environment configuration remains deliberate and observable.

Concurrent builds use multiple phases and can leave an invalid index. Inspect the server error and pg_index readiness/validity, waits, and transactions; do not assume the operation was atomic or load-free.