Can someone explain the significance of Hazelcast Custom Serialization techniques :-
StreamSerializer
ByteArraySerializer
I have gone through Hazelcast official documentation but it's not very clear from that.
There's a nice blog writeup at https://hazelcast.com/blog/comparing-serialization-methods
Related
Could anyone guide me how to do event sourcing in mule as mentioned in the blog below
https://dzone.com/articles/introduction-to-event-sourcing
The article describes a conceptual practice. You can implement it as you like. It is not something that Mule provides. It is the same as you would design your database as an example. Not a Mule concept.
I want to use MassTransit bus with RabbitMQ. But I am not able to find a simple example. I am looking for example which will get me started.
What I have tried.
googled: But most the examples are using MSMQ or they using too many configuration options.
GitHub: I looked a the GitHub for MassTransit (https://github.com/MassTransit/MassTransit/tree/master/src/Samples) But the example here is heavily loaded. It's very hard to understand for beginners.
Reading docs: I have started reading docs but it will take some time before I finish it. I am hoping if someone shares a link to simple example which will get me started.
Please provide your suggestion.
Here's a simple, good pub-sub example using MassTransit and RabbitMQ both.
http://looselycoupledlabs.com/2014/06/masstransit-publish-subscribe-example/
In case the article link does not work, here's the link to the source code:
https://github.com/dprothero/MtPubSubExample
Thanks to the author of course!
MassTransit implements a lot of concepts and provides great many features with a very small surface API. There's no simple way to describe everything it does, because the problems it helps to solve are not simple, but an example can be made small.
Have a look at this sample I have for testing throughput:
https://github.com/et1975/Throughput-Test
The only "extra" that one might find unnecessary is Dependency Injection integration. You'd want one in most cases, but it does hide how certain bits interact.
Look at https://groups.google.com/forum/?fromgroups#!forum/masstransit-discuss for more help.
Cheers,
ET.
I'm working on API versioning in WCF these days. I've read many articles regarding best practices of doing this. What I've to understand the most important thing is to identify either changes in API are Breaking or Non Breaking in new version. A very nice article/discussion on Changes impact on stackoverflow WCF API Deployment Versioning
To implement custom Serialization requirement I've chosen ixmlserializable technique. Now my question is Either Breaking and Non Breaking concept will remain same in this case? If no, please help me to find out the way to implement API versioning in this context.
My understanding is that new changes will always break when working ixmlserializable because ReadXml method implement the manual way to construct the object.
Please do let me know either my understanding is correct and how to proceed in this scenario. Any help in this regard will be highly appreciable.
/Rizwan
Is there a practical example or demo that walks you through creating a service and then breaking it because of improper versioning. Most examples I see on the web just tell you what it is, but don't walk you through a demo.
Dhananjay Kumar shows some code samples for data contract versioning on these blog posts:
http://debugmode.net/2010/10/03/versioning-in-wcf-data-contract-part-1-adding-new-members/
http://debugmode.net/2010/10/03/versioning-in-wcf-data-contract-part-2-missing-members/
There is also some guidance on MSDN with a bit of code about all around versioning in WCF:
http://msdn.microsoft.com/library/ff384251.aspx
Can anyone give/point me to 'official references' about component inheritance support in Nhibernate 3.10 ?
Already google it, but never find any reference about that.
Thanks
NHibernate (and Hibernate for that matter) does not support component inheritance out of the box. You have two relatively unpleasant options:
Map hierarchy as entities.
Write custom hydration/dehydration code using IUserType. This workaround is described in this article
(java, but should work for C#).
In the mean time you can vote for this feature to be implemented in Hibernate and maybe some day ported to NHibernate. NHibernate version of this feature request.
Here there's some doc but I'm not sure if this can help you:
https://ayende.com/blog/3941/nhibernate-mapping-inheritance
Updated
I think it's not possible! look here:
https://stackoverflow.com/q/3739806/735864