Microservices is one of the hottest buzzwords in tech right now. But just because something is buzzy doesn’t mean we cannot be pragmatic about it. It is important to think about how you can get the hype to work in your organization.
In the healthcare industry, data interoperability has long been considered a holy grail. And eight years after the passage of the HITECH Act, which promised to create incentives for healthcare providers to “meaningfully use” electronic health record technologies and open access to medical data, interoperability still remains a massive challenge.
Late last year, the US Department of Veterans Affairs announced the completion of a Proof of Concept for a Digital Health Platform (DHP) which promises a solution to these interoperability challenges.
How do you transition your organization from mainframe to microservices?
According to our recent survey of IT decision makers, 91% say that they are either undertaking digital transformation initiatives or planning to do so in the next three years. But nearly half say also say that legacy systems are the single biggest obstacle to achieving their digital transformation goals. Clearly, legacy modernization is on the minds of IT decision makers and is a key issue to resolve.
With the rise of new technology trends, changing consumer behavior and disruption by new market entrants across industries, one thing has become clear: Speed is becoming the currency of success as organizations adapt to ever-changing market forces.
As such, the trends that are set to take hold over the next 12 months are ones that will not only help an organization evolve, but do it faster than the competition.
A convergence of digital forces – notably mobile,
This post is by one of our MuleSoft champions, Antonio Abad.
Let’s start with a simple definition of both concepts:
“An ESB is basically the integration of the new and the old, providing a central place for the services, applications, and IT resources in general that you want to connect.”
“A microservice architecture (vs. the legacy monolithic architecture) is an approach to developing a software application as a series of small services,
Every business needs to stay agile. Every business wants to improve their speed. Every business wants to innovate faster. And they want to achieve these things not only today, not only tomorrow but for years in the future. This is true for established businesses dealing with digital disruption, but also the disrupters themselves. That’s why we’re excited to announce that Spotify, the world’s most popular and powerful streaming music service, has implemented MuleSoft’s Anypoint Platform™ to improve business agility and operational efficiency.
Download our Best Practices for Microservices whitepaper to gain a deeper perspective about our approach to microservices written in this post.
If IT today has a watchword, that word is “speed.” At the same time, IT is expected to protect the organization’s crown jewels (company finances and private customer records) and to keep services available and responsive. The message: Go faster, but don’t break anything important. Even Facebook has modified its motto on this front from “Move fast and break things” to “Move fast with stable infrastructure.”
In response to these pressures,
Featured guest post on MuleSoft Blogs from Abraham Santiago, Principal Integration Consultant of WhiteSky Labs.
API middleware integration industry is definitely not short of Architectural principles, from top-down strategic initiatives like digital transformation and legacy modernization to developer-centric ones like event-driven architecture, microservices, and DevOps. But beyond that and onto the fun and games of actual delivery of services to enterprise customers,
Govind Mulinti, a senior architect at Whishworks, is the guest author of this blog post.
Microservices has been a buzz word for past few years. It talks about a technique of designing integrations and APIs as independently deployable services. There are certain characteristics around organizations around business capabilities, automated deployments, intelligent endpoints and distributed control of data.
Before we start on microservice style,
In this blog post, I would like to highlight the similarities between the physical logistics of moving physical cargo containers and the digital logistics of moving data. In essence, I want to translate the shipping jargon into everyday language to allow you to gain an insight into the world of containerization. Equally for the Container Terminal Managers and their IT teams, this blog post takes optimization from the yard to the server room; I want to highlight that integration of systems is critical and how having the right approach can enable your business to flourish.
Sign up for our newsletter
Sign up for our newsletter
