Reply to post: "nothing new – it's an idea "from the early 1970s" "

Microservices guru warns devs that trendy architecture shouldn't be the default for every app, but 'a last resort'

W.S.Gosset Silver badge

"nothing new – it's an idea "from the early 1970s" "

Older than that, methinks.

In my experience, though, all the various changing memes have been merely current-hard+software-circs snapshots of the larger & unchanging oldiebutgoodie: "Common Sense": Keep moving parts together, separate at changes of "speed" (eg, scope, commonality of function, cost of infrastructure, frequency of user changes, etc).

Those separation decisions are often based on net results of externalities so can change over time as they do; eg huge rise in network speed:cost ratio, huge drop in cpu cost allowing users to have a mainframe each (in their pocket), drop in cost of various levels of virtualisation, etc etc etc.

Closest label I've seen to this/commonsense is "Responsibility Driven Programming".

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon


Biting the hand that feeds IT © 1998–2020