I’ve been thinking about some of the current trends and hyped terms/concepts lately.
On one hand I’m convinced we’re coming out of the inflection point chaos that has
consumed our industry over the past several years, and on the other hand any time
things start to stabilize the hype-masters come out of the woodwork because there’s
money to be made. This isn’t new – see my SOA,
dollar signs and trust boundaries
post from 2004…
In this post I’m going to briefly talk about microservices, containers, and devops.
What’s interesting about that 2004 post is that it is one of quite a number of posts
on service-oriented concepts, and most of my focus at the time was on “pure
service-oriented” thinking – which never took off – and which is now known by the
newly-trendy term “microservices”.
In other words, this “new” microservices
stuff is just the
type of SOA that we should have been doing for the past decade. Oops.
As always, when an old idea comes back around under a new name, we owe it to ourselves
to ask whether there’s anything different this time that might make the idea more
successful than it was last time?
For example, it took us decades to get asynchronous programming to become
mainstream. We tried...(Read whole news on source site)