Catalyst Accelerate for Healthcare webinar is now available to watch on demand.
Slides are also available now, click here to view them.
The combination of legislative, technological, and market pressures has created a digital transformation imperative in healthcare.
For healthcare IT teams, addressing this imperative requires the the ability to expose and orchestrate data between clinical and non-clinical systems, while doing so in a way that promotes reuse and accelerates project delivery.
I wrote a piece in July, Future of Fintech depends on APIs, talking about the landscape of Fintech and how a regular part of our lives today is enabled through Fintech innovations and APIs.
Here, I want to talk about banks and how they shouldn’t see fintech players as competitors, but partners. We’re also seeing the trend where banks are either partnering up with fintech companies, acquiring them, or funding them. Some banks are even launching them their Fintech subsidiaries – see diagram below:
An Enterprise Service Bus (ESB) is a set of principles and rules for connecting applications together over a bus-like infrastructure. ESB products enable users to build this architecture, but they differ in their methodology and the capabilities they provide. Mule as an ESB is the runtime engine of Anypoint Platform.
In today’s world, APIs are used to abstract the complexity of systems of records, to provide secure connectivity to the end systems, and to accomplish business goals such as creating a unified view of a customer. But APIs alone cannot accomplish all integration use cases. For example, when you want to send data from won opportunities in Salesforce to SAP for invoice creation, on top of using APIs, you will also want to do data migration and/or data synchronization to accomplish this use case.
We get requests from time to time about guest blogging at MuleSoft. Here is an official post about it if you are interested in submitting a guest post.
Should you guest blog?
Of course! You have valuable insights and content and we want to help you share that information with others.
Some benefits include:
- Thousands of readers will get to read and interact with your ideas
Today’s post is from Sean McClure. Sean is the Director of Data Science at Space-Time Insight, a leading provider of advanced analytics software for organizations looking to leverage machine learning for their business applications. Having worked across diverse industries, and alongside many talented professionals, Sean has seen the blend of approaches required to convert raw data successfully into real world value. Sean’s passion is working with cross-discipline teams to build the next generation of adaptive, data-driven applications.
A recent trip to Istanbul got me thinking about enterprise IT architecture. Seriously! If you’ve ever been to Istanbul, you’ll know that it’s a fast-growing, vibrant, and dynamic city. Unfortunately, the roads can also be very congested at times, taking hours to get from one side of the megacity to the other.
This post will be part 1 of 3 for my ultimate guide to API security best practices series. In this post, I will be discussing the current concerns IT decision makers have in regards to their current digital assets.
Part 2 will address the need for keeping data private and protecting it from being compromised while making it accessible at all times.
MuleSoft Anypoint Runtime Manager (ARM) provides connectivity to Mule Runtime engines deployed across your organization to provide centralized management, monitoring and analytics reporting. However, most enterprise customers find it necessary for these on-premises runtimes to integrate with their existing monitoring systems such as Splunk and ELK to support a single pane of glass view across the infrastructure.