Testing Microservices, the sane way
Cindy Sridharan
7.5K26

Nice read. You are well ahead if you are thinking about security compliance, data integrity issues, etc etc that such a model would bring. And the pressure is sure on from the beginning to design such a system that would

  1. Work as normal for all the production traffic and continue to route to the old service
  2. Identify & handle the test traffic in production and route to the new service under test
  3. The monitoring and metrics know to disregard such test traffic
  4. And that all this is a for each service

Not to say this is not possible but it has to be in the ‘engineering’ culture.

For me..I am still battling the ‘this is frontend’ / ‘backend’ issue

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.