#121 Mark Eisenberg, Microservices in the Enterprise

Summary
Mark Eisenberg discusses why enterprises should adopt microservices, what is stopping them, and how they can overcome those problems.

Details
Who he is, what he does. Mark's interest in microservices. What a microservice is, why it is important, why it is difficult; what he means by "enterprise". What enterprises are currently doing - using new technology in an old way. Are enterprises changing for the wrong reasons; what are the right reasons - "fear". Time to market and scale is very short, think of Uber, Airbnb, etc. Product Enterprises don't always see the threat that is coming. Changes needed - culture, support from business units, CI/CD, build security in from start, cloud is not necessary, Jez Humble's book Accelerate, everything has to change. Better, faster, cheaper is what the execs are interested. Microsoft's recommendations on getting microservices into the enterprise. Concrete steps an enterprise can take - training, developers should be driving the change. Don't start with "can't", focus on what and why.

Links
Mark's twitter

Download mp3 of podcast

#113 Morgan Bruce, Working With Microservices

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

Details
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

#89 Mark Eisenberg, Breaking the Monolith

Summary
Mark Eisenberg talks about the very long life of the software monolith, when it started, and how we have been trying to escape it since.

Details
Who he is, what he does. What is a monolith, tell-tale signs of a monolith, coupling and decoupling. Why we built monoliths. N-tiers and monoliths. Software is rarely a green field. Were we ever able to swap tiers. Advantages of a monolith, it's familiar. Companies need a visionary to effect change. Risk raises its head. SOA didn't work, client server didn't work, n-tier didn't work. Successful companies went from monoliths to microservices when they needed to. RPC is from the 1960s, are you running one piece of code on one machine or ten machines. How to get off the monolith, find a visionary. Time to respond to a challenge is very short. Microsoft is a good example of a large company changing.

Links
Mark's LinkedIn

Download mp3 of podcast