ProductsDesktop Server For Scientific Computing For IBM POWER For IBM System z For SAP Business Applications Red Hat Network Satellite ManagementExtended Update Support High Availability High Performance Network Load Balancer Resilient Storage Scalable File System Smart Management Extended Lifecycle SupportDeveloper Studio Portfolio Edition Web Framework Kit Application Platform Web Server Data Grid Portal Platform Red Hat JBoss A-MQ Red Hat JBoss Fuse SOA Platform Business Rules Management System (BRMS) Data Services Platform Messaging JBoss Operations Network JBoss Community or JBoss enterprise
SolutionsApplication development Business process management Enterprise application integration Interoperability Operational efficiency Security VirtualizationSolaris to Red Hat Enterprise Linux Migration overview Migrate from your UNIX platform How to migrate to Red Hat Enterprise Linux Upgrade to the latest Red Hat Enterprise Linux release JBoss Enterprise Middleware Benefits of migrating to Red Hat Enterprise Linux Migration services Start a conversation with Red Hat
TrainingPopular and new courses Red Hat JBoss Administration curriculum Core System Administration curriculum JBoss Middleware Development curriculum Advanced System Administration curriculum Linux Development curriculum Cloud Computing, Virtualization, and Storage curriculum
ConsultingBusiness Process Management Cloud and Virtualization Custom Software Development Enterprise Data and Storage Systems Management Migrations
December 6, 2007
by Red Hat Enterprise MRG Team
Looking at the stories that have been written about Red Hat Enterprise MRG since our announcement on Tuesday, we think that it is worth pointing out a few additional distinctions about the offering. Some writeups have focused on MRG as a replacement for other vendor’s messaging products, such as Tibco and IBM WebSphereMQ. At Red Hat, we believe in freedom and choice and intend to continue to tune and support other messaging products and our partners’ messaging platforms–even if MRG overlaps in some use cases. To this end, MRG realtime has been developed with customers running many other vendors’ products (including all of the key messaging providers). The better we can make all of a customers’ products perform, the more our customers win–and we win too.
Some of the biggest workloads that we have tuned, and with which we have developed realtime, have been other messaging systems. If these other systems meet a customer’s needs, we believe that MRG can provide differentiation for the systems’ deployments, which are latency/determinism-sensitive or require broader interoperability.
For MRG, we are working to provide the maximum throughput, CPU and latency possible for any given hardware. When deploying MRG, what really excites us is the possibility to have an open ecosystem and provide value to our customers. MRG was created not with the goal of displacing any point product, but to provide value through the integration of a compute platform that adds the next layer to Linux Automation.