←back to thread

Use One Big Server (2022)

(specbranch.com)
343 points antov825 | 2 comments | 31 Aug 25 17:29 UTC | HN request time: 0.007s | source
Show context
alkonaut ◴[31 Aug 25 19:36 UTC] No.45086341[source]▶
Microservices vs not is (almost) orthogonal to N servers vs one. You can make 10 microservices and rent a huge server and run all 10 services. It's more an organizational thing than a deployment thing. You can't do the opposite though, make a monolith and spread it out on 10 servers.
replies(2): >>45086757 #>>45087104 #
marcosdumay ◴[31 Aug 25 20:25 UTC] No.45086757[source]▶
> You can't do the opposite though, make a monolith and spread it out on 10 servers.

You absolutely can, and it has been the most common practice for scaling them for decades.

replies(1): >>45089895 #
alkonaut ◴[01 Sep 25 06:06 UTC] No.45089895[source]▶
That’s just _duplicating_ the nodes horizontally which wasnt what I meant.

That’s obviously possible snd common.

What I meant was actually butchering the monolith into separate pieces and deploying it, which is - by the definition of monolith - impossible.

replies(1): >>45090211 #
1. doganugurlu ◴[01 Sep 25 07:00 UTC] No.45090211{3}[source]▶
What would be the point of actually butchering the monolith?

There is no limit or cost to deploying 10000 lines over 1000 lines.

replies(2): >>45091086 #>>45091429 #
2. alkonaut ◴[01 Sep 25 10:27 UTC] No.45091429[source]▶
I meant in the sense of ”machine A only manages thing authentication” and ”machine B only manages orders”.

If that’s possible (regardless of what was deployed to the two machines) then the app just isn’t a true monolith.