This post is from the XebiaLabs blog and has not been updated since the original publish date.
Exploring Uncharted Territory of Microservices - Q & A
Our recent webinar “Exploring the Uncharted Territory of Microservices” featured a panel of thought leaders who combined brought more than 30 years of collective experience to explore Microservices and their surrounding environments.
During the hour long discussion our panel touched on the following topics:
- Relevence of Microservices in your career
- The appeal of Microservices
- How to start using Microservices
- Traps to be aware of
Our thought leaders included: Gene Kim is known as the founder of Tripwire, and as the author of three books, “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win,” “Visible Ops Security,” and “The Visible Ops Handbook.” Randy Shoup is a consulting CTO and former director of engineering for cloud computing at Google. He was previously Chief Engineer and Distinguished Architect at eBay. Andrew Phillips is VP of product management for XebiaLabs, the leading provider of software for Continuous Delivery and DevOps. He contributes to a number of open source projects including Apache jclouds, the leading cloud library. Gary Gruver is president at Practical Large Scale Agile and was the former VP of Release, QA and Ops at Macys.com and before that he was Director of Engineering at HP
Post Webinar Q & A
Almost as informative as the session itself, we featured an insightful audience participation Q&A session at the end which allowed listeners to ask questions directly to the panel. The questions and responses both gave deep insight into Microservices as a practice, not just a philosophy. The following questions were discussed:
- How much do Microservice breakdown an n-tiers architecture? Is it just something complementary to what we are doing?
- If you encourage redundancy of data, then how do you ensure data integrity when a service call fails? Sometimes a business activity must be completed as a transaction across multiple micro services?
- If we are modeling the real Microservices world, do we end up with for instance the concept of an 'incomplete order' in the code?
- Are Microservices considered more of an architectural strategy? Or an design/implementation style for SOA?
- Regarding managing the graph of service dependencies, is there a generally accepted paradigm to help manage that complexity? An API gateway, an enterprise service bus, or something else, for example?
- Since accessing the database violates the API, how would you send bulk-data from your Microservices to a data warehouse?
- When you say small changes...does that mean development/tested/deployed to prod because products/features are not small?
- How do you define a Microservice and then Microservice architecture?
- What would you choose as a secure and practical way to communicate between Microservices to ensure their independency while keeping a reasonable performance
- To me, Microservices sound perfectly suitable for Test driven development (is it actually mostly the preferred pattern in developing Microservices)?
- Would you consider a governance structure or micro services library to keep the services "clean"? Also taking into account SLA's of services?
- Very granular services may result in information flow redirected to people/service registry/QA to cover multi service use cases. What is your take on that?
- How do you know that all the major companies use Microservices - is there a paper that published this?
- What is the difference between a webservice and a Microservice