mardi 18 avril 2017

A kind of A/B testing when B is a fallback

Actually better term may exist for what I need, but I am not aware of it and would be grateful to anyone who suggests one and/or edits the subject of the question appropriately.

Consider web api service S which is deployed to production server. Let's treat it as a working source of truth.

Then I, for example, need to update some external dependencies or change infrastructure code neither directly affecting core business logic nor service's public contract.

Thus I get S_updated which must pass phase of staging and only then be deployed to production. Due to the kind of changes made to the codebase I would expect this service to either work as previous version or not to work at all due to integration issues. There is still a risk of somehow altering the behavior of the system, but I can live with it and expect unit tests to be a rather good safety net. This is also proved by the practice.

What I actually want is to be able to deploy S_updated to production and to have some proxy service dispatching all or some (depends on configuration) failed requests to the former S service.

Do some generic configurable solutions for such functionality exist?

Aucun commentaire:

Enregistrer un commentaire