1. 10
  1.  

  2. 3

    A common corollary to entity services is the idea of “stateless business process services.” I think this meme dates back to last century with the original introduction of Java EE, with entity beans and session beans. It came back with SOA and again with microservices.

    This is a key point, and one I don’t see made enough around the microservices hype. If people saw the historical connection here, maybe they’d stop thinking these approaches are so hip and novel. Systems have crumbled under these designs before; study history or repeat it. (And, of course, sometimes these designs had successes, too; what were the circumstances?)

    1. 5

      Systems have crumbled under these designs before; study history or repeat it.

      The amount of work expended to avoid thinking critically about your particular context in the face of whatever the current fad is enormous: “A week in the lab can save 15 minutes in the library.”

      1. 2

        My only regret is that I have but one upvote to give for my country.

      2. 2

        This is what happens when what’s hip and new comes from people who dismiss the projects and teams that have experience out of hand because they’re seen as dinosaurs / enterprise wankery / other euphemisms for “old therefore slow and irrelevant”.

      3. 1

        Aren’t these “services” merely what we called (distributed) “applications” yesterday? Perhaps using a new name makes us all feel like we can now better write systems composed of separate “applications”. It certainly makes the consultants and framework vendors happy that they have something new to sell.