Redesign of the M.A.R-T>Y. system after the MVP with a focus on tightening communication.
Primarily, a focus on making communication truly asynchronous. Message handling has been completely revamped to allow clients to handle responses in any order, without waiting for the 'chronologically ordered' response first.
Secondly, support for UNIX sockets was introduced so that depending on various factors certain clients can take advantage of lower latency than TCP. A standard send, acknowledge, receive setup benchmarked a single client responding to 10 different senders concurrently at 45,536 84-byte (typical MMP packet size) transactions per second through the UNIX socket on the Alpha quality message broker, m-admiral.
Thirdly, there is a greater focus on 'endpoints' similar to what you'd expect in HTTP-based applications, to better define communication capabilities.
All M.A.R-T>Y. v2.0 clients take advantage of the improvements made in MMP v2.0; v1.0 is considered deprecated as the MVP stage is no longer relevant.