Moreover, Viper manages concurrency and processing loads as you would expect from any self-respecting TP monitor. Viper runs on top of Windows NT and Windows 95, and applications will be written to run on Viper using any number of COM-enabled development environments. You're already seeing the influence of Viper today. DTC lets developers distribute autonomous transactions across multiple SQL Servers, and it provides automatic recovery services as well. Microsoft's entry into the MOM market is designed to further Microsoft's strategy to provide enterprise-ready middleware products such as Viper.
Falcon is MOM, so it's naturally able to handle interprocess communications asynchronously.
Falcon does not require that the target processor actually be working when the message is sent, because MOM uses a queuing mechanism that stores messages for delivery when the processor is again active. Of course, Falcon and Viper are joined at the hip with ActiveX. Falcon provides an ActiveX server side and a client-side set of components. . Thus developers can use any tools that work with ActiveX components to deliver Falcon-based applications. Browser-based applications will be able to dispatch messages. Microsoft is already looking to provide an interface to IBM's MQSeries MOM and CICS TP monitor.