3 ms·
Speaking from my own experience message queues haven’t disappeared as much as have been abstracted away. For example enqueue to SQS + poll became invoke server
by vishnugupta 2y ago
Speaking from my own experience message queues haven’t disappeared as much as have been abstracted away. For example enqueue to SQS + poll became invoke server less process. There is a message queue in there somewhere just that it’s not as exposed.
Or take AWS SNS which IMO is one level of abstraction higher than SQS. It became so feature rich that it can practically replace SQS.
What might have disappeared is those use cases which used Queues to handle short bursts of peak traffic?
Also streaming has become very reliable tech so a class of usecases that used Queues as streaming pipe have migrated to the streaming proper.
- akira2501 2y ago> There is a message queue in there somewhere just that it’s not as exposed. It's still pretty exposed. You can set redelivery timeouts and connect a dead letter queue to lambda functions. Even just the lambda invoke API is obviously just a funny looking endpoint for adding messages to the queue. > as much as have been abstracted away In AWS in particular into EventBridge which further extends them with state machines. They've become the very mature corner stone of many technologies.
- 1oooqooq 2y agogood point. tcp was justified at some point in it's birth a queueing component. today nobody dates to think of it as such.