We use automated build systems not only because they make our lives easier by taking care of building our apps, but because they can run our automated tests and deploy what we build to the target platform. One of our options for building applications (especially Mule applications) is Gradle. The Gradle plugin for Mule apps provides a variety of ways to deploy Mule apps and that’s what we’ll be covering in this post!
Note:This is the fifth part of our Gradle plugin series; be sure to check out the previous posts!
First, I want to mention what our current version of Gradle can do today. Then, I’ll introduce features that are under development for release 2.0 of the plugin.
This character is QuickSilver and he’s the fastest of the X-Men. Mule 3.6 has no super powers, but when it comes to XPath, it’s the fastest ever! As you may remember, with the release of Mule 3.6.0 the XPath and XSLT was revamped. In this post, I’d like to not only continue elaborating on how great the improvement is, but also focus on a new aspect: Performance.
Last week marked a special moment in time for MuleSoft, as we position ourselves for the next phase of growth. The $128 million in funding we announced led by Salesforce Ventures brings our total financing raised to $259 million. ServiceNow and Cisco also made significant investments, along with public market investors Adage Capital Market, Brookside Capital and Sands Capital Ventures, as well as our existing venture investors. Each investment during MuleSoft’s evolution has allowed us to continue to solve the largest unsolved problem in IT. $593 billion of global IT spending is on integration, and we see it as a massive opportunity to make connectivity happen in a programmatic way that was not possible before.
Sometimes (more often than we think), less concurrency is actually more. Not too long ago, I found myself in a conversation in which we were discussing non-blocking architectures, tuning, and performance. We were discussing that tuning for those models often starts with “2 threads per core” (2TPC). The discussion made me curious about how Mule’s batch module would perform if tested by 2TPC. I knew beforehand that 2TPC wouldn’t be so impressive on batch, mainly because it doesn’t use a non-blocking threading model. However, I found myself thinking that the 16 thread default threading profile might be a little excessive (again, because sometimes less is more) and wanted to see what would happen if we tried it. You know, just out of curiosity.
CONNECT 2015 Technical Sessions
With over 30 sessions, customer case studies, hands on labs, product demonstrations, complimentary certification, and a packed solution expo of MuleSoft certified partners, CONNECT provides an great opportunity for current users of Anypoint Platform to uplevel their skills. And if you’re deciding if MuleSoft’s solutions are a good fit for you and your organization, we’ve designed a 3 day experience that will equip you with the resources to make the right decision.
“Any sufficiently advanced technology is indistinguishable from magic.”
– Arthur C. Clarke
Take a quick look around you. Maybe you’re on your way to work, or perhaps you’re waiting in line at the coffee shop. Now take a quick look at the people around you–don’t stare--but try and eyeball the number of people you see. Got it?
Ever wanted to get certified on our Anypoint Platform, but discovered that you didn’t have the training?
We’d like to introduce MuleSoft.U: self-study, public, FREE certification courses that will enable developers to learn core MuleSoft skills. At a significant cost per seat for a public class, instructor-led training is unattainable for most independent developers. With MuleSoft.U, independent developers can get up and running in no time. In our first course, Mulesoft.U Developer Essentials, students will learn:
- How to use Anypoint Studio to build integration applications to connect to SaaS and on-premise applications and data.
- How to use the Anypoint Platform for APIs to define APIs with RAML and then implementing them as web services using Anypoint Studio and APIkit.
- Deploying and running applications on CloudHub and/or Mule ESB Enterprise.
This is a great resource for independent developers, and any partner and customer developers who prefer the multi-week schedule are welcome to enroll as well. The first course begins on May 20, so register today!
Financial Institutions (FIs) find that deploying PaaS and IaaS solutions within a private cloud environment are an attractive alternative to technology silos created by disparate server hardware, operating systems, applications and application programming interfaces (APIs). Private cloud deployments enable firms to take a software-defined approach to scaling and provisioning hardware and computing resources.
FIs face a number of challenges as they build out their private cloud and PaaS environments:
Learn how @ CONNECT 2015
The pressure to deliver solutions in support of initiatives such as mobility and cloud services often trumps keeping mission-critical services stable and reliable. Without a way to simultaneously respond to the demands of the business and IT, industry leaders of today will quickly become the logos of the past.
Handling endpoints with disparate speed when the platform is in the cloud
A fairly common integration requirement is to accumulate data coming in real-time or near real-time, hold and consolidate the records, then send the transformed messages to another system on a fixed schedule (e.g. daily etc.) for business reasons, especially if the endpoints are legacy systems. For on-premises integration platforms, this use case is rather straightforward to implement. For cloud-based integration platforms though, which are generally geared toward real-time processing and lack access to local file storage, this requirement does seem to pose some technical challenges. Fortunately for CloudHub, with the built-in persistent queue feature and the Mule Requester Module, the implementation is as easy as doing it with legacy on-premises platforms.
Fast and Slow can play nice together