You are not logged in.
Pages: 1
How does it compare with the reference of SOA implementation (at least in the Windows world) - aka WCF?
"Comparaison n'est pas raison", as we use to say in France.
But we will also speak about Event Sourcing, and why it is now on our official road map.
Comparing our implementation with WCF is the opportunity to make our framework always better.
We may be tempted to say that mORMot SOA architecture is almost complete, even for a young and Open Source project. Of course, WCF features (and suffers) its SOAP-based architecture. The only missing feature is transactional process, which must be handled on server side, within the service implementation (e.g. with explicit commit or rollback).
An Event Sourcing design has been added to the mORMot road map, in order to handle transactions on the SOA side, relying on ORM for its data persistence, but not depending on database transactional abilities. In fact, transactions should better be implemented at SOA level, as we do want transactions to be database agnostic (SQLite3 has a limited per-connection transactional scheme, and we do not want to rely on the DB layer for this feature). Event Sourcing sounds to be a nice pattern to implement a strong and efficient transactional process in our framework - see http://bliki.abdullin.com/event-sourcing/why
Comments on blog article http://blog.synopse.info/post/2012/04/2 … t-Sourcing
Offline
Some remarks about WCF and mORMot are also available in this blog article.
http://blog.synopse.info/post/2012/10/1 … e-not-evil
Offline
Pages: 1