25
Mar
/
Unlocking Business Benefits with APIs
Renowned API expert Liad Bokovsky discusses the transformative power and benefits of APIs in the business landscape, highlighting their ability to enable faster innovation, strengthen partnerships, and enhance customer experiences. He also provides practical guidance on bridging the gap between business needs and technology solutions for successful API programs.
31
Jan
/
The Dangers of API Design
APIs are an interesting topic, especially from a security perspective. Consider what an API is designed to enable. An application can communicate and exchange data with another application, including over the public Internet. By its very nature, an API must be publicly accessible. This makes APIs especially vulnerable to attack.
9
Oct
/
API Design with Patterns: Patterned Design
Designing APIs is a critical activity in many software projects. Its success depends upon requirements and the experience of the API designers. Pattern collections document collective experiences, making it possible to arrive at suitable designs quickly and with less risk. Join us on a short journey through microservices API patterns that look at protocol-independent problems in API design and propose proven solutions in a compact manner.
13
Sep
/
Conducting API Design Reviews
This article shows why it is extremely important to conduct API design reviews before interfaces go live.
26
Jul
/
Quo Vadis, API Management? Developments in API Management
Over the last 20 years, API management has developed dynamically. You could go back even further in the history of “computing” and end up in the late 1960s, where the term “application program interface” first appeared in literature. But let's limit ourselves to the more recent past, where the discussion is still interesting and enlightening.
26
Jun
/
REST APIs: Stop Polling, Let’s Go Streaming
REST APIs have become the dominant means for distributed applications to communicate over the last ten or fifteen years, whether that is client-server such as mobile applications, web clients, or server-server between monoliths and microservices. However, the way REST works and increasing demands on how the REST paradigm works has seen the idea and frameworks around REST-based web services evolve, including the adoption of the idea of streaming. Streamsing represents the data source's ability to continuously send to the client data, just as we do with video and audio media, rather than request-reply. We will look at why we should consider it as part of our kit bag of technical options, how streaming works, the considerations needed in adopting the approach, and the frameworks that have supported and helped its adoption.
24
May
/
A Successful API-first Strategy? Do This
What do four horsemen, three golden rules, an iceberg, and a cloud have to do with a successful API-first integration strategy? This is not the start of a bad joke. These are the ins and outs of successful API-first approaches.
22
Mar
/
tsoa: API documentation for Node.js
JavaScript is known as the Wild West of web development. But despite the absence of law and order, there are a few things that even the wildest developers should stick to. These include consistent structure, documentation, and testing. We will take a look at how that works for API documentation with tsoa for Node.js.
21
Feb
/
The Role of APIs in Digital Government Context
Connecting information systems, applications, and registers, exchanging data, and sharing services are essential requirements for any digital service. Government and the public sector are no exception. The ability to exchange data and share services between government entities and authorities is a must-have requirement when public services are digitised. Also, the need is not limited to data exchange capabilities between government entities since the ability to exchange data and share services between public and private sectors is evenly essential.
5
Dec
/
API Contract Definitions – Different Ways of Specifying API Contracts: Contract first, implementation first, OpenAPI, GraphQL, gRPC
When running one or multiple services, it is essential that they have reliable service contracts defining their exposed APIs. Those contracts mostly consist of declarative interface definitions, which strongly define and type the API exposed by the respective service. As such, it is crucial that the code making up the service exactly implements the interface and therefore fulfills its side of the contract. Regressions need to be detected and changes reflected in a well-communicated update to the contract. Here, we want to look at different ways of specifying contracts for what is one of the most common protocols for exposing service APIs: HTTP.