Continuous Delivery Suicide = Building Application Architectures with Microservices, but without Service Virtualization

By Scott Edwards

Jason Bloomberg recently wrote a great blog on how these microservices are a lot like Lego building blocks, helping developers “mix and match various bits and pieces, building flexible applications by simply snapping their components together.”   Another article on InfoWorld gives a great example of how these microservices come together to create a search result in an online shopping scenario – kicking off over 170 applications to deliver images, matches, recommendations, reviews, transaction, etc. all based upon that search.

digitalfutureThat’s all very cool stuff from the customer standpoint.  But, how do you ensure all those microservices come together to actually deliver a high-quality experience?  How do you test against this and follow the transaction flow?

Microservices just increased complexity 10 fold.  There are more dependencies on other services than ever before. All these microservices are dependent on each other.

These complexities and dependencies are the antithesis to speed. Developers don’t have time to wait in a DevOps shop that must continuously be delivering software and doing so with paramount quality.

Read the entire article at http://servicevirtualization.com/profiles/blogs/continuous-delivery-suicide-building-application-architectures.

SHARE THIS:

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.