Finding efficient ways to process, share, and reuse functionality and data is crucial – it’s an important way to break down monolithic applications into more consumable and maintainable microservices. In today’s API-focused world, this translates into multiprotocol development (gRPC, GraphQL, EDAs, etc.) and an enhanced development process (governance, standards, design-first). To understand this, we need to look more closely at protocols.

Since the early ’90s, computer users and businesses have used Adobe’s venerable PDF format as the de facto choice for digital documents where portability and advanced features such as form-filling, digital signatures, and accurate rendering is important.

Growing your career can be both scary and exciting, and our SEO manager Savannah Whitman experienced both before joining Moesif. Now she’s nurturing search rankings to bring the latest in API observability to technologists who need it. In this installment of Meeting Moesif, we talk to her about where API technology is heading, and what it takes to keep up.

The technology you choose to start your project with determines what your product is capable of now and what it will be capable of in the future. Finding the right stack to build on top of is one of the biggest engineering challenges you can face. Picking a stack that allows you to build a product and get to market rapidly is great unless that same choice limits the scalability and features of a product in the future.

For many companies, performance is the main reason to go with GraphQL. But is that a valid argument? Often developers compare GraphQL to REST APIs and see the N+1 requests (or over-fetching) as an important reason to go for GraphQL. Let's put that to the test and explore if GraphQL APIs actually can outperform existing REST APIs. For this, we'll take a GraphQL-ized REST API (from JSONPlaceholder) and test the performance of GraphQL and compare it to the REST approach.

CMA CGM is a global player in sea, land, air, and logistics solutions, serving 420 of the world’s commercial ports and operating 285 shipping lines with 580 vessels. Supporting such complex international logistics requires a sophisticated and reliable IT infrastructure, underpinned by APIs that unlock the data needed to flow across the ecosystem of internal IT, partners, and customers.

Kubernetes shouldn’t be reserved for production. Using local Kubernetes in development means you can build and test your service using the same technologies as your live deployments. Some organizations provide a shared Kubernetes cluster for development activities. Others offer on-demand virtual clusters that serve staging environments for significant changes.

Knowing how to deal with APIs to allow communication between software systems is essential if you're a web developer. This article will show you how to develop a CRUD REST API in a Node.js environment using an Express.js server and a PostgreSQL database. We'll go over how to use node-postgres to connect an Express.js server to PostgreSQL. The API will support HTTP request methods that correlate to the PostgreSQL database from which it gets its data.