Hi All. We are kicking off our Mule meetups in Melbourne. Come and join us to hear the news, watch exciting demos, and rub shoulders with your fellow Mule users. We are also looking for presenters and would like to hear from your experiences with API-led connectivity, microservices, DevOps - anything with Mule in and around it. We are also open for partnerships and welcome sponsors to help us make this event a success.

Mule 4 adds vastly more power, higher speeds and greater simplicity into the famously smallfootprint of Mule – the industry’s leading all‐purpose engine for building application networks.This beta release delivers a simplified language for connectivity, transparent data access andstreaming, automatic performance tuning and smoother upgrades.

Out of the box, the Mule runtime offers a traditional application server deployment model, with many applications being (re)deployed into long-running Java server processes. The footprint of the runtime itself often isn’t a concern, because this resource cost is amortised across all the applications running on it. How does this model translate to a containerised microservice world? How can we reap the immutability, isolation, scalability and security benefits of containerisation while approaching the efficiency and convenience of a monolithic app server? We look at several approaches to minimising the resource footprint of the Mule runtime to optimise it for single app containerised deployments.