It might help to simplify the complexity of software modeling. If you want to learn more, I highly recommend the book. The publication is made public so others can consume and reconstruct it.Ĭongratulations on getting this far. Repository: storing and loading the Aggregate.įactory: handling the creation of the Aggregate.ĭomain Service: orchestrate multiple Aggregate.ĭomain Event: a description of what has happened to the Aggregate. It is used to describe the property of Entity.Īggregate: a collection of Entities that are bounded together by Aggregate Root (which is also an entity). HTTP 1.1 vs HTTP 2, Follows request-response. Only required data will be fetched from server. Value Object: a domain object without ID. GraphQL vs REST vs gRPC Data fetch, Efficient fetching of data. Alhasil, kita dapat mengetahui API mana yang lebih mudah digunakan dan efisien dalam mengambil data. There is a lot of content in this book, so I'll summarize the basics.Įntity: a domain object that has ID and life cycle. Pada artikel kali ini saya akan membahas mengenai perbedaan GraphQL dan REST API dalam proses kita mengakses endpoint dari masing-masing API dan bagaimana respon yang diberikan oleh kedua API tersebut. It explained a methodology to model a complex business. DDD was introduced in Eric Evans’ classic book “Domain-Driven Design: Tackling Complexity in the Heart of Software”. In our previous post, we discussed the benefits and drawbacks of two of the most popular API models REST and gRPC. Message brokers (e g NATS, Rabbit) provide a higher-level abstraction in which a client sends messages to an intermediate service called a broker (this could be done using gRPC) and the broker may queue messages and either ship them directly to services (push) or wait for a service to check its subscription (pull).
0 kommentar(er)
