4 ms·

That's microservices. Microservices handle a bounded domain. At least in traditional advice for splitting microservices. The microservice provide an api for tha

That's microservices. Microservices handle a bounded domain. At least in traditional advice for splitting microservices. The microservice provide an api for that domain.

goodpoint 6y ago
No, that's SOA. Microservices are almost always described as quite small.
- UK-Al05 6y ago
  The "Building Microservices" book, which used to be the goto book for microservices suggests on page 31 to page 38 that bounded domains are a good model for microservices. The main difference between SOA and microservices is dump pipes vs smart pipes. Not service size. As explained in that book. Most people trying to implement microservices seem to have not read much about them outside of blogs.
  - ex_amazon_sde 6y ago
    Quoting some book does not change the fact that most people understand SOA as being team or domain-bound and microservices as being much smaller.
    - UK-Al05 6y ago
      I'm assuming most people adopting micro-services weren't even around when SOA was a big thing. People not reading the literature then implementing it badly isn't problem with the idea. In the same way that not studying calculus then doing badly isn't a problem of calculus. Most of these issues around microservices like how to split them so they don't cause issues, are known and solved problems. Just people have not read the literature other than the odd "blog". Like don't do microservices, for your first iteration. Backwards compaitble apis, and understand your bounded contexts from your first iteration before you try. They end up creating chatty nano services with tons of version fixed cross dependencies.
    - tdeck 6y ago
      Interesting because I always thought SOA was just a slightly older term for microservices.
jblwps 6y ago
Doesn't a "service" handle a domain?
- UK-Al05 6y ago
  Putting micro in front of service was a bad idea. Lots of people have the wrong idea because of that.

That's microservices. Microservices handle a bounded domain. At least in traditional advice for splitting microservices. The microservice provide an api for that domain.

goodpoint 6y ago

No, that's SOA. Microservices are almost always described as quite small.

UK-Al05 6y ago
The "Building Microservices" book, which used to be the goto book for microservices suggests on page 31 to page 38 that bounded domains are a good model for microservices. The main difference between SOA and microservices is dump pipes vs smart pipes. Not service size. As explained in that book. Most people trying to implement microservices seem to have not read much about them outside of blogs.
- ex_amazon_sde 6y ago
  Quoting some book does not change the fact that most people understand SOA as being team or domain-bound and microservices as being much smaller.
  - UK-Al05 6y ago
    I'm assuming most people adopting micro-services weren't even around when SOA was a big thing. People not reading the literature then implementing it badly isn't problem with the idea. In the same way that not studying calculus then doing badly isn't a problem of calculus. Most of these issues around microservices like how to split them so they don't cause issues, are known and solved problems. Just people have not read the literature other than the odd "blog". Like don't do microservices, for your first iteration. Backwards compaitble apis, and understand your bounded contexts from your first iteration before you try. They end up creating chatty nano services with tons of version fixed cross dependencies.
  - tdeck 6y ago
    Interesting because I always thought SOA was just a slightly older term for microservices.

jblwps 6y ago

Doesn't a "service" handle a domain?

UK-Al05 6y ago
Putting micro in front of service was a bad idea. Lots of people have the wrong idea because of that.