In the second blog roundup of this year, we are highlighting the top 7 blogs over the last three months––providing you, our readers, with insight into the top stories you may have missed!
1. Why the monolith isn’t dead
Many praise the microservices design approach, but does this mean that a monolithic architecture is outdated and inefficient? Think again. Read this blog to learn more about monolithic architectures and see what use cases render a monolithic design ideal.
This year, we are starting a new roundup series, highlighting the top 2018 blogs of each quarter in order to provide our readers with insight into the most popular stories!
Today, I’m pleased to share that MuleSoft has entered into an agreement to be acquired by Salesforce. This is a major milestone for the company and potentially one of the most game-changing technology acquisitions in history. I believe it will accelerate us on our mission to enable organizations across the world to change the clockspeed of business with application networks. I could not be more excited about this next chapter for MuleSoft.
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.
Today is a big day to celebrate the great work of the Muleys who have made it happen. You should be proud and enjoy this moment—it’s an excitement that few people will experience.
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.
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.
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.
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,
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?
