I'm grateful for the Rust async stuff if only because of the discussions it's prompting across the internet, I'm learning a lot about async models in other programming languages — and also the absolute bonkers stuff some programmers believe about queueing theory 
-
-
3. Producers trying to write to a full queue should block, providing backpressure. Consumers reading from a queue that can't process the item in a timely fashion should drop the item and take the next. There is no other sane strategy for dealing with load.
Prikaži ovu nit -
4. Queues belong at the edges of a system, not within it. Remember: queues only solve burstiness, and burstiness can only happen when input size/rate is unknown, and that only happens at the borders. Systems themselves should be deterministic and synchronous.
Prikaži ovu nit -
There's plenty more to learn but those 4 rules will stop you from shooting yourself in the foot. Shamelessly adapted from https://apenwarr.ca/log/20170814 and https://programmingisterrible.com/post/162346490883/how-do-you-cut-a-monolith-in-half …
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
queue up on disk isn't unbounded, but can be large enough that you don't know ahead of time what a reasonable point is to just start losing messages. everything is finite. but you don't necessarily know the cap.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.