←back to thread

Use One Big Server (2022)

(specbranch.com)
343 points antov825 | 1 comments | 31 Aug 25 17:29 UTC | HN request time: 0s | 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 #
const_cast ◴[31 Aug 25 21:08 UTC] No.45087104[source]▶
> You can't do the opposite though, make a monolith and spread it out on 10 servers.

Yes you can. Its called having multiple applications servers. They all run the same application, just more of them. Maybe they connect to the same DB, maybe not, maybe you shard the DB.

replies(1): >>45089899 #
alkonaut ◴[01 Sep 25 06:07 UTC] No.45089899[source]▶
That’s obviously not what I meant. I meant running different aspects of the monolith on different servers.
replies(3): >>45090181 #>>45090690 #>>45093106 #
1. lelanthran ◴[01 Sep 25 06:55 UTC] No.45090181{3}[source]▶
> I meant running different aspects of the monolith on different servers.

Of course you can. I've done it.

Identical binary on multiple servers with the load balancer/reverse proxy routing specific requests to specific instances.

The practical result is indeed "running different aspects of the monolith on different servers".