News for hackers. Stuff that matters.
Re:Post-REST by jimbokun on Monday November 19, 2018 @04:28PM (#18489907)
He has an entire section on "Post-REST: Per­sis­tent con­nec­tions" 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.

Re:Post-REST by otabdeveloper1 on Tuesday November 20, 2018 @08:15AM (#18493539)
> He has an entire section on "Post-REST: Per­sis­tent con­nec­tions" 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.)