+972 52-548-6969
Building Distributed Apps with NHibernate and Rhino Service Bus
time to read 1 min | 19 words
The first part of a two parts article about NHibernate and Rhino Service bus in now on MSDN.
FUTURE POSTS
No future posts left, oh my!
RECENT SERIES
-
Recording
(16):
29 May 2025 - RavenDB's Upcoming Optimizations Deep Dive -
Webinar
(6):
27 May 2025 - RavenDB's Upcoming Optimizations Deep Dive -
RavenDB News
(2):
02 May 2025 - May 2025 -
Production Postmortem
(52):
07 Apr 2025 - The race condition in the interlock -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration
RECENT COMMENTS
-
By Scooletz on Recording: RavenDB's Upcoming Optimizations Deep Dive
-
By Scooletz on Comparing DiskANN in SQL Server & HNSW in RavenDB
-
By Oren Eini on Comparing DiskANN in SQL Server & HNSW in RavenDB
-
By Joel on Comparing DiskANN in SQL Server & HNSW in RavenDB
-
By Oren Eini on Scaling HNSW in RavenDB: Optimizing for inadequate hardware
Syndication
| Main feed | |
| Comments feed |
Comments
great article. i especially like the caching technique, simply "re-send" the response. I'm looking forward to part 2.
Interesting! With some modifications and an automapper with the domain layer it should be fairly straightforward to write the client in Javascript. The persistent cache can be handled with WebKit SQL storage.
Great! I've been looking for some solid guidance on this exact type of architecture with smart clients.
Will the final source project be posted somewhere?
Matthijs,
the final source code is already posted
http://github.com/ayende/alexandria
Nice article, but... Where are the tests? I don't understand how it can be considered acceptable to publish a code sample like this without unit tests. IMO, tests are the most important part of sample code.
@g
Yeah I was considering how to apply this architecure to a Javascript application as well. You statement about using WebKit SQL implies you would keep the queue on the client. I was thinking the queue would still be on the server, the javascript code would just be a queue client.
You lose the transaction support and durability, but it allows for the message based architecture. I can see though how having a queue on the client would be helpful as well to coordinate UI blocks that communicate.
Does anyone know of tools to support such an architecture in a javascript scenario?
fschwiet, do you have an email address / twitter?
Great article!
Is this something that could be used in a silverlight application as wel. If so, you probably need to rewrite the PersistentCache to store the files in isolated storage, or is there more involved?
I am looking forward to your next installment.
Great article as always. Can't wait for part two...
I am however interested in how you handle authentication... is authentication handled at the message level or at some higher, more general level?
Wow, this should be a 3-in-1 article covering 3 different MSDN magazine columns. It covers the basics of a backend infrastructure implemented the right way using the right tools (NHibernate, Rhino.ServiceBus w. protobuf-net, etc) but also covers a very acceptable (maybe the best?) way to implement a UI client in WPF/SL using the Caliburn framework. Add that lot of best practises can be found in the article (IoC containers, ISession management, etc). I wish if you could write even more (about new details on Linq and re-motion's Linq provider in 3.x release on NHibernate trunk). Microsoft should take such articles into very detail.. You are upfront & forward-thinking as always. **10/10
@g, I'm the only fschwiet on the internet :P its @gmail
Comment preview