So my general advize would be to start small. Think about the central concepts of CQRS and what you need from. If you are looking at the java API and do a solution in smalltalk you just need some confidence that you didn't forget a ton of stuff only because it is much smaller and easier :)

I agree with you and this is the reason why I was looking for an Smalltalk framework to build CQRS webapps.
�

I really like the topic. If you have other inquiries or insights regarding this topic I'm always interested. If you can tell what you need I can think about what of the stuff I did might be useful to others.

Unfortunately, what I really need is to implement CQRS, or some of its concepts as you said, in a Java-based webapp, but not in Smalltalk. We are suffering severe performance issues and I'm evaluating if the "read model" of CQRS could be a good solution for our problem. Then I thought: why not to look up inspiration in an Smalltalk framework, if it exists :-)

Rafael Luque