#113 Morgan Bruce, Working With Microservices

Morgan Bruce author of Microservices in Action talks about how and why he builds microservices.

Who he is, what he does, his stack. Morgan's book. What is a microservice, difference between microservice and monolith; are monoliths still ok. What to do with a new application. How small should a microservice be. Can a microservice be made up of multiple languages. Microservices calling other microservices; service discovery. Tracing requests across services, tracing on buses. Keeping a copy of data or calling another microservice. Bounded contexts, getting the boundaries right. Deploying, scaling, rolling back. Monitoring. Redeploying a faulty container. Are microservices worth the trouble.

Download mp3 of podcast

8 thoughts on “#113 Morgan Bruce, Working With Microservices

  1. Working in a small team on applications which scaling is not a concern I haven’t spent much time looking into microservices. His answer to your last question specifically about this I found helpful and has me interested some now. Thank you.

  2. I appreciate the discussion balancing the advantages of microservices with the special considerations like data sharing and discoverability. I’ve never had the opportunity to build a “true” microservice as separate and autonomous data stores are a very hard sell to management when single databases have been the norm forever. While we are leveraging Azure slot deployments to make releases easier, one thing that still puts a crimp on it is that too many apps rely on the same database. Slots are great but great care must be taken when a database deployment goes along with it. I think this is a great case for trying to use microservices from the start of a project.

  3. Nice to think about microservices as services that are not just small, but separate. They can be updated separately and deployed separately. I know I tend to focus on the micro, but it’s really about autonomy.

Leave a Reply to None Cancel 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.