How should developers and employers get the most from each other?
There is growing pressure for IT to deliver on business demands in real time—but there is often a gap between what they need to do and what they can do. So, how can they close the IT delivery gap? For starters, they should make everyone in the company a developer.
This is part 3 of my API security blog series. I will be showing an example scenario of how Anypoint platform can be a vital component of a secure API-led architecture and the capabilities to securing the API.
If you missed part 1 and part 2 here they are:
- API security: Ways to authenticate and authorize
- API security: Keeping data private but accessible
The vast majority of RESTful APIs follow a simple “request-response” message exchange pattern, but that pattern is often too limiting and is not sufficient to achieving robust and reliable application performance. We frequently get questions from customers asking: ‘How I design asynchronous APIs?’ and ‘How I design an API that allows for the concurrent modification of the same API resource without bringing the resource into inconsistent state?’. In this blog post, we present two approaches answering these questions using standard HTTP headers and status codes. Further, we provide RAML snippets that can serve as a starting point when designing such APIs.
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.”
Traditionally, “Application Program Interface (API)” was a term known mostly within the developer community. Also, it would be rare to hear about a marketer or a financial analyst “working with APIs.” However, as technology continues to evolve, there are more data and ways to measure data. A particularly interesting topic – marketing technology – came across my mind, and after some research, I’ve noticed marketers were actually the largest consumers of APIs.
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.