You need to reduce the number of unplanned rollbacks of erroneous production deployments in your company's web hosting platform. Improvement to the QA / Test processes accomplished an 80% reduction. Which additional two approaches can you take to further reduce the rollbacks?

1. Introduce a blue-green deployment module

2. Fragment the monolithic platform into micro services.

Explanation:

1. Blue-green deployment is a type of technique which minimizes downtime and risk by running two identical production environments called Blue and Green.

This technique eliminates downtime due to app deployment. In addition, blue-green deployment reduces risk: if something unexpected happens with your new version on Green, you can immediately roll back to the last version by switching back to Blue.

2. The scenario behind microservices architecture is that some types of applications become easier to build and maintain when they are broken down into smaller, composable pieces which work together. Meaning that each component is developed separately, and the application is simply the sum of its constituent components.

Each service runs a unique process and usually manages its own database in a micro services architecture,. This provides development teams with a more decentralized approach to building software, ans also allows each service to be deployed, rebuilt, redeployed and managed independently.

Micro services do have a few disadvantages when compared to monoliths:

Micro services, unlike the internals of a monolith, communicate over a network. In some situations, this can be seen as a security concern. Istio solves this problem by automatically encrypting the traffic between microservices.

Achieving the same level of performance as with a monolithic approach can be difficult because of latencies between services.