Web Front-End CQRS
The crazy architect enters theroom
”We are doing CQRS!”
WAT?
Command and QueryResponsibility Segregation
What?
Commands can’t return dataQueries can only return data
And how are we doing that?
Command HandlersEvent HandlersService busMessage queueEvent storesProjections
NServiceBusMassTransitMsMQEventStoreRabbitMQCommon Domain
Front-end?
Emil Cardell@emilcardellunwillingcoder.tumblr.com
CQRS Web Front-End Journey
Going from CRUD to CQRS
Teach our front-end to speakCQRS
Just in time Front-End CQRS
Font-end CQRS domination
Why CQRS?
ReliabilityScalability
Reliability is to never loosedata and to never go downeven if hardware goes down
Scalability to scale linear bydistributing you applicationto multiple servers
Separate in to parts onlyresponsible for one thing
It gives us focus to delivervalue faster
Replaceability
Distribute
UI keeps it togeather
How does a distributedsystem effect the UI?
Eventual Consistency
ΔTserver vs ΔTclient
In the beginning
Same same but different
Ugly CRUD syntax
Not separated
Why FubuMVC?
Speak the same language asour domain. There is nothingin our domain calledcontroller.
Separation of concernsone class = one functionRESTishmethods = http methods
Questions?
Reliable
Scalable
Replaceable
Distributed
Have courage to experiment,respect your peers and keepit simple
Emil Cardell@emilcardellunwillingcoder.tumblr.comhttp://mvc.fubu-project.org/http://jquery.com/http://benalman.com/project...
Web Front-End CQRS
Web Front-End CQRS
Web Front-End CQRS
Upcoming SlideShare
Loading in …5
×

Web Front-End CQRS

1,502 views

Published on

My Web Front-End CQRS slides from Devsum 2012

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,502
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
20
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Kod. Från CRUD till CQRS anrop
  • Kod. Från CRUD till CQRS anrop
  • FUBU Convetions > Command och Query1. Separatingoutcommands and queries.
  • Web Front-End CQRS

    1. 1. Web Front-End CQRS
    2. 2. The crazy architect enters theroom
    3. 3. ”We are doing CQRS!”
    4. 4. WAT?
    5. 5. Command and QueryResponsibility Segregation
    6. 6. What?
    7. 7. Commands can’t return dataQueries can only return data
    8. 8. And how are we doing that?
    9. 9. Command HandlersEvent HandlersService busMessage queueEvent storesProjections
    10. 10. NServiceBusMassTransitMsMQEventStoreRabbitMQCommon Domain
    11. 11. Front-end?
    12. 12. Emil Cardell@emilcardellunwillingcoder.tumblr.com
    13. 13. CQRS Web Front-End Journey
    14. 14. Going from CRUD to CQRS
    15. 15. Teach our front-end to speakCQRS
    16. 16. Just in time Front-End CQRS
    17. 17. Font-end CQRS domination
    18. 18. Why CQRS?
    19. 19. ReliabilityScalability
    20. 20. Reliability is to never loosedata and to never go downeven if hardware goes down
    21. 21. Scalability to scale linear bydistributing you applicationto multiple servers
    22. 22. Separate in to parts onlyresponsible for one thing
    23. 23. It gives us focus to delivervalue faster
    24. 24. Replaceability
    25. 25. Distribute
    26. 26. UI keeps it togeather
    27. 27. How does a distributedsystem effect the UI?
    28. 28. Eventual Consistency
    29. 29. ΔTserver vs ΔTclient
    30. 30. In the beginning
    31. 31. Same same but different
    32. 32. Ugly CRUD syntax
    33. 33. Not separated
    34. 34. Why FubuMVC?
    35. 35. Speak the same language asour domain. There is nothingin our domain calledcontroller.
    36. 36. Separation of concernsone class = one functionRESTishmethods = http methods
    37. 37. Questions?
    38. 38. Reliable
    39. 39. Scalable
    40. 40. Replaceable
    41. 41. Distributed
    42. 42. Have courage to experiment,respect your peers and keepit simple
    43. 43. Emil Cardell@emilcardellunwillingcoder.tumblr.comhttp://mvc.fubu-project.org/http://jquery.com/http://benalman.com/projects/jquery-message-queuing-plugin/

    ×