MuleSoft recently announced their Anypoint Platform supporting the development, deployment and integration of cloud and on-premise services. InfoQ caught up with MuleSoft CTO Ross Mason during his global Mule Summit tour to talk about the new platform. Ross founded the open-source Mule project.
WSO2 Developer Studio 3.0 and 3.1 improve ESB and Registry Resource Editor tools, has better performance, uses Eclipse Juno SR2, and supports JAX-RS REST code generation.
In his new post Subbu Allamaraju discusses some of the problems with current APIs usage and suggests the introduction of an additional layer responsible for aligning APIs to the client requirements.
Jaime Ryan in an article for ComputerWorld recommends the replacement of ESBs with lower-cost, easy-to-use and lightweight modern SOA gateways which fulfill not only the typical ESB functional requirements but also add non-functional capabilities. InfoQ spoke to Jaime Ryan to present his detailed analysis behind this reasoning.
A couple of weeks ago, MuleSoft announced the availability of its new Integration Platform as a Service: Mule iON. This iPaaS comes with a series of out-of-the-box connectors to integrate with SaaS solutions, Cloud services and social media platforms. Mule iON also provides a secure gateway to the enterprise to access these APIs and integration scenarios.
This week, MuleSoft released version 3.1 of its enterprise service bus, Mule ESB. Mule 3.0 was released in September with one major focus: "simplify everything...to make Mule 3 more accessible to everyone". This week, Mule 3.1 takes the simplification further by focusing on Mule Cloud Connect, Mule Flow and BPM.
Ross Mason, founder of MuleSource expressed his frustration with OSGi: "OSGi is a great specification for middleware vendors, but a terrible specification for the end user." He argues that OSGi just isn’t ready for the developer yet as it is too difficult to completely make it invisible to a developer.
A long standing debate in the SOA community about top down vs. bottom up approaches to SOA resurfaced recently, after open source ESB maker MuleSoft announced the release of a management console said to support their bottom-up approach to SOA management philosophy.
In his new post, Ganesh Prasad tries to describe the most complex issues of an SOA implementation and provides recommendations on how to solve them.
Tcat Server, an Apache Tomcat-based application server created by MuleSoft (formerly MuleSource), was released today. InfoQ took the opportunity to talk with Mahau Ma, Greg Schott and Ross Mason of MuleSoft to learn more about Tcat Server and another new integration framework called iBeans.
The NServiceBus, previously covered by InfoQ in an interview with Udi Dahan (the creator of NServiceBus), is just released in version 1.9. The new version includes a decreased footprint on dependency injection frameworks like Spring.NET and the amount of assemblies referenced is reduced to only one.
Jack Van Hoof presents a prescriptive guidance on how to model a federated service bus infrastructure such that it affords the various parts on the enterprise interacting with it, the desired levels of autonomy.
Clemens demonstrated the capabilities and the programming model of the Azure Service Bus. The ASB offers secure and reliable functionality for connecting business partners, services and composite applications across the Internet.
In an article on SOA Governance, Ross Mason, CTO and Co-Founder, MuleSource, says that in today's world, the traditional top-down philosophy for SOA is outmoded and outdated and urges for a more practical real-world approach to governance and SOA in general.
A new three-part post by Neil Ford discusses both the rationale behind SOA implementations and the role large vendors play in distracting them.