1216
Upwards mobility (lemmy.dbzer0.com)
submitted 11 months ago by to c/programmer_humor@programming.dev
137 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 11 months ago (4 children)

If the Java monolith used 6 gb of ram and each Go service uses 500mb of ram, but now there are 16 micro services, which uses more memory?

Monoliths are more efficient, but hav other issues.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 11 months ago (2 children)

    Can be more efficient, but it's not always. You can scale those services more too. Do you need all 16 running on idle? Lazy load then as needed. Also does it really need a whole 500mb? Why? If its just a cache made that's better handles with another shared service (redis, etc). If it's software, why? A full "fat" Suse Base Container image uncompressed is 94.8mb and not all of that will be loaded in RAM. Going down to a micro at 23mb. All this and now you can deploy it on the shared infra, no separate OS, Management/security/logging/networking solution.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 11 months ago (1 child)

    Sure, but they also have duplication, IE database connections. Each service needs at least 1 connection versus one for a monolith.

    There are pros and cons to any architecture.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
    • load more comments (1 reply)