3 ms·
> What about simply "services"? Let's call them "tiers". I think 3 is a reasonable number..
by js8 7y ago
> What about simply "services"?
Let's call them "tiers". I think 3 is a reasonable number..
- MosheZada 7y agoI’m ok with whatever you call them, just don’t split a single codebase into 20 services and over 10 databases
- disintegore 7y ago"Tiers" imply some sort of vertical partitioning. These "non-micro" services may coexist on a layer, transcend boundaries, overlap, etc. In any case, there's already such a term. It's called SOA: https://en.wikipedia.org/wiki/Service-oriented_architecture https://en.wikipedia.org/wiki/Service-oriented_architecture. Microservices arguably evolved out of this.
- aliswe 7y agoNo, tiers comprise slicing the application horizontally by technology, basically, ie. "All database stuff here" and "all frontend stuff here". To me that's like "let's put all the house sinks in one room to ease repairs for the craftsman". Services is more like feature folders? Where you define everything you need related to a VERTICALLY sliced part of your application, ie. Products, or whatever.