Updates and container deployment

Documentation status: guide — see Maturity and evidence.

Models, views, and services are runtime assets, so updating them is part of application evolution.

A simple update descriptor can keep module name, version, and distribution location explicit:

<modules>
  <module
      name="business-application"
      path="https://example.org/builds/business-application.zip"
      version="1.0.0" />
</modules>

Containerization packages the same conceptual runtime rather than replacing it:

services:
  business-application:
    image: business-application
    ports:
      - 9696:9696
    volumes:
      - ./deploy/database:/var/application/database
      - ./deploy/temp:/var/application/temp

A release process should make independently versioned pieces explicit and should preserve the same conceptual identities across packaging changes.