My Web Front-End CQRS slides from Devsum 2012

1. Web Front-End CQRS

2. The crazy architect enters the
room

4. ”We are doing CQRS!”

5. WAT?

6. Command and Query
Responsibility Segregation

7. What?

8. Commands can’t return data
Queries can only return data

9. And how are we doing that?

10. Command Handlers
Event Handlers
Service bus
Message queue
Event stores
Projections

11. NServiceBus
MassTransit
MsMQ
EventStore
RabbitMQ
Common Domain

12. Front-end?

13. Emil Cardell
@emilcardell
unwillingcoder.tumblr.com

14. CQRS Web Front-End Journey

15. Going from CRUD to CQRS

16. Teach our front-end to speak
CQRS

17. Just in time Front-End CQRS

18. Font-end CQRS domination

19. Why CQRS?

20. Reliability
Scalability

21. Reliability is to never loose
data and to never go down
even if hardware goes down

22. Scalability to scale linear by
distributing you application
to multiple servers

23. Separate in to parts only
responsible for one thing

24. It gives us focus to deliver
value faster

25. Replaceability

26. Distribute

27. UI keeps it togeather

28. How does a distributed
system effect the UI?

29. Eventual Consistency

30. ΔTserver vs ΔTclient

31. In the beginning

33. Same same but different

34. Ugly CRUD syntax

35. Not separated

36. Why FubuMVC?

37. Speak the same language as
our domain. There is nothing
in our domain called
controller.

38. Separation of concerns
one class = one function
RESTish
methods = http methods

40. Questions?

41. Reliable

42. Scalable

43. Replaceable

44. Distributed

45. Have courage to experiment,
respect your peers and keep
it simple

46. Emil Cardell
@emilcardell
unwillingcoder.tumblr.com
http://mvc.fubu-project.org/
http://jquery.com/
http://benalman.com/projects/jquery-
message-queuing-plugin/