3 ms·

Couldn’t agree more. I also really like his idea of apps. Micro services introduces operational complexity and overhead. Most of the time, I see teams using i

• layer8 4y ago
  It’s not clear to me what he means by “apps”. These are either separate monoliths or seperate services.
  • Existenceblinks 4y ago
    > major things of value or value creation, possible core proposition, limited to a few apps From his tweet thread. I think it's like a separate product except it's under the same company or domain name. Many companies do this. A product could be just a backend server providing API with its own database. All that is scoped by "value" .. or a target market. This could imply that when micro services start to introduce to a system, we should question the value proposition of the whose system. We could mix up the engineering and business aspect.
• BeefWellington 4y ago
  I personally view anyone trying to design an application from the start using microservice architecture to be doing premature optimization. Microservices are meant to solve a scaling problem. Yes, design your applications in a modular way such that it becomes readily possible to stub parts of it out when the time comes. Don't start with a microservice focus or you're just begging someone else to beat you to market.