3 ms·

Unless your project complexity is on the order of blinking an LED, there isn't enough time in the day for a monolith, I'm afraid. You are going to have to build

Unless your project complexity is on the order of blinking an LED, there isn't enough time in the day for a monolith, I'm afraid. You are going to have to build in coordination with other services (OSes, DMBSes, etc.) It is a nice idea, but totally impractical.

feoren 3y ago
Highlight all the code you have written / are responsible for. Have you highlighted just one single project that gets deployed as one unit? Then you have a monolith. Monolith doesn't mean you never talk to other services; it means you only own one.
- deleted 3y ago
  [deleted]
- randomdata 3y ago
  My coworker highlighted just one single project that gets deployed as one unit. I have a second hobby project I work on at home of which I also take ownership. He is building a monolith, I am not? Even though we are working on the exact same project? Um. Okay. So, just so I am clear, the advice here can be rephrased as: "Save a matter of life or death, don't have hobbies"?
  - feoren 3y ago
    I think you know what I meant. If you want exact definitions of words, study math.
fallingknife 3y ago
You can use Rails/Django/NextJS + Postgres/Mysql and while I guess that's not technically a monolith, everybody calls it that anyway because the coordination is pretty much abstracted out. And that's gonna get you pretty far. If you really wanted it to be a monolith, you could use sqlite and that would actually get you pretty far too, but why would you when postgres/mysql is just as easy and will scale so much further?
- randomdata 3y ago
  If we also call that a monolith, what else is there? We have fully encompassed all the options.
  - fallingknife 3y ago
    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.
    - randomdata 3y ago
      > 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.
      - Falmarri 3y ago
        Yes. It could be 25 Django services
        randomdata 3y ago
        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.

feoren 3y ago

Highlight all the code you have written / are responsible for. Have you highlighted just one single project that gets deployed as one unit? Then you have a monolith. Monolith doesn't mean you never talk to other services; it means you only own one.

deleted 3y ago
[deleted]
randomdata 3y ago
My coworker highlighted just one single project that gets deployed as one unit. I have a second hobby project I work on at home of which I also take ownership. He is building a monolith, I am not? Even though we are working on the exact same project? Um. Okay. So, just so I am clear, the advice here can be rephrased as: "Save a matter of life or death, don't have hobbies"?
- feoren 3y ago
  I think you know what I meant. If you want exact definitions of words, study math.

fallingknife 3y ago

You can use Rails/Django/NextJS + Postgres/Mysql and while I guess that's not technically a monolith, everybody calls it that anyway because the coordination is pretty much abstracted out. And that's gonna get you pretty far. If you really wanted it to be a monolith, you could use sqlite and that would actually get you pretty far too, but why would you when postgres/mysql is just as easy and will scale so much further?

randomdata 3y ago
If we also call that a monolith, what else is there? We have fully encompassed all the options.
- fallingknife 3y ago
  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.
  - randomdata 3y ago
    > 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.
    - Falmarri 3y ago
      Yes. It could be 25 Django services
      - randomdata 3y ago
        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.