Marko Anastasov (@markoa, Co-Founder Semaphore CI) talks about how to manage the evolution of monoliths to microservices using modern CI/CD.

SHOW: 667

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW SPONSORS:

• CloudZero - Cloud Cost Intelligence for Engineering Teams
• FujiFilm. Your archival and backup data strategy, built on tape. Fujifilm tape is helping businesses get a handle on their vast amounts of data in the most secure, scalable and efficient way. Find out more at builtontape.fujifilmusa.com
• CDN77 - CDN Focused on VOD and Security
• CDN77 - ask for a free trial with no duration or traffic limits. 

SHOW NOTES:

• SemaphoreCI website
• Semaphore CI/CD Resources
• Transitioning from Monolith to Microservices (ebook)

Topic 1 - Marko, let’s start with a quick introduction. How did you get involved with SemaphoreCI?

Topic 2 - You have been working on CI/CD for 10+ years. Many listeners are familiar with the concepts of CI and CD but what brought you into the space and what are the primary benefits you see in clients you work with?

Topic 3 - We hear success stories from organizations that are doing hundreds to thousands of deployments a day (Netflix, Twitter, etc.). Many didn’t start out that way. Some didn’t even start with microservices, but started with monoliths and moved to microservices as they outgrew a monolithic architecture. Is this common?

Topic 4 - What are the tradeoffs between monoliths and microservices? Also, does the concept of a greenfield deployment vs. a brownfield deployment factor into the decision? Where does an organization start?

Topic 5 -  What are the guidelines to building a successful microservices strategy? Where do you even start to split up a monolith? Is it a line of business function, technical boundary in the application, keeping the size of the development team small?

Topic 6 -   In the journey to microservices, what are the first advantages seen? What are the first pitfalls encountered?

Topic 7 - Developers just want to go fast and automate all the things. Once a microservices strategy is built, my next thought goes to governance, compliance, security & cost. All items that keep developers from going fast. Doesn’t “shifting left” come at a price?

FEEDBACK?

• Email: show at the cloudcast dot net
• Twitter: @thecloudcastnet