Cloud Bits: Bounded by contract

In the last post, we saw how deep-checks & health-checks can prevent your application from failing due to a bad deployment. Continuing with the same theme, we will take a look at how can we enforce better testing in a service-oriented architecture even before the code is merged to the main branch of a service. Understanding the problem We now know that a good cloud architecture should have resiliency against a bad deployment through health probes. Though this also means that someone was able to check-in bad code & that went to the deployment stage. Also as your service becomes complicated, testing all integration points through probes will become a challenge. A typical cloud application can have an architecture that looks as below There are multiple integration points & a bug in one of the services can result in complete application failure when these errors bubble up. Something as simple as renaming a field can go unnoticed until the code reaches staging or canary(And in worse case…