MT3 api changes and MT3 status

[Brian Weeres]

Are the MT3 public API changes mostly finished with the 3.02 alpha or are there significant changes to come? (RabbitMQ related changes are all we are really concerned about.) We have a a fairly large wrapper library around MT2 that we are looking at using in a production app in the fall. We are considering upgrading it to MT3 and using that to deploy in the fall instead but it will take some work to update it to MT3. Trying to decide if we should stick with MT2 or move to MT3 now with the hope MT3 itself is near production ready around September time frame and the public API won't change much from now until then.

Thanks.

[Chris Patterson]

Most of the API changes are complete with the latest (3.0.2) alpha. The middleware configuration bits (for things like retry, logging, filtering, transactions, etc.) are mostly done but that's new functionality anyway.

The pipeline bits are done, there should be nearly no churn on them at all at this point.

Also, Automatonymous is fully baked with 3.0.2 so the state machine should be completely integrated by now.

I expect MT3 to be GA by May/June.

On Wed, Mar 18, 2015 at 2:48 PM, Brian Weeres <bwe...@gmail.com> wrote:

Are the MT3 public API changes mostly finished with the 3.02 alpha or are there significant changes to come? (RabbitMQ related changes are all we are really concerned about.) We have a a fairly large wrapper library around MT2 that we are looking at using in a production app in the fall. We are considering upgrading it to MT3 and using that to deploy in the fall instead but it will take some work to update it to MT3. Trying to decide if we should stick with MT2 or move to MT3 now with the hope MT3 itself is near production ready around September time frame and the public API won't change much from now until then.

Thanks.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/2fb2db09-2e2a-403b-91ac-ef49a6ceac2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Weeres]

Terrific news. Thanks so much for the quick reply and the information.

[Marko Lahma]

Will the new RabbitMQ .NET client 3.5.0 with backward-incompatible AP changesI be included to test out possible usage problems?

https://groups.google.com/forum/#!topic/rabbitmq-users/sPSP3ulG6sg/discussion

Cheers,

-Marko

[Chris Patterson]

I always try to keep MT current with the latest RabbitMQ client, but it's never recommended to use a version newer than the one linked with the MT transport because they've broken APIs several times in the past.

The dependency and build stack has been significantly flattened with MT3, making it so there are fewer builds to update with an updated dependency. So it should be must easier to quickly update dependent packages and release, versus MT2 which required many other packages to be built after MT to keep everything updated.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-dis...@googlegroups.com.
To post to this group, send email to masstrans...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/da1b880e-cf12-4a09-b0ad-f2a676f217cd%40googlegroups.com.

[faze...@free.fr]

FYI I just experienced RabbitMQ.Client 3.5.0 (thank you nugget !) and it definitely does NOT work with the current MT3 version from nugget....