Web Front-End CQRS

The crazy architect enters the room

”We are doing CQRS!”

WAT?

Command and Query Responsibility 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 speak CQRS

Just in time Front-End CQRS

Font-end CQRS domination

Why CQRS?

ReliabilityScalability

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

Scalability to scale linear by distributing you application to multiple servers

Separate in to parts only responsible for one thing

It gives us focus to deliver value faster

Replaceability

Distribute

UI keeps it togeather

How does a distributed system 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 as our domain. There is nothing in our domain called controller.

Separation of concernsone class = one functionRESTishmethods = http methods

Questions?

Reliable

Scalable

Replaceable

Distributed

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

Emil Cardell@emilcardellunwillingcoder.tumblr.com

http://mvc.fubu-project.org/http://jquery.com/http://benalman.com/projects/jquery-message-queuing-plugin/