We have all heard, or even lived, this story before -- we had a greenfield project with an exciting business opportunity, so we chose Django with all of its batteries included to move fast and go to market quickly. Fortunately, things went very well, the business was booming and the company growing. Unfortunately, so was the operational and developmental complexity of our Django project. It’s a good problem to have, but a problem nonetheless. In this talk, I will discuss two different approaches to decomposing a Django monolith into multiple services.
YOU MAY ALSO LIKE:
Decomposing a Django Monolith: Two Different Approaches
I’m a software engineer, jack of all trade, trying to be a master of some. I was a tech lead at Memrise and a senior Python engineer at Growth Street. Now I’m at Deliveroo building growth products and marketing automation. I wrote my first line of Django code probably 10 years ago, and even though I’m not actively using the framework anymore, Django still has a very special place in my heart.