Domain Driven Design Rest Api
So if you want a module to calculate a bunch of charges for a contract you might have a billingservice class with a method for doing the calculation.
Domain driven design rest api. A great api design strategy is critical for api product adoption and sustainable application development 4. Dependency injection for configs etc. While domain driven design is supposed to take care of complexity in the very core of software rest is usually treated as a plain remoting technology.
Domain driven design application architecture api design event architectures. Pony orm for relational data. In rest the primary role of your api is hypermedia data transfer which is to say converting domain concepts to from hypermedia representations.
Falcon gunicorn for http server. Designing apis and microservices using domain driven design 1. We re going to discover how a good domain design is essential to building a great rest api in the first place and.
That s probably best described as an application concern rather than a presentation concern. Domain driven design applies to the implementation side of things including api implementation while resources in rest api drive the api design and contract. Applying domain driven design to apis and microservices james higginbotham launchany 2.
Api resource selection should not depend on the underlying domain implementation details. All configs via environment variables. Your rest api is running in a user application that talks to the application layer layer 7.
Oliver gierke explores some commonalities of domain driven design and rest and how to create rest apis that are driven by the domain. In this talk we re going to explore some of their commonalities in respect to designing both the domain and the resources. The most common style of interface to a module is to use procedures or object methods.