Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Domain-Driven Design & REST

Domain-Driven Design & REST

Slides of the talk I gave at Spring I/O 2016.

@springcentral

Oliver Drotbohm

May 19, 2016
Tweet

More Decks by Oliver Drotbohm

Other Decks in Programming

Transcript

  1. 2

  2. 9

  3. 9

  4. Stringly typed code 12 public class Customer { private Long

    id; private String firstname, lastname, email; … }
  5. Stringly typed code 13 public class SomeService { public void

    createUser(String firstname,
 String lastname, String email) { … } }
  6. 14 public class Customer { private Long id; private Firstname

    firstname; private Lastname lastname; private EmailAddress emailAddress; … }
  7. Still, they’re worth it. 16 See „Power Use of Value

    Objects in DDD“ by Dan Bergh Johnsson.
  8. 18 @Value public class Customer { UUID id = UUID.randomUUID();

    Firstname firstname; Lastname lastname; EmailAddress email; @Value static class EmailAddress { String value; } }
  9. 30 Shipping Accounting Catalog Orders User
 Registration Accounting Payment information

    Billing Address Shipping Shipping address Customer Product
  10. 34 Level 0: No events at all Level 1: Explicit

    operations Level 2: Some operations as events
  11. 37 Level 0: No events at all Level 1: Explicit

    operations Level 2: Some operations as events
  12. 37 Level 0: No events at all Level 1: Explicit

    operations Level 2: Some operations as events Level 3: Event Sourcing
  13. 48 Aggregate Root / Repository Collection / Item Resources IDs

    URIs @Version ETags Last Modified Property Last Modified Header Relations Links
  14. Method URI Action Step POST /orders Create new order 1

    POST/PATCH /orders/{id} Update the order (only if "payment expected") 2 DELETE /orders/{id} Cancel order (only if "payment expected") 3 PUT /orders/{id}/payment Pay order (only if "payment expected") 4 Barista preparing the order GET /orders/{id} Poll order state 5 GET /orders/{id}/receipt Access receipt DELETE /orders/{id}/receipt Conclude the order process 6
  15. Method Resource type Action Step POST orders Create new order

    1 POST/PATCH update Update the order 2 DELETE cancel Cancel order 3 PUT payment Pay order 4 Barista preparing the order GET order Poll order state 5 GET receipt Access receipt DELETE receipt Conclude the order process 6
  16. 52 GET /orders { „_links“ : { „cancel“ : {

    „href“ : … }, … „createdDate“ : …, „status“ : „Payment expected“ … }
  17. 53 GET /orders { „_links“ : { „cancel“ : {

    „href“ : … }, … „createdDate“ : …, „status“ : „Payment expected“ … }
  18. 56 GET /orders { „_links“ : { „cancel“ : {

    „href“ : … }, … „createdDate“ : …, „status“ : „Payment expected“ … }
  19. Web Service Repository - Orders Spring Data Spring Data
 REST

    Payment Spring Data Manual
 implementation Manual
 implementation