Saturday, June 14, 2008 6:41 AM
Well today Chris and I decided that MT had reached another milestone of functionality. After having several people review our efforts we have tried to take a lot of the feedback into the system and really polish it up.
This release shows a lot of improvement towards embracing the IoC container quite a bit more. I think that it still has some rough edges around it, but it is an excellent start that should help us to now see where we can further embrace it.
We cleaned up the subscriptions quite a bit, and squashed some bugs that were causing some chatty exchanges. We are also working on a single click install of the subscription manager.
As has been noted previously we are also working on a dashboard that will let you see 'into' the system a bit more, and will be the focus of my work along with automating some more intensive tests. Going to explore just what TeamCity can really do.
Some of the new tests that we are running, and I am looking forward to automating include a load test, load request/reply test, and a load batch test. These three tests have been awesome for ironing out bugs at higher stress levels. I am looking forward to running these on a more automated basis as well as finding new types of tests to create.
The 'host' project has been rewritten to fit a style more comfortable to us as a developer. You basically write a then console program in your project and add a few lines of code to it and off it goes. Much easier to debug into than the old style.
Another new feature and a flavor that Chris will be working on going forward is a Distributed Subscription Cache using memcached that should be a very interesting part of the project to see how it grows and influences the rest of the project.
Batching was rewritten and is now quite a bit smoother, I upgraded the systems at work to include this new API and it reads quite a bit better now.
Not a lot of progress on the build support, which should make working with msmq in your deploy scripts a bit easier to work with.
XML serialization was dropped as it just didn't seem to work as well as we would like. If anyone has a better XML serializer I am all ears. :) The JSON serializer is still in there, but at this point is likely to see little use. The binary serializer is quite nice.
And lastly the project structure has been cleaned up quite a bit, and I look forward to cleaning up and automating even more of the Mass Transit experience. So, pull it down and let us know what you think!
-d