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 
-
-
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 -
-
-
This is a place where you seem to disagree with my post. The most important insight I wrote there is that it's not about senders or receivers, it's about muxing and demuxing. Muxers should send backpressure, demuxers physically cannot. People get this mixed up all the time.
-
I believe I'm echoing your post, not disagreeing with it. I understand "muxing into a queue" as essentially synonymous with "producer" or "writer".
- Još 2 druga odgovora
Novi razgovor -
-
-
Marius’s corollary: if backpressure is an explicit, not emergent, property of your system, it’s designed wrong.
-
Interesting. What's the difference between explicit vs. emergent backpressure? (I think I understand, but want to be sure.)
- Još 4 druga odgovora
Novi razgovor -
-
-
definitely. but "full" depends on how much latency you can allow before it has to ack that it will fail to deliver. don't put something in a queue if it is guaranteed to be too late, etc.
-
"Full" is well defined for queues and not a function of job latency SLAs...
Kraj razgovora
Novi razgovor -
-
-
Had a question about this from the article, "use backpressure from x to i". What would be a concrete example of muxers sending backpressure? Is it just queue i blocking on send to x? Or does x send a 503 on recv to i to signal backpressure? cc
@apenwarr -
Backpressure is abstract, easiest form is blocking and refusing to accept more work, returning an error also qualifies but is a little trickier
Kraj razgovora
Novi razgovor -
Č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.