Systems | Development | Analytics | API | Testing

Managing Application Auth for Different Audiences

Let’s pose a hypothetical scenario. You're the API product owner at the Paris, Texas Regional Airport. You're in charge of two main APIs: Flights API and Scheduling API. Flights API is primarily used by local research institutions that are interested in read-only access to information about departures and arrivals. Scheduling API is primarily used by airline partners who are interested in updating information about their flights and gates.

The 4 Biggest Challenges of Scaling Cloud-Native AI Workloads

When working with #AI in cloud environments, traditional data provisioning and software testing methods don't work because of the behavior of AI and LLM APIs. In this Cloud Native Computing Foundation (CNCF) webinar recording, we discuss the top 4 challenges of scaling cloud-native AI workloads, and the solutions developers are turning to instead.

How To Estimate API Development Time

Application programming interfaces (APIs) have quickly become vital to modern businesses. APIs work by allowing different systems to talk to each other and share data. The commercial use of APIs and web APIs has skyrocketed over the last decades in accordance with the rise in app development, mobile apps, and e-commerce. However, how do you estimate API development time? Well, API creation and the development time frame will always vary from project to project.

7 Must-Know Factors in API Development

An API (Application Programming Interface) is a set of rules and protocols that let software programs communicate with each other. It acts as an intermediary between different software or services. For example, when using a mobile app to book a hotel room, the API allows the app to communicate with the hotel’s booking system. While many REST API developers have their way of doing things, some factors in API development are generally considered essential.

Choosing The Perfect Message Queue: Factors To Consider

Not long ago, I was handed a problem that’s no stranger to the world of programming: making asynchronous threads communicate effectively within the same process. Given the widespread nature of this issue, I expected to find an existing solution to resolve it. My search led me to the concept of message queue, which seemed promising for streamlining this communication challenge.

GitOps Integration with WSO2 APK: Kubernetes Native API Management

Explore the seamless integration of GitOps with WSO2 API Platform for Kubernetes (APK) in this enlightening screencast session. The need for a robust API management solution that fits naturally into the Kubernetes ecosystem has never been more critical. WSO2 APK emerges as a solution designed to harmonize with Kubernetes-native practices, offering native GitOps integration to API lifecycle management. This session delves into how WSO2 APK not only simplifies the deployment and management of APIs within Kubernetes clusters but also enhances operational efficiency and consistency through GitOps methodologies.

GitTogether | Let's get Meshy with Istio Service Mesh | Leon Nunes

In the world of microservices, networking and Observabilty is always a challenge, often there are different methodologies used. A service mesh is something that standardizes this. Istio service mesh is a mature framework that runs in K8s and provides a standard interface for this In this session we will do a istio 101 and go over how a service mesh helps with microservices and hybrid architectures.

Resolving Database Conflicts with Centralized APIs in Microservices

Back in the 2000s, code lived in one execution thread. Database queries, user interactions, and data pipelines were all managed by the same processes. The problem? Everything was interconnected and interdependent. Fixing one thing might break another. Releases were all or nothing. We call this monolith hell. Your ticket out? Microservices.