To Share, or Not to Share: Service Virtualization and Microservices

By Jessica Pennington

Microservices are individual units of executable code that work within a limited framework. They are extremely useful when placed within an architecture of numerous microservices. On June 24th, 2015 I attended a webinar titled “How to Share Share-Nothing Microservices,” hosted by Jason Bloomberg, the President of Intellyx, and Scott Edwards, Director Product Marketing for Service Virtualization at CA Technologies. The webinar explained how to use microservices to your advantage in order to deliver products that are competitive in the application economy.

msev2The title of the webinar seems a little strange, until one hears how Bloomberg describes the functionality of microservice architecture. He describes the microservices as parsimonious, or extremely cheap or precisely rationed. He uses this to mean that each microservice is as small as it can be without sacrificing functionality. They will perform a single task, and do so effectively. The “share-nothing” concept comes in when we discuss the capabilities of the microservices. Each microservice is small, but still maintains its own code, runtime, OS, and data cache. The data caches should not be shared between microservices, because the instances of the services are constantly changing. This limits co-dependency.

Read the entire article at https://communities.ca.com/community/ca-devtest-community/blog/2015/07/06/to-share-or-not-to-share-service-virtualization-and-microservices

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.