Indy.Code() Sessions tagged microservices

Don’t Build a Distributed Monolith: How to Avoid Doing Microservices Completely Wrong

As a consultant, I get to see many systems built by many different developers. Recently, I’ve seen an uptick in the number of systems built with a microservice architecture in mind, but those systems often include a lot of the same mistakes that keep them from working well.

In this session you’ll learn from my experiences and get pointers on what to avoid in your microservices implementations so that you don’t accidentally build something which has all the worst aspects of a monolithic application and the worst aspects of microservices These monsters are what I call “distributed monoliths”, and I can help you avoid building one accidentally.

Speaker

Jonathan "J." Tower

Jonathan "J." Tower

Partner & Principal Consultant, Trailhead Technology Partners

A Real World Journey from Monolith to Microservices

Many companies have legacy systems that have become tangled webs of ownership and dependencies. Sources of truth float around as they are synced from one system to the next, any fault can cause side effects or stale data. My team and I have been working on decoupling our monoliths and I would like to share that journey, the technologies (Kafka, ksqlDb, etc), and the patterns (Strangler, Scaffolding, etc) we use to create single sources of truth and a new modern software ecosystem.

Speaker

Jacob Van Brunt

Jacob Van Brunt

Service Architect, Sweetwater