0Pricing
Erlang OTP: Distributed & Fault-Tolerant Systems Programming · Lezione

Versionamento e distribuzione delle release

Comprenda le best practice per il versionamento delle release, la distribuzione degli aggiornamenti e la gestione dei rollback in ambiente di produzione

Versionamento e distribuzione delle release è una lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Erlang OTP: Distributed & Fault-Tolerant Systems Programming, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Why Version Your Releases?

When you build an Erlang application for production, it's bundled into a release. Just like any software, releases need clear version numbers.

Versioning helps you:

  • Track changes over time.
  • Identify specific builds.
  • Manage compatibility with other systems.
  • Plan for upgrades and rollbacks.

Erlang's Versioning System

In Erlang, versioning happens at different levels. Each individual application (an .app file) has its own version. The overall release (the .rel file) also has a version that typically reflects the entire bundle.

The vsn key in an .app file defines an application's version.

% my_app.app file (conceptual)
{application, my_app,
 [{description, "My Erlang Application"},
  {vsn, "1.0.0"},
  {modules, [my_app_app, my_app_sup]},
  {registered, []},
  {applications, [kernel, stdlib]},
  {mod, {my_app_app, []}},
  {env, []}]}.

Semantic Versioning (SemVer)

A widely adopted standard is Semantic Versioning (SemVer), typically formatted as MAJOR.MINOR.PATCH. It's a great practice to follow for your Erlang applications.

  • MAJOR: Incremented for incompatible API changes.
  • MINOR: Incremented for new functionality in a backward-compatible way.
  • PATCH: Incremented for backward-compatible bug fixes.

This helps users understand the impact of an upgrade.

Applying SemVer in Erlang

You'll typically apply SemVer to your application's vsn in the .app file. When you create a release, its version (relvsn) often matches the main application's version or follows a similar scheme.

Tools like rebar3 manage these versions when building releases.

% my_app.app file
{application, my_app,
 [{description, "My Erlang Service"},
  {vsn, "1.2.3"},
  {modules, [my_app_app, my_app_sup]},
  {registered, []},
  {applications, [kernel, stdlib]},
  {mod, {my_app_app, []}},
  {env, []}]}.

Deployment Strategies Overview

Once you have a versioned Erlang release, how do you get it running in production? There are several strategies, depending on your system's requirements for uptime and complexity.

  • Cold Deployment: Simplest, involves downtime.
  • Hot Upgrades: Zero-downtime (covered in previous lesson).
  • Blue/Green or Canary Deployments: More advanced, often used with orchestration tools.

Cold Deployment: Simple Restart

A cold deployment is the most straightforward method. You stop your currently running Erlang system completely, replace its files with the new release, and then start the new version.

This method always incurs downtime, making it suitable for systems where brief interruptions are acceptable.

# Stop the old release
/path/to/my_app/bin/my_app stop

# (Replace files with new release)

# Start the new release
/path/to/my_app/bin/my_app start

Hot Upgrades vs. Full Deployment

Recall from the previous lesson that hot code loading allows you to upgrade a running Erlang system without stopping it.

While powerful for applying patches or minor feature additions, hot upgrades are specific to changing *parts* of a running system. A full deployment often refers to the initial setup or a complete replacement of the entire release, sometimes involving a cold restart or more advanced traffic management.

The Importance of Rollbacks

Even with careful testing, new deployments can introduce unexpected issues. A robust deployment strategy always includes a plan for rollbacks.

A rollback means reverting your system to a previous, stable version if the new deployment fails or causes problems. This minimizes the impact of failures and restores service quickly.

Erlang's Rollback Mechanism

Erlang releases are designed to support rollbacks. When you perform a hot upgrade, Erlang generates an .relup script that describes how to move between versions. Crucially, it also knows how to reverse that script to go back.

Even with cold deployments, you can switch back to a previous release by managing your release directories and restarting the desired version.

# Example of a rollback command using release_handler
# This would typically be part of a custom script or release tool

% release_handler:install_release("my_app-1.1.0").
% release_handler:make_permanent("my_app-1.1.0").

# Alternatively, for cold deployment:
# /path/to/my_app_1.1.0/bin/my_app start

Test Your Understanding

Order the steps for a typical cold deployment of an Erlang release.

Summary: Versioning & Deployment

You've learned about the critical aspects of release versioning and deployment in Erlang:

  • Versioning: Use vsn in .app files, ideally following SemVer (MAJOR.MINOR.PATCH), to track and manage changes.
  • Deployment: Understand cold deployment (with downtime) and its distinction from hot upgrades.
  • Rollbacks: Always plan for reverting to a stable previous version to ensure system resilience.

These practices are key to managing robust Erlang applications in production!

Domande Frequenti

La lezione «Versionamento e distribuzione delle release» è gratuita?

Sì — il testo completo di «Versionamento e distribuzione delle release» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming, passa a CoddyKit PRO. Il corso Erlang OTP: Distributed & Fault-Tolerant Systems Programming include 4 lezioni in totale.

Cosa imparerò in «Versionamento e distribuzione delle release»?

Comprenda le best practice per il versionamento delle release, la distribuzione degli aggiornamenti e la gestione dei rollback in ambiente di produzione Eserciti Erlang OTP: Distributed & Fault-Tolerant Systems Programming con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Erlang OTP: Distributed & Fault-Tolerant Systems Programming?

Non è richiesta alcuna esperienza precedente. Erlang OTP: Distributed & Fault-Tolerant Systems Programming su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.

Quanto tempo richiede la lezione «Versionamento e distribuzione delle release»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming?

Sì. Ogni lezione Erlang OTP: Distributed & Fault-Tolerant Systems Programming include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Creazione di release Erlang
  2. Caricamento e aggiornamento a caldo del codice
  3. Versionamento e distribuzione delle release
  4. Configurazione delle release e script di avvio
← Torna a Erlang OTP: Distributed & Fault-Tolerant Systems Programming