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.
Get 20% off your ticket with special promo code: BLOG20
Whatever your role, or industry, CONNECT is the place to be.
Don’t miss the opportunity to engage in an interactive discussion with your peers around digital
transformation and learn why an API-led connectivity approach has become IT’s secret weapon at CONNECT 2015. Nearly every business priority can be enabled by IT through API-led connectivity. Whether you’re a CIO, an enterprise architect, or an IT leader, you’ll walk away with a number of innovative ways to improve and transform your business. Don’t miss the opportunity to be inspired, learn best practices, and take away practical solutions you can use today!
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. Hopefully by the time 3.7 is out, you’ll already be familiar with all the new goodies at your disposal.
Technology is disrupting industries, and no more so than in Healthcare where wearables, devices and the Internet of Everything (IoE) more broadly, provide the means to reframe how healthcare is delivered. These technologies are bringing hardware and software together to enable the provision of data, to both healthcare professionals and patients, and ultimately to enable better clinical decision making.
Delivering distinct solutions
In the past, there’s been a dichotomy between hardware and software. Companies, products and engineers alike were defined by whether they fell in the hardware or software camp. IoE is blurring these lines, as Apple’s Healthkit can attest. What these technologies are achieving is a fluid flow of data between device and application; patients must seamlessly be able to enter data from their individual device into a system to be accessed by their doctors, and conversely, individualized treatment plans or fitness recommendations are sent to personal devices from a central information system. We believe that the promise of innovation can only be truly by bringing hardware and software together in this way, to deliver truly coherent and distinctive solutions.
We’re pleased to announce that for the second year in a row, Gartner has named MuleSoft a Leader in the Magic Quadrant for Enterprise Integration Platform as a Service (iPaaS). CloudHub, the cloud-based integration component of Anypoint Platform, was evaluated in the Magic Quadrant.
Ken Yagen, our vice president of products, noted, “Digital transformation requires enterprises to rapidly integrate SaaS applications and digital services from
business partners with their existing back office systems. This calls for broad API-led connectivity and deployment on a platform that seamlessly connects the cloud and traditional data centers. Gartner’s recognition is a testament to CloudHub’s leadership and significant role in an enterprise’s hybrid integration strategy.”
Connect anyone, changes everything…
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, given the ever more disruptive ambience of modern lifestyles. Constant manual finger swiping simply will not do.
By leveraging MuleSoft’s industry leading connectivity technologies, combined with our newly developed Connected Universal People Identifying Decision (CUPID™) engine, we have created an API-centric innovative dating solution that will automatically make the optimal matches for the lonely souls out there. A user can simply make a call to the CloudShack REST API, all the while remaining restful (pun intended), and CloudShack will handle the rest and return the best match. Imagine, a dating platform where all the exchange patterns are request-response, processing strategy is not just synchronous but also harmonious, and every outbound endpoint finds itself an inbound endpoint. That is CloudShack.
Financial services industry standards and file formats are unique and complex. There are different standards for low value payments, high value payments, international payments, bank statements, securities trades, derivatives, and stock custody transactions. In an effort to unify disparate formats based on geographic boundaries, industry utilities and market participants, the International Organization for Standardization (ISO) developed the ISO 20022 XML standard. The ISO 20022 standard was originally developed in 2004 and is an internationally agreed upon, global set of common standards for the development of financial services messages using a standardized XML syntax.
ISO20022 Migration Initiatives Underway
Adoption of ISO 20022 has reached a critical mass and implementation efforts continue to evolve. The European Union’s SEPA credit transfers and direct debits migration, completed in 2014, was the first high profile ISO 20022 standardization project. There are many other ISO 20022 migration initiatives underway across payments, securities, treasury, trade services, cards, and foreign exchange, including:
UX, meet Engineering. Engineering, meet UX. You two should talk.
MuleSoft’s very own Mason Foster, Director of User Experience, checked out this year’s SXSW Interactive festival and made an interesting observation. In a recent post on re/code, he points out that, “there were myriad opportunities for engineers to learn the ins and outs of the hot technologies, and countless rooms packed with user experience (UX) professionals discussing the latest trends in design. But you didn’t see these folks talking to each other, and there weren’t many structured opportunities to do so.”
This post brought to you by Christopher Jay. The original article can be found on The Australian Financial Review.
In the ever-evolving world of the internet, transferring data between different internet locations and organisational databases is becoming a lot easier with the dramatic spread of a particular set of software modules designed to standardise routine connection tasks.