3 ms·
The web got faster, and it became easier to build and consume APIs, so we eliminated the need for an intermediary. More "native" event-driven architectures emer
by bdcravens 2y ago
The web got faster, and it became easier to build and consume APIs, so we eliminated the need for an intermediary. More "native" event-driven architectures emerged.
- sublinear 2y agoI was going to say something like this but you beat me to it. Moving more application state and logic to frontend SPAs reduced the need for so much backend work. Backends are faster and more robust when they don't need to manage the "session" so much and instead just validate the final API request data and if they queue up anything it's those actions that require database transactions or to publish a message.
- bigiain 2y ago"The web got faster" [citation needed] Sure the network has gotten faster, but with the few exceptions like Craigslist and this site, in general "the web" has gotten way way slower in real terms, at least as I see it. These days megabytes of javascript (or webassembly) seems to be required just to display pages with a kilobyte of two of actual text content...
- zztop44 2y agoBrowsing one of those bloated monstrosities on a nice new MacBook with a 2gbps connection is still a lot faster and nicer than Craigslist on old Celeron at 56k.
- bdcravens 2y agoI should have clarified that I mean the backend infrastructure is much faster; I'm not talking about the client's experience (since rarely do end clients interact with message queues)
- tekla 2y agoIt's weird that people say this and yet the web feels very slow.
- bdcravens 2y agoI should have clarified that I mean the backend infrastructure is much faster; I'm not talking about the client's experience (since rarely do end clients interact with message queues) (in other words, by "web" I mean the network, not the content)