3 ms·
He has an entire section on "Post-REST: Persistent connections" which you seem to have missed. "As for the rest of it, sure, you might have a queue, or som
by jimbokun 8y ago
He has an entire section on "Post-REST: Persistent connections" which you seem to have missed.
"As for the rest of it, sure, you might have a queue, or some orchestration layer. Is that your consumer-facing API? Just b/c I push a message into some queue implementation does not mean I want to expose that implementation to my caller."
REST for external APIs, and queues for internal, more tightly coupled micro services seems like a good way to architect things.
- otabdeveloper1 8y ago> He has an entire section on "Post-REST: Persistent connections" which you seem to have missed. That section is really stupid. He goes on about HTTP/2 and QUIC while seemingly being ignorant of HTTP/1.1's existence. Keep-alive has existed for decades. Use it, it solves the problem definitively without adding any new ones. (People have yet to figure out what the point of HTTP/2 and QUIC was. Except for Google's not-invented-here syndrome, of course.)