Embrace Events and let CRUD die

•

2 gostaram•697 visualizações

Talk delivered in Warsaw during 4Developer Conference 2016 More Domain-Driven Design related content at: https://domaincentric.net/

Engenharia

Clients
Database
DTO’s/DomainObjects
Data
Presentation
Service
Business Logic

Can’t we all become
join vegans?
Alberto Brandolini

What if we treat change
as a ﬁrst class citizen?

Book added
to library
Book lent
to reader
Book
extended
Book
returned

Event
1. something that happens or is
regarded as happening; an
occurrence, especially one of
some importance.

Current state is a left-fold
over past events
Greg Young

Given:
Book “DDD” was added to library
When:
Reader lends “DDD” book
Then:
Book “DDD” was lent to reader

Given:
Book “DDD” was added to library
Book “DDD” was lent to reader
When:
Reader lends “DDD” book
Then:
Exception: Book “DDD” already lent

odd-looking workshop
that has a massive consumption
of orange sticky notes
Alberto Brandolini

Book added
to library
Book extended
Book
added to
inventory
Reader
identity
conﬁrmed
Reader
registered
Book
reservation
placed
Book lent
to reader
Book recalled
Book returned

Reader
registered
Reader
identity
conﬁrmed
Identity
Conﬁrmed by
Carer
Deposit paid
Deposit Not
Paid
Reader
Account
Activated

Reader
registered
Reader
identity
conﬁrmed
Identity
Conﬁrmed by
Carer
Deposit paid
Deposit Not
Paid
Reader
Account
Activated
Registration

Book Lent
Lend Book
Reader
Book Already
Lent

Book
Returned
Late
Penalize Lock Account

Book Lent
Book
Returned
Book
Book
Extended
Return
Lend
Extend

Book
Returned
Book Added
Book Lent
Available
Books

Available
Books
Reader
Lend Book Book Lent

User
Command
Aggregate
External
System
Domain Event
Read Model
Policy
Command
UI
Picture that explains everything
by Alberto Brandolini

Mais conteúdo relacionado

Semelhante a Embrace Events and let CRUD die

Mimi Yin: Getting Things Done: Technology and PracticeSteve Williams

Code4Lib 2007: Hurry up please, it's timeeby

Володимир Довганик “5 typical features that make BA mad”Dakiry

Ethics 090412professorreyes

INSTG020 lecture for UCL DIS students - Project ManagementAndrew Preater

Email Is A Killer Application And It Is Killing Me Personal And Enterprise ...Peter Buck

Semelhante a Embrace Events and let CRUD die (6)

Mimi Yin: Getting Things Done: Technology and Practice

Code4Lib 2007: Hurry up please, it's time

Володимир Довганик “5 typical features that make BA mad”

Ethics 090412

INSTG020 lecture for UCL DIS students - Project Management

Email Is A Killer Application And It Is Killing Me Personal And Enterprise ...

Mais de Kacper Gunia

How a large corporation used Domain-Driven Design to replace a loyalty systemKacper Gunia

Rebuilding Legacy Apps with Domain-Driven Design - Lessons learnedKacper Gunia

The IoC HydraKacper Gunia

Forget about Index.php and build you applications around HTTP - PHPers CracowKacper Gunia

Domain-driven Design in PHP and Symfony - Drupal Camp Wroclaw!Kacper Gunia

OmniFocus - the #1 ‘Getting Things Done’ toolKacper Gunia

Scaling Symfony2 apps with RabbitMQ - Symfony UK MeetupKacper Gunia

Forget about index.php and build you applications around HTTP!Kacper Gunia

Dutch PHP Conference - PHPSpec 2 - The only Design Tool you needKacper Gunia

PHPSpec - the only Design Tool you need - 4DevelopersKacper Gunia

November Camp - Spec BDD with PHPSpec 2Kacper Gunia

Dependency Injection in PHPKacper Gunia

Code DojoKacper Gunia

SpecBDD in PHPKacper Gunia

Mais de Kacper Gunia (14)

How a large corporation used Domain-Driven Design to replace a loyalty system

Rebuilding Legacy Apps with Domain-Driven Design - Lessons learned

The IoC Hydra

Forget about Index.php and build you applications around HTTP - PHPers Cracow

Domain-driven Design in PHP and Symfony - Drupal Camp Wroclaw!

OmniFocus - the #1 ‘Getting Things Done’ tool

Scaling Symfony2 apps with RabbitMQ - Symfony UK Meetup

Forget about index.php and build you applications around HTTP!

Dutch PHP Conference - PHPSpec 2 - The only Design Tool you need

PHPSpec - the only Design Tool you need - 4Developers

November Camp - Spec BDD with PHPSpec 2

Dependency Injection in PHP

Code Dojo

SpecBDD in PHP

Último

Call Girls Narol 7397865700 Independent Call Girlsssuser7cb4ff

Work Experience-Dalton Park.pptxfvvvvvvvLewisJB

System Simulation and Modelling with types and Event SchedulingBootNeck1

Arduino_CSE ece ppt for working and principal of arduino.pptSAURABHKUMAR892774

Software and Systems Engineering Standards: Verification and Validation of Sy...VICTOR MAESTRE RAMIREZ

young call girls in Green Park🔝 9953056974 🔝 escort Service9953056974 Low Rate Call Girls In Saket, Delhi NCR

Vishratwadi & Ghorpadi Bridge Tender documentsSachinPawar510423

Gurgaon ✡️9711147426✨Call In girls Gurgaon Sector 51 escort servicejennyeacort

Transport layer issues and challenges - GuideGOPINATHS437943

Mine Environment II Lab_MI10448MI__________.pptxRomil Mishra

Research Methodology for Engineering pdfCaalaaAbdulkerim

home automation using Arduino by Aditya Prasadaditya806802

Input Output Management in Operating SystemRashmi Bhat

POWER SYSTEMS-1 Complete notes examplesDr. Gudipudi Nageswara Rao

Past, Present and Future of Generative AIabhishek36461

Virtual memory management in Operating SystemRashmi Bhat

CCS355 Neural Networks & Deep Learning Unit 1 PDF notes with Question bank .pdfAsst.prof M.Gokilavani

TechTAC® CFD Report Summary: A Comparison of Two Types of Tubing Anchor Catcherssdickerson1

Internet of things -Arshdeep Bahga .pptxVelmuruganTECE

Risk Assessment For Installation of Drainage Pipes.pdfROCENODodongVILLACER

Embrace Events and let CRUD die

1. Embrace Events and let CRUD die @cakper

2. Goal

3. CRUD

4. Who knows what CRUD is?

5. Clients Database DTO’s/DomainObjects Data Presentation Service Business Logic

6. Well known

7. Easy to sell

8. Tooling

9. Who never had problems with it?

10. Soft Delete

11. Audit

12. Calculating changes

13. Scaling

14. 3rd Normal Form

15. Optimised for write

16. Large & slow queries

17.

18. But that’s good!

19. In the WRITE context

20. What is your write:read ratio?

21. Some of the applications are read heavy

22. Joins are expensive

23. Can’t we all become join vegans? Alberto Brandolini

24. Denormalisation

25. Read models

26. You have to maintain two models now

27. What if we treat change as a ﬁrst class citizen?

28. Event Sourcing

29. Book added to library Book lent to reader Book extended Book returned

30. Event 1. something that happens or is regarded as happening; an occurrence, especially one of some importance.

31. Current state is a left-fold over past events Greg Young

32. Aggregate

33. Consistency boundary

34. Consuming commands

35. Producing events

36. Reconstituting from history

37. Snapshotting

38. Testing

39. State-based testing

40. We test what changed

41. What about things that didn’t?

42. Behaviour-based testing

43. Given: Book “DDD” was added to library When: Reader lends “DDD” book Then: Book “DDD” was lent to reader

44. Given: Book “DDD” was added to library Book “DDD” was lent to reader When: Reader lends “DDD” book Then: Exception: Book “DDD” already lent

45. Event Store

46. Append-only

47. Scaling

48. Optimistic locking

49. Retries

50. Integration

51. MQ

52. REST

53. 2PC

54. Eventual consistency

55. Projections

56. Query optimised storage

57. Task-based UI

58. Business Value   of Events

59. Insight into past data

60. Business Intelligence

61. Legal compliance

62. Debugging

63. How do we get there?

64. Event Storming

65. odd-looking workshop that has a massive consumption of orange sticky notes Alberto Brandolini

66.

67. How does it work?

68. Start by capturing Domain Events

69. Domain Event

70. Book added to library Book extended Book added to inventory Reader identity conﬁrmed Reader registered Book reservation placed Book lent to reader Book recalled Book returned

71. Behavioural mindset

72. Timeline

73. Book added to library Book extended Book added to inventory Reader identity conﬁrmed Reader registered Book reservation placed Book lent to reader Book recalled Book returned

74. Naming

75. Book added to library Book extended Book added to inventory Reader identity conﬁrmed Reader registered Book reservation placed Book lent to reader Book recalled Book returned

76. Complexity

77. Reader registered Reader identity conﬁrmed Identity Conﬁrmed by Carer Deposit paid Deposit Not Paid Reader Account Activated

78. Pin point risks

79. Risk

80. Reader registered Reader identity conﬁrmed Identity Conﬁrmed by Carer Deposit paid Deposit Not Paid Reader Account Activated Registration

81. Right People

82. Event sources

83. Users

84. Command

85. Book Lent Lend Book Reader Book Already Lent

86. Other events

87. Policy