Hi Patrik, I was playing little bit with new mongo-shipping sample. I like the concept a lot but we need to clean rough edges. Separation of layers is tooo unclear. When programming something like this we have to separate layers. Maybe via separate project or something else (any idea?). When I'm programing business tier Services I should work only with Repositories and Services of same module. When I'm programming orchestration tier or integration tier (any other good name for this tier above services?) I can use only commands and business tier services (no repositories) across different modules. Am I right? For now it's very unclear and confusing and not error prone for programmer. You have to be very careful what are you including in your services. I like your event handling but here are many duplicity even already in model. Can we simplify this somehow for example generating DomainEvent for each CommandEvent? What is proposed transaction model? Where transactions begins and ends (on service tier, on orchestration tier, ...)? Will we have some explicit compensation methods? Please also consider some explicit dead letter queue for commands which aren't processed (exception fired when processing event/command in default EventSubscriber handler). Can we make similar sample without using mongoDB? This noSQL stuff is still strange and confusing for me and maybe also for others.
This concept is very import. I would like to make it right. Should you write somewhere generic concept before we start implementation. I know you are clever guy and you have something in mind but I would like to influence you (if possible ;-) that it should be more universal. I'm excited about it and maybe we aren't going to make it perfect for 1.9 release but for 2.0 I would like to have it usable and integrated with at least one major SOA platform and tested with different configurations. We are stepping to integration tier with sculptor and it's very important for enterprise development. We already have some need for this in our projects and we can do it now in sculptor - great. Regards Pavel ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
