-
Recent Posts
Recent Comments
- elopezrios on Force .NET application to run in 32bit process on 64bit OS
- mck ☠ on Migrating to Git
- Michael Freidgeim on Dynamic reflection versus static reflection
- Groverboy on Synchronizing calls to the UI in a multi-threaded application
- Rvsawant21 on Step-by-step Introduction to Delegates and Lambda Expressions
Archives
Categories
- asynchronous
- book
- bootstrapper
- brownfield
- BUILD
- ClickOnce
- commands
- Conference
- CQRS
- data binding
- delegates
- design
- developer
- didactics
- Event sourcing
- Fluent NHibernate
- fluent Silverlight
- framework
- Git
- hiring
- How To
- installation
- interactive extensions
- introduction
- job
- jQuery
- lambda expressions
- learning
- legacy code
- methodology
- misc
- Mock
- mocking framework
- Mono
- Mono Cecil
- MSIL
- multi threading
- MVVM pattern
- NHibernate
- no-database
- NSIS
- patterns
- personal
- plugins
- practices
- presentation
- PTOM
- refactoring
- reflection
- reporting
- review
- Setup
- Silverlight
- SOLID
- Styles and Templates
- TDD
- tutorial
- Uncategorized
- validation
- Windows
- WIX
- Workflow
Meta
Category Archives: CQRS
Anders Hejlsberg Is Right: You Cannot Maintain Large Programs In JavaScript
There’s a quote over on a Channel 9 video of Anders Hejlsberg: Erik Meijer: Are you saying you cannot write large programs in JavaScript? Anders Hejlsberg: No, you can write large programs in JavaScript. You just can’t maintain them. With … Continue reading
Adding Request / Reply To The Application Controller
Back in December of 2009 I had a post on using various messaging patterns within an application controller as part of an application’s architecture. One of the patterns that I distinctly left out was request/reply. At the time I had … Continue reading
Comments Off
CQRS Performance Engineering: Read vs Read/Write Models
I’ve used a lot of different architectures, patterns and implementations that revolve around the core concept of command-query separation (CQS) and the more recent label of command-query responsibility separation (CQRS). The ideas behind these principles help us create code that … Continue reading
Comments Off
