Production Twitter on one machine? 100Gbps NICs and NVMe are fast

Post by Tepix » Sat, Jan 07, 2023, 9:07 PM UTC

trishume wrote: post #16

Cyph0n wrote: post #10

Earlier quoted context omitted.

My bad - not English, but ASCII. The assumed max tweet size is in bytes rather than (UTF) characters.

I specifically assumed a max tweet size based on the maximum number of UTF-8 bytes a tweet can contain (560), with a link to an analysis of that, and discussion of how you could optimize for the common case of tweets that contain way fewer UTF-8 bytes than that. Everything in my post assumes unicode.

Post by TillE » Sat, Jan 07, 2023, 9:08 PM UTC

andrewstuart wrote: post #26

judge2020 wrote: post #25

Earlier quoted context omitted.

Kubernetes and containers are a means to service architecture; It enabled scalability but does not require it. You should still be containerizing your applications to ensure a consistent environment, even if you only throw it in a docker-compose file on your production server.

I don't even use containers - I aim primarily for simplicity and so far I have found I am able to build entire sophisticated systems without a single container. Containers I find make things much more complex.

Post by tambourine_man » Sat, Jan 07, 2023, 9:09 PM UTC

andrewstuart wrote: post #39

tambourine_man wrote: post #36

Earlier quoted context omitted.

>… without understanding how much capacity there is in horizontal. I think you mean vertical, right?

Ha ha yes I do! (corrected)

Post by readonlybarbie » Sat, Jan 07, 2023, 9:10 PM UTC

yodsanklai wrote: post #44

andrewstuart wrote: post #24

Most projects I encounter these days instantly reach for kubernetes, containers and microservices or cloud functions. I find it much more appealing to just make the whole thing run on one fast machine. When you suggest this tend to people say "but scaling!", without understanding how much capacity there is in vertical. The thing most appealing about single server configs is the simplicity. The more simple a system ea…

> The thing most appealing about single server configs is the simplicity. The more simple a system easy, likely the more reliable and easy to understand. What if your unique machine crash?

Post by andrewstuart » Sat, Jan 07, 2023, 9:10 PM UTC

yodsanklai wrote: post #44

andrewstuart wrote: post #24

Most projects I encounter these days instantly reach for kubernetes, containers and microservices or cloud functions. I find it much more appealing to just make the whole thing run on one fast machine. When you suggest this tend to people say "but scaling!", without understanding how much capacity there is in vertical. The thing most appealing about single server configs is the simplicity. The more simple a system ea…

> The thing most appealing about single server configs is the simplicity. The more simple a system easy, likely the more reliable and easy to understand. What if your unique machine crash?