3 ms·
I don't really know how to take comments like this. I work on a pipeline that processes millions of events per day in a pipeline that contains two pretty busy
by pravus 3y ago
I don't really know how to take comments like this.
I work on a pipeline that processes millions of events per day in a pipeline that contains two pretty busy Go programs. One has an embedded Javascript engine and does all kinds of pattern matching and string manipulation. The other does a ton of database read/write and some crypto-calculations to do data integrity for us.
Millions of events. Per day. Never a panic in production.
It is easily possible to write deterministic, highly performant, and durable applications in Go.
- pmarreck 3y ago> millions of events per day I was talking about millions of events per every couple of seconds, not per day. A million events per day can be accomplished with just 11 per second, btw; a very... achievable number. WhatsApp, which is built on OTP, handled 64 billion messages in a day. Averaging out to 744,000 a second. Almost 10 years ago. (Granted, also on 8000 cores. But thanks to the concurrency...) https://www.businessinsider.com/whatsapp-64-billion-messages-24-hours-2014-4 https://www.businessinsider.com/whatsapp-64-billion-messages...
- tester457 3y ago> One has an embedded Javascript engine and does all kinds of pattern matching and string manipulation. Why did you decide to use an embedded JavaScript engine instead of pure go?