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

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.

主站蜘蛛池模板: 湖北省| 孝感市| 河曲县| 灵川县| 阜城县| 呼图壁县| 舟山市| 鹤岗市| 西城区| 高州市| 新巴尔虎右旗| 陆川县| 竹山县| 上杭县| 亳州市| 乌拉特前旗| 宁蒗| 富平县| 全州县| 会理县| 温泉县| 静安区| 鄂伦春自治旗| 云安县| 五大连池市| 德安县| 永康市| 峨山| 仁布县| 海丰县| 阿坝县| 佛冈县| 安庆市| 南康市| 上思县| 花垣县| 邯郸市| 普洱| 海丰县| 赣榆县| 沈丘县|