Crafting Domain-Driven Designed REST APIs - Julien Topçu - DDD Europe 2022

Domain-Driven Design Europe 2022

You have just coded your business logic by applying the principles of Domain-Driven Design! But when comes the time to write your API, you are facing a serious issue! All the intention and the expression of your domain go up in smoke to fit the blankness methods GET, POST, etc.

Denatured by the REST layer, the business workflow is then deported on the consumer side to compensate for the limited vocabulary of this well-known CRUD protocol...

During this talk, we will see how to bring the business intent back inside the REST API by finally being able to expose our domain services and agregates' methods. The business workflow will also be encapsulated in the REST API in order to have the power to guide our consumers through the workflow of our domain.

About Julien Topçu

I like to craft software with high business value using techniques from Domain-Driven Design, all powered by Xtreme Programming in the Kanban #NoEstimates philosophy. Member of the OWASP foundation, I evangelise on application security techniques in order to avoid being hacked properly.

[kurianjpanjikaran]

Fantastic! Loved this concept of workflow oriented REST APIs.

[AvineshSinghSaab]

Despite the specific title, there is so much to learn from this talk that I have re-watched it thrice. Beautifully explained, love the energy and very practical!

[DevOpsCraftsman]

Very interesting talk! I think that lot of advises are pretty actionable quickly on most projects.

Digression: I'm very frightened by the state of the audience...

I'm feeling that DDD is getting so mainstream that people are coming to talks just because it's "fashion" theses days to go to a DDD conf.

[farewelltitet]

Thanks you, this is a very interesting talk. I'm not familiar with hateoas, how about the request which perform an action that need a large body, we can't put it in url, as usual we make a post request with a json body.

[nichtverstehen]

well, basically, all we need is to go back to server-rendered content and forget about that rich-client crap. i totally agree with that.
front-end should be simply about the look. functionality must be handled in single place - the back-end.

simplicity is the ultimate sophistication -- leonardo da vinci

[BeekuBird]

REST uniform interface isn't the same as CRUD.

[smithdragon]

so we don’t need pass post body as json? If we need pass body as json how do we return it through links

[chauchau]

IMHO, he is right on the problems but wrong on the solutions