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.
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.
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.
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.
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.
Are we sitting on major security vulnerabilities right now? How has security changed in the past 20 years? We interviewed Ilkka Turunen, Sonatype Field CTO and Muzaffer Pasha, Security Evangelist at Traceable about how to achieve better security in open source and in your organization.
We spoke with Borya Shakhnovich, CEO of airSlate, about the capabilities of no-code solutions and how they help empower non-technical business users. Borya Shakhnovich discusses some tips and things to consider when developing APIs and how airSlate overcame challenges during API development.
Java continuously introduces new, useful features. For instance, Java 8 introduced the Stream API, one of the biggest highlights of the past few years. But is aggregating data with the Stream API a panacea? In this article, I’d like to explore if there’s a better alternative for certain cases from a complexity perspective.