Lokad.CQRS - Getting Started

In the Salescast technology announcement article some time ago I've mentioned that Lokad is planning to share experience, technological principles and frameworks behind this project with the community. The process has just started.

Lokad.CQRS is another open source project by Lokad. It is based on our experience of working with scalable applications, efficient development of enterprise solutions and dedication to Windows Azure (all the things needed to deliver massively scalable forecasting services for businesses). There also was a practice of doing research and development, learning from mistakes and publishing results for the community to benefit from.

This project aims to provide field-tested guidance and .NET Application Blocks to help architects and developers deliver solutions ranging from high-traffic web sites to feature-rich enterprise solutions.

In a sense, Lokad.CQRS is merely an adaptation of well-known principles and practices to the specific field of Windows Azure. These well-known principles include all the references and open source projects mentioned in xLim and CQRS series (but are not limited to them).

Given all that, first drops of the code from the Lokad codebase are available within the Open Source Lokad.CQRS project at Google Code (mirror at CodePlex).

Lokad.CQRS might interest:

• Architects and technology leaders planning to design and deliver scalable enterprise solutions with Windows Azure;
• Developers considering building such applications;
• Students learning about messaging, enterprise integration, CQRS, DDDD and scalable software;
• Everybody else who is interested.

Currently trunk includes the latest port of Lokad.CQRS engine for Windows Azure environment. Porting more essential parts of CQRS architecture is in the Roadmap. However, this engine already comes with some base features:

Feature Highlights:

• Publish/subscribe
• Handle commands and events
• Scheduled tasks
• Predefined deployment profiles

Some Advanced Features:

• Non-intrusive infrastructure for hosting your business domain
• Extend and plug CQRS roles with custom functionality
• Various scalability options

There is a little bit of documentation and some samples, too. From now on I'm planning to walk through the samples provided with the source code, as they get published. Obviously we start with really simple ones, moving to more elaborate scenarios, as more features get ported to the public domain of Lokad.CQRS. Project documentation will be expanded along the way.

Here are some basic links to get you started:

• Getting started with Lokad.CQRS
• Community and FAQ
• Download Samples

All feedback and participation in the project and its community is highly appreciated.

In the next blog post on the subject we'll walk over the first sample and the importance of messaging in CQRS solutions.

Comments

[qwerty]

your lokad.com site is down:

Failed to access IIS metabase.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.

[Rinat Abdullin]

@Querty - when exactly did this happen? We didn't notice any failures and the site is up and running now.

[Matthieu]

There's a relation between Lokad.CQRS and others Lokad cloud projects like Lokad.cloud (the storage library) ? In any case it's nice to see application like that to show code about CQRS architecture.

[Rinat Abdullin]

Matthieu, relation between Lokad.Cloud and Lokad.Cqrs is shown in the next article. As for the samples - series of articles on Lokad.CQRS are already planned. I'll start posting them soon.

[qwerty]

>>> @Querty - when exactly did this happen?

Please check datetime of my first comment. It was arounfd that time and lasted at least 10 minutes. After 10 minutes I stopped trying to open lokad.com...

[Rinat Abdullin]

@Querty, thank you. As investigated, it was a short term issue at the data-center of our web site, that hopefully should not happen again.