Hacker News new | ask | show | jobs
by artursapek 4170 days ago
He listed one of the benefits of microservices as freedom to use whichever languages/frameworks developers prefer.
2 comments
huxley 4170 days ago
I could see that freedom becoming technical debt if the project is big enough and poorly documented.

I keep picturing the legendary missing Novell server that was buried behind drywall at the University of North Carolina:

http://arstechnica.com/civis/viewtopic.php?f=2&t=1824

link
drbryanadams 4170 days ago
Sure, but the title says "ditching Django" ... presumably if they have a Django monolith, at least some of the devs might choose Django for some of the microservices?

Maybe they are still using Django in some capacity and the title is just slightly overstated ... not sure, but would appreciate an author comment in this regard.

link
tmwatson100 4170 days ago
Yes you're right it is slightly overstated. We still use our Django monolith to compensate for not re-writing every single part of our codebase.

However overtime I would imagine we would move away from Django as with small enough services it would be overkill as a solution.

Saying that, if it makes sense at the time then why not. With this architecture you have the flexibility to do that.

link
drbryanadams 4170 days ago
Sure -- not looking to nitpick. I just wanted to understand if there was something about Django that you found incompatible w/ microservices, and it sounds like there isn't.

An overstated headline isn't the worst crime on the planet (though, I would say that Google has already carried the headline far and wide already ... sigh).

link