Myself and Dave recently spoke a different events about Real-time APIs and use cases. Folks ahve been asking for the slides and video, so here they are!
Want to leverage existing PHP experience of your development team to accelerate implementation times? In this blog post I’m going to show you how to take advantage of new Mule PHP scripting module, that enables your applications to use good’old PHP as the programming language in Mule scripting components.
The way we build applications is changing. As the development model shifts from writing lots of code to composing APIs together, a new generation of middle tier application architecture is being born. What does this mean for you? Ross Mason, MuleSoft’s founder and CTO, will provide his perspective on the future of this growing movement.
When? Thursday, July 26, 2012
Session 1: 2 PM BDT/9AM EDT
Session 2: 1 PM EDT/10 AM PDT
Webhooks are a very simple way to tie application together on the Internet. Suppose application A wants to be informed when data changes in application B: the traditional approach consists in having application A poll B for changes. The webhooks approach turns the problem around: B gets configured so it hooks to A via HTTP calls. Whenever data changes in B (or for that matter, whenever anything of interest happens in B), B will call A to let it know. No more polling, just simple HTTP server-to-server callbacks. Webhooks is so simple that there is no spec for it: the HTTP spec is all what is needed really.
SOAP, JMS, Restful, SFTP… Sometimes your integration just comes to the point in which you need to be able to download a file from your browser. From Ubuntu One all the way to Dropbox and Google Drive, the number of file storage services on the cloud just keeps climbing. One that is particularly gaining a lot of momentum and putting a lot of effort on cloud to cloud integration is Box, so we decided to build a Cloud Connector for it and we’ll show it to you in this post.
We’re big fans of real-time here at MuleSoft, always asking “why wait for anything?”. This week we have Ross our CTO and Dave our Salesforce Architect and Integration Strategy Lead talking at local events, the CloudMafia meet up and the Salesforce.com Integration and Analytics meet up. We’d love to see you at either of these events this Wednesday evening.
A new Mule release has to come with another internal hackathon. Our development teams focused on using the new features we added in Mule 3.3 and we came to the conclusion “A hackathon is like a box of chocolate, you never know what your are gonna get”. In our case, we got some really cool applications, so cool that some of those can become real products in the future.
We’ve just released Mule ESB 3.3 into the wild. This is a big release for us and and marks a huge step forward in the ease of use of Mule and what you should expect from an integration platfrom. Not only has Mule Studio been significantly improved and the brand new DataMapper added, but Mule itself has also undergone a number of significant improvements.
With the flexibility and power of Mule Flows introduced in Mule ESB 3.0 along with Mule Studio including DataMapper and the improvements to Mule itself in this new release, Mule ESB 3.3 really is “Mule 3 Reloaded”. Read the recent whole product release announcement for an overview of everything that is being released with Mule ESB 3.3, then continue reading this post to get the low down on some of the most important new feature in Mule.
Would you like chicken or pasta? Chocolate or vanilla? Coffee or tea? White wine or red? Component or transformer? If you have a piece of custom code, should you implement it as a custom transformer or as a custom component?
Technically, you can do either. But under what circumstances is it better to use a transformer versus a component?