Much of the code in MassTransit was written prior to the introduction of the Task Parallel Library (or TPL), and even the.net 4.0 support was before async and await were added to the language. In order to embrace the world of asynchronous programming, as well as leveraging the power of advanced messaging platforms like RabbitMQ, a foundational rewrite was required. In early 2014, after a few years of research and design, work was started on an entirely new MassTransit. After four years of continued success, Chris and Dru continued to push forward on their Journey, and were joined by Travis Smith The near future should bring much for the MassTransit community as RabbitMQ became the broker of choice, lessening the focus on MSMQ. The first commit was pushed to GoogleCode on, and shortly there after both Dru and Chris went to production with MassTransit and both of their companies have had success in getting value out of their efforts. Initially the goals were as much about learning distributed message based systems, as well as building something both of their companies could use. For these reasons, they decided to embark on the quixotic trek of building their own service bus (seriously, how hard could it be? LOL). It also become obvious that NServiceBus wasn t quite ready for external contributors to come onboard. After reviewing NServiceBus, it was determined that the only real dependency injection container supported was Spring.NET. After searching the.net ecosystem for a tool that would help them achieve their goals, the only real option was the venerable NServiceBus. Combined with an awareness of the latest advances in tooling, libraries, and coding practices they decided that a better option must exist. Surrounded by the best and brightest in.net, the energy was there to build better tooling that supported testable processes. It was at this conference that Chris and Dru not only realized that they had a lot of the same problems to solve, but also how much the standard tooling provided by Microsoft just didn t fit their needs. :) In 2007, Chris Patterson and Dru Sellers met, for what Dru thinks is the first time, at the first ALT.NET conference in Austin, TX. 1.1 A bit of the back story? We are often asked why MassTransit was created, well here s the story. Message-based communication is a reliable and scalable way to implement a service oriented architecture. MassTransit provides an extensive set of features on top existing message transports, resulting in a developer friendly way to asynchronously connect services using message-based conversation patterns. Contents 1ħ CHAPTER 1 What is MassTransit? MassTransit is a free, open source, lightweight message bus for creating distributed applications using the.net framework. 5 MassTransit is a free, open source, lightweight message bus for creating distributed applications using the.net framework.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |