Today is a big day for us. We’re having our IPO today. Going public means that we have grown MuleSoft to a scale and level of performance that few companies achieve. It means that we will be playing on an even bigger stage, and we’re ready.
It had just turned 2 a.m. on April 18th, 2003. I was getting ready to release my first open source project, and I was about to pull the trigger on a name. I settled on MULE as I was trying to solve the hard, unrelenting work of connecting applications and data—MULE was going to take the “donkey work” out of integration. What I didn’t know was that I was choosing the stock ticker symbol for a company that would go on to solve much bigger problems for companies globally. It’s pretty cool to reflect on that now, and it has been an amazing experience getting here.
We’ve called downtown San Francisco home to our headquarters for several years, and we love the energy around tech in the Bay Area. MuleSoft is growing dramatically, and in order to keep the pace, we’re looking to quickly expand our engineering organization and tap into the incredible talent in the South Bay. We’re thrilled to be opening a new development center in downtown Mountain View.
We get requests from time to time about guest blogging at MuleSoft. Here is an official post about it if you are interested in submitting a guest post.
Of course! You have valuable insights and content and we want to help you share that information with others.
Some benefits include:
I’m excited to announce the release of DevKit v.3.8.0 today. This version includes a lot of new features, enhancements, and bug fixes. Here are seven key features you should note from this release.
With DevKit 3.8.0, partners can manage their connector’s license natively within DevKit. This feature will allow partners to require license entitlement before users can deploy their connector in runtime. Now, similar to how our Premium Connectors work, users will see a form requiring the entitlement before the connector can be deployed.
A while ago MuleSoft started considering sponsoring an organization supporting women in technology. There were many to choose from but we wanted to work closely with an organization that would allow us to be very involved. We also wanted to be inclusive since technology is not just about coding. Luckily, we learned that a new branch of Girls in Tech was getting started in Argentina and were looking for sponsors to organize a hackathon, so we jumped in.
Since I joined the company this summer, one of my main tasks has been to improve the connector certification program. To do this, I’ve engaged with partners, developers and MuleSoft employees; to further familiarize myself with our technology and processes, I decided to build my own Google Translate Connector. I’ve learned a lot by going through the process and wanted to share some resources I found most useful as I was building my connector.
Salesforce unveiled Lightning Connect with the promise of allowing you to expose the data stored in your legacy data source into Salesforce in real time, without needing any migration. The only requirement is exposing such datasource through an OData endpoint.
So you have your datasource on one end, and Salesforce supporting OData on the other. The question now is: how do you connect the dots?
Enter Anypoint Data Gateway
MuleSoft Champions are the life-blood of the MuleSoft community – experts who work tirelessly to give back to the community – whether it be through core contributions, creating connectors, writing blog posts, or through answering questions on our forums and StackOverflow.
For the work that our Champions do, we cannot recognize them enough. First we started with the creation of the MuleSoft Champions Program of which only 7 people have reached the highest honor, becoming a MuleSoft Champion.
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.
Sign up for our newsletter
Sign up for our newsletter
