I agree with some of the other older hands in here, much of technology 'changes' are rarely anything new, just new names and tweaked implementations of much the same core elements.
New generations like new names, worded in terms they become familiar with. Doesn't make them less valid, but often not as new as perceived.
Much like the music business, new bands put out covers of old music, new audience thinks it's a great new sound, but underneath it may be very much the same old song.
This is really not true. While every industry, and especially Software Engineering, is prone to hype, the reason things become popular is that they deliver real value.
REST API's and microservices are a design that originated when software teams started growing in size and didn't want to lose the agility they observed when having control of their complete stack. It was enabled by a fundamental shift in infrastructure: previously, everything was managed by dedicated infra teams, but Containers and Container Orchestrators gave development teams control of their deployments. The old model of monolithic services stood in the way of developers who had access to this new power, and hence microservices were invented to address that.
I could give you similar reasons for the rise of Big Data, Infra as Code etc. Every one of these changes are driven by changes in fundamental technologies. They aren't fads.
When I read the article and looked at the e-commerce diagram, all I could think was "hmm, this seems to be pretty much exactly how we implemented the early versions of amazon.com, except without any of the this technology or terminology".
