Configuring zero-downtime upgrades using automated development and test analysis

A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for upgrade of an application from a first version to a second version, the application interacting with data stored in a database system, the operations comprising:

• during development of the second version within a development environment, tracing activities to determine sets of development tables, the second version comprising changes that are incompatible with the first version, the set of development tables comprising a set of deploy tables, sets of activation tables, and sets of troubleshooting tables;
• computing, by a configuration generator, an upgrade configuration based on the set of development tables, the upgrade configuration defining a set of tables to deploy the changes during an upgrade, the set of tables being computed based on the sets of development tables;
• during the upgrade:
• continuing production use of the first version of the application using a first runtime at least partially comprising a first data schema, and
• establishing a second runtime at least partially by defining a second data schema within the database system using the upgrade configuration, the second data schema comprising the set of tables;
• and
• completing the upgrade by switching production use to the second version of the application from the first version of the application.

A system, comprising:

• a computing device;
• and
• a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for upgrade of an application from a first version to a second version, the application interacting with data stored in a database system, the operations comprising:
• during development of the second version within a development environment, tracing activities to determine sets of development tables, the second version comprising changes that are incompatible with the first version, the set of development tables comprising a set of deploy tables, sets of activation tables, and sets of troubleshooting tables;
• computing, by a configuration generator, an upgrade configuration based on the set of development tables, the upgrade configuration defining a set of tables to deploy the changes during an upgrade, the set of tables being computed based on the sets of development tables;
• during the upgrade:
• continuing production use of the first version of the application using a first runtime at least partially comprising a first data schema, and
• establishing a second runtime at least partially by defining a second data schema within the database system using the upgrade configuration, the second data schema comprising the set of tables;
• and
• completing the upgrade by switching production use to the second version of the application from the first version of the application.