Overview

This section explains how auto-upgrade is performed in microservice. The below configuration helps customers to perform seamless auto-upgrade in microservice:

• First Time Deployment – Helps to generate and execute DDL scripts
• Upgrades – Helps to generate and execute incremental DDL scripts
• Data Model Validator – Supports backward compatibility

The Big Bang Adoption method involves a lot of risks and the fallback systems may be inadequate to deal with them. Rolling deployment spreads out the deployment of a new software update across multiple phases, which often involves several servers while performing different functions in a server cluster. Rolling deployment is effective for applications that run as multiple instances which make-up a server cluster and whose server nodes receive traffic through a load balancer. The major benefit of Blue-Green deployment is in simple rollouts, quick rollbacks, and easy disaster recovery. 

To leverage the latest functional and technical features, Temenos clients look for upgrade microservice packages running in their own premise or cloud environments. Once the clients receive the specified version of microservice package, they can adopt a Blue-Green deployment strategy for upgrading their existing microservice packages.

The Temenos microservices are designed to use either SQL or NoSQL databases based on its business data model requirements and querying complexity. The database migration scripts are available in the package, which need to be executed to migrate the database. Microservice customers prefer to upgrade the microservice database during migration from Blue-Green deployment versions of the microservice.  

It provides the below capabilities:

• Allows to develop database-agnostic application by creating tools to support the generation of database-specific installation scripts from the database models (JPA entity classes/.entity.)
• Provides infrastructure services to upgrade the database without any manual intervention and without resulting in database downtime. 
• Restricts developers from making any backward compatibility changes in the database model during the development.