3 ms·
Dependency issues will worsen over time. You’re just building a monolith with it. API interfaces should be dumb and simple. Neither REST (Swagger rules) or Grap
by ChicagoDave 4y ago
Dependency issues will worsen over time. You’re just building a monolith with it. API interfaces should be dumb and simple. Neither REST (Swagger rules) or GraphQL are healthy long-term implementations.
- za3faran 4y agoGenuine question: what are healthy long term implementations? gRPC?
- ChicagoDave 4y agoUI needs data which can be represented in a read model. Read models can be represented however the receiver needs it. UI’s should rarely need to make complex or large queries. So if I’m displaying data for one subject (customer) I should have a read model that delivers everything I need to display. If I need an Orders or Inventory read model, that’s fine. Sending data to an api for creation or updating should be simple business commands and not based on resources or transport. My mantra is to think like the business, not like an API or data store.