Providing SDKs is the shortest path for developers to get started with your API.
We are happy to announce the September ’15 release of the Salesforce Analytics Cloud Connector v2.0.0. In this blog post, I will be covering some of the important features of the connector as well as walking you through the technicalities of ingesting data into Salesforce Wave Analytics Cloud by leveraging features within Anypoint Platform.
We’re happy to announce that MUnit 1.0 (GA) is now available. MUnit is the functional test framework for Mule. This is builds on feedback from our previous release candidate and it contains many quality and usability improvements.
I am excited to announce the latest update to the Anypoint Platform. This update is focused on a number of capabilities that enable even more efficient management of a well-oiled API-led connectivity solution.
Rich API product offering through layered service level agreements
Anypoint Platform Service Level Agreements (SLAs) allows API owners to define the menu of offerings available to API consumers.
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.
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.
In this post we’re going to continue the discussion started our last post “A sneak peek into Mule 3.7’s deepest internals” about how Mule’s registry, lifecycle and dependency injection mechanism are being overhauled in Mule 3.7. In this case, we’re going to take a deep dive into how we managed to unify the registries while keeping backwards compatibility and all the implications of such maneuvers.
Mule 3.7 is approaching, and among other things we decided to put a lot of focus on the experience of the guy coding custom components (Devkit based or not). For this, the first 3.7 milestone is incorporating big changes in terms of the how Mule Lifecycle and Dependency Injection are applied.
As I said, these changes are BIG, so for clarity reasons we’ll cover them in a series of post starting with this one.
SAN FRANCISCO – April 1, 2015 – MuleSoft, the company that makes it easy to connect applications, data and devices for corporations, today announced a new component of its flagship Anypoint Platform™, CloudShack, a highly available, resilient, and scalable solution for connecting people, thus making the world a better place.
Today, even lonesome hearts demand seamless and automated interactions with their mating service providers,
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.