Software Architecture Pitfalls and How to Avoid Them

Re:Software Architecture Pitfalls and How to Avoid Them by fallingknife on Friday December 22, 2023 @01:28AM (#38731528)

I mean, if I say my backend is a 'Django monolith', I have run into exactly zero engineers who don't know exactly what I'm talking about.

[ Parent | on HN ]

Re:Software Architecture Pitfalls and How to Avoid Them by randomdata on Friday December 22, 2023 @02:00AM (#38731687)

> I have run into exactly zero engineers who don't know exactly what I'm talking about.

And I am afraid I haven't broken your streak. I know what Django is and what it usually entails.

I'm not sure what "monolith" adds, though. Simply saying "Django" would communicate the exact same thing, no? Is there a "Django non-monolith" that it could be confused with?

Per your definition above, it seems there is no software that is not a monolith.

[ Parent | on HN ]

Re:Software Architecture Pitfalls and How to Avoid Them by Falmarri on Friday December 22, 2023 @02:30AM (#38731852)

Yes. It could be 25 Django services

[ Parent | on HN ]

Re:Software Architecture Pitfalls and How to Avoid Them by randomdata on Friday December 22, 2023 @02:45AM (#38731933)

I have no idea what you are trying to say, but my best guess is that you are referring to a case where one Django application is coordinating with 24 other services in some fashion?

Per fallingknife's definition, that's still a monolith. No different than a Django application coordinating with MySQL. If it is that you think 25 > 1 is somehow significant, throw in Stripe, GPT, etc. in addition to MySQL. He would still call that a monolith. It's all the same.

That would not be a monolith by my definition as I say that coordination removes software from being a monolith, but we've long moved past my definition. We're only here now to understand where fallingknife's definition allows for there to be anything other than monoliths.

[ Parent | on HN ]