Announced this morning on the new Pivotal blog, where RabbitMQ now resides, this version includes enhancements to garbage collection, consumption, requeuing, memory use, and dead lettering.
For those on Mac OS X, there is a newly packaged, standalone release of RabbitMQ that doesn’t require a separate Erlang install.
Some key, new capabilities include eager synchronisation of mirror queue slaves, automatic cluster partition healing, and improved statistics (including charts) in the management plugin. There are also many enhancements and bug fixes to the server, Java client, Erlang client, and a number of other plugins, including federation, old-federation, shovel, Web-STOMP, STOMP, and MQTT plugins, as well as the consistent hash exchange.
Next year is going to be even bigger with the Pivotal Initiative where several of the products covered on this blog will be following the new venture. This is still in the planning stages, so we will be expecting to share with you the plans for our products alongside the formal communications from each of the companies involved. (Sorry — no extra information is available right now)
Application developers and data management teams continue to look for ways to modernize legacy apps, manage costs more effectively, build new apps on robust application platforms, and solve big data problems. These are some of the key reasons why vFabric is on the CIO (or CTO) agenda. With several new product releases in the vFabric Suite, VMware continues to provide a best-in-class application platform and help customers solve their top application development and data management problems.
Recently, we had the opportunity to speak with architect Brett Cameron about vFabric RabbitMQ. A popular speaker, Brett is well known for his effort to port Erlang and RabbitMQ over to the “legacy” OpenVMS operating system platform (now owned by HP). With over 19 years in the software industry, Brett specializes in systems integration and large, distributed systems. Of course, he has spent a lot of time with OpenVMS – an OS with one of the more interesting histories in the software industry.
When we started chatting with Brett, he had recently discussed the concept of the Polyglot Rabbit with Alexis Richardson and written a great article titled, “The Polyglot Rabbit: Examples of Multi-Protocol Queues in RabbitMQ.” According to Brett, the main goal of this article is about the fact that you can publish messages into this environment via one protocol and consume via one or more other protocols (simultaneously if you want). “It’s a brilliant and a very powerful capability.” Brett felt that this capability was possibly not being promoted enough, and hopefully the article will go some way towards fixing this.
At VMworld-2012 San Francisco, the session APP-CAP1426 – The Benefits of Virtualization for Middleware was greatly attended, and we want to thank all of the attendees that helped us score 4.5 out of 5 in our survey results. Because of this, the session is going to be presented at VMworld-2012 Barcelona, and we are posting related information here in this article. Before reading this article, you might want to take a look at the related blog post we released before VMworld-2012 San Francisco.
NOTE: Just like in VMworld-2012 San Francisco, at Barcelona we will raffle copies of my book the Enterprise Java Applications Architecture on VMware
This year at the session, we went deep into tuning large-scale middleware and the discussion around JVM tuning was well received. Hence as a follow-up, I wanted to share some of my more recent research, which will be discussed at VMworld-2012 Barcelona. This focuses on tuning in-memory data management systems such as vFabric SQLFire.
The article below covers:
An Overview of GC Tuning
Parallel GC in Young Generation and CMS in Old Generation
GC Tuning Recipe
Step A – Young Generation Tuning
Step B – Old Generation Tuning
Step C – Survivor Spaces Tuning
JVM and GC Best Practices for vFabric SQLFire Members
The Application Management Marketplace brings together an ecosystem of developers, independent software vendors, system integrator partners, and end consumers to collaborate and share solutions so IT teams can get instant access to ready-to-use cloud application management solutions. These solutions are meant to accelerate deployment and simplify management of real-world enterprise applications on private, public, and hybrid clouds, using VMware’s Application Management products – namely VMware vFabric Application Director for provisioning cloud applications and VMware vFabric Application Performance Manager for monitoring and scaling applications.
Ten years ago, the Spring Framework delivered radical simplicity to the complex world of enterprise Java. Today, VMware is delivering integrated middleware components in vFabric and driving the exact same simplification agenda.
Our customers have been successfully virtualizing Java workloads on vSphere for years, and VMware has built up a wealth of experience which we’ve been sharing with exponentially increasing numbers of attendees every year at VMworld. This year is no exception! (For example, check out “The Benefits of Virtualization for Middleware” on Thursday, Aug 30, 10:30 AM – 11:30 AM.) As we’ve grown in supporting Java on vSphere, we’ve also continued to embrace more Java and open source products within our vFabric product portfolio. Continue reading →
Register for Session (APP-CAP1426 – The Benefits of Virtualization for Middleware): Click Here
Follow all vFabric updates at VMworld on Twitter: Click Here
Middleware virtualization has three key trends that we are observing with our customer base:
2) Elasticity and Flexibility, and
In this blog, we examine each one of these trends briefly and invite you to come along for technical deep dive at this year’s VMworld session APP-CAP1426 – The Benefits of Virtualization for Middleware to be presented in both San Francisco and Barcelona.
Many of our customers find that their middleware deployments have proliferated and are becoming an administrative challenge associated with higher costs. We see a trend across customers who look to virtualization as a way of reducing the number of server instances. At the same time, customers are taking the consolidation opportunity to rationalize the number of middleware components needed to service a particular load. Middleware components most commonly run within a Java Virtual Machine (JVM) with an observed scale of 100 to 1000s of JVM instances and provide many opportunities for JVM instance consolidation. Hence, middleware virtualization provides an opportunity to consolidate twice – once to consolidate server instances, and, secondly, to consolidate JVM instances. This trend is far-reaching, because every IT shop on the planet is considering the cost savings of consolidation.
Aadhaar was conceived as a way to provide a unique, online, portable identity so that every single resident of India can access and benefit from government and private services. The Aadhaar project has received coverage from all possible media – television, press, articles, debates, and the Internet. It is seen as audacious use of technology, albeit for a social cause. UIDAI, the authority responsible for issuing Aadhaar numbers, has published white-papers, data, and newsletters on progress of the initiative.A common question to the UIDAI technology team in conferences, events and over coffee is – what technologies power this important nation-wide initiative? In this blog post, we wanted to give a sense of several significant technologies and approaches.
While the deployment footprint of the systems has grown from half-a-dozen machines to a few thousand CPU cores processing millions of Aadhaar related transactions, the fundamental principles have remained the same: