官术网_书友最值得收藏!

Release rollback in case of failure

Since monolithic applications are either bundled in the same archive or contained in a single directory, they prevent the deployment of code modularity. For example, many of you may have experienced the pain of delaying rolling out the whole release due to the failure of one feature.

To resolve these situations, microservices gives us the flexibility to rollback only those features that have failed. It's a very flexible and productive approach. For example, let's assume you are the member of an online shopping portal development team and want to develop an application based on microservices. You can pide your application based on different domains such as products, payments, cart, and so on, and package all these components as separate packages. Once you have deployed all these packages separately, these would act as single components that can be developed, tested, and deployed independently, and called μService.

Now, let's see how that helps you. Let's say that after a production release launching new features, enhancements, and bug fixes, you find flaws in the payment service that need an immediate fix. Since the architecture you have used is based on microservices, you can rollback the payment service instead of rolling back the whole release, if your application architecture allows, or apply the fixes to the microservices payment service without affecting the other services. This not only allows you to handle failure properly, but it also helps to deliver the features/fixes swiftly to a customer.

主站蜘蛛池模板: 阳江市| 福泉市| 双柏县| 东乌珠穆沁旗| 绥中县| 高碑店市| 凉城县| 家居| 兴义市| 金沙县| 万全县| 平塘县| 额济纳旗| 南岸区| 栾城县| 宾阳县| 广灵县| 天峻县| 无锡市| 西丰县| 天柱县| 汉沽区| 寿宁县| 锡林浩特市| 泸溪县| 新宾| 珲春市| 巴塘县| 故城县| 张北县| 湖南省| 甘洛县| 广宁县| 桂平市| 元谋县| 清镇市| 团风县| 祁东县| 甘德县| 黄大仙区| 互助|