Before APIs, if you wanted to know if there were any updates on a specific event you had to query the API periodically and check if updates indeed occurred. Most likely, many of these queries would probably return no results as no new event happened but still resources were consumed in the process including the API call and parsing the response. Now, what if you want to get notified not only of 1 event but 10, 20 or 100? Wasting resources like this is not acceptable both for a the application consuming the API and for the API provider and that is why streaming emerged.

Kira on Wednesday, November 23, 2011

Get the most out of Mule HA clusters

3

3.2 introduced out-of-the-box and . Want learn how to get the most out of these new capabilities?

Mike Schilling, MuleSoft’s Lead Architect, shares his in depth knowledge about Mule 3.2′s HA clusters.  If you are looking learn the leading tips and tricks for designing and managing clusters, as well as the applications running on the cluster, you should plan to attend MuleSoft’s upcoming webinar titled: High Availability for Integration Applications.

At QCon SF last week I gave my talk on DevOps to NoOps: 10 cloud services you should be using. I talked about what I call the API explosion and how that impacts the way we build applications before introducing my list. I focused on infrastructure APIs because I believe these have the biggest impact on application development and thus the developers that build applications. For me, the interesting part of the talk was the questions, it highlighted the general reaction to the benefits of infrastructure – if you are not using them you probably don’t get the value.

Of all the professional networks available LinkedIn has clearly taken the lead with more than 120 million members. Do you use LinkedIn? Most likely you do! That’s why we thought it’s important to have a Connector to interact with LinkedIn and take advantage of its social power.

When developing a Application the normal way to define an statement is by declaring it directly in the connector, as shown in the following snippet.

However is possible that you’ll face a situation in which you have to use large and complex queries. For that scenario the previous approach is not adequate since you’ll end up with a configuration difficult to read. So the best thing to do is to externalize these queries in one or more files.

around public cloud offerings has always been a major point of concern (and controversy) for users. How do cloud providers protect customer data? How is log data protected? How is the surrounding infrastructure secured? We previous talked about how iON stays up and running even through EC2 outages. Today, we will talk about iON security to show how we protect customer information and the infrastructure used in building iON.

 

We are pleased to announce the Beta Milestone 5 release of Mule Studio, the graphical design tool for ESB. At its core, it is based on the Development Platform which many developers are already familiar with. But we have added significant functionality to it to achieve a very tight integration to Mule ESB. This makes a powerful visual and coding environment for developing Mule ESB applications.

The last time we talked I show you how you can easily build RESTful APIs on top of iON.  I just covered just a very narrow scenario, the sky is the limit when talking about the kind of integrations that you can build using iON. So this week I’m going to walk you through another interesting use case, IVRs. If you don’t know what they are, don’t worry I will cover the basics in this article. Stick around it’s going to be wild.

In this blog post I will show how to extend in a simple way using the recently released Mule DevKit. The goal of the Mule DevKit is to accelerate the development of Mule extensions by abstracting you from Mule specific stuff so that you just focus on what your are trying to build.

My idea here is to create a simple Cloud Connector to interact with Google Maps API but the concepts covered here can be used in other scenarios as well. Since the Mule DevKit is intended for developers, expect many code snippets so that you can go through this example on your own and play around with the code. You can get the full source code here.

Ross Mason on Tuesday, November 8, 2011

AMQP and the future of web messaging

6

Last month the AMQP working group, which includes big hitters such as Bank of America, Credit Suisse, JPMorgan Chase, Barclays, Goldman Sachs, Microsoft, Cisco, VMWare, Redhat, and Informatica finalised version 1.0 of the AMQP standard.   It has been 5 years in the making, the market for messaging has changed a lot in that time.

What is ?

“The Advanced Message Queuing Protocol (AMQP) is an open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security.” - Wikipedia

The specifications are available on-line and several broker implementations exist, like the popular RabbitMQ and Apache Qpid. AMQP is built around a few easy to grasp concepts: