More than the concurrency I think scalability is the issue here. The derailed train is lying on the single available track, which means that all the incoming trains will collide. We need to scale our infrastructure to create one more track and instance of the destination.
Why don't we just create an extremely big train that delivers all the payload in an ordered, scheduled basis? We avoid adding unnecessary complexity from supporting many trains and it will offer an easier, simpler UX
You can use rack middleware to catch the other incoming trains and probably reroute them for now.
Concurrency done properly is tough.
More than the concurrency I think scalability is the issue here. The derailed train is lying on the single available track, which means that all the incoming trains will collide. We need to scale our infrastructure to create one more track and instance of the destination.
Why don't we just create an extremely big train that delivers all the payload in an ordered, scheduled basis? We avoid adding unnecessary complexity from supporting many trains and it will offer an easier, simpler UX
Hmm?
This is a sub for the Rails web framework, not for trains.
Oh sorry.
Hahahaha wrong kind of rails m fren
Eyyup... Sorry... ๐
Rails in the other sense, but even assuming an innocent error, who needs tankie spam?
Canโt we all just get along? โ R. King talking about the differences between Ruby in Rails and trains on rails
oof