Understanding gRPC and gRPC Web
What’s the difference between gRPC and gRPC web? gRPC and gRPC-Web are entirely different protocols, but ultimately were built to work together. What is gRPC?
The latest posts and insights about Ambassador Labs - our products, our ecosystem, as well as voices from across our community.
What’s the difference between gRPC and gRPC web? gRPC and gRPC-Web are entirely different protocols, but ultimately were built to work together. What is gRPC?
Let’s say you’re building a new feature. You’ve gone through the API design and are trying to get the MVP running. Your frontend team is working on the front end, and your backend devs are building infrastructure and new APIs. But frontend is going faster than backend. This is understandable, as your backend team has a ton of new APIs to spin up. But the front-end developers want to see what data will look like in their components, and work out how to render out different states based on the API responses. How can the frontend do this without the APIs being up and running? Mock API lets you simulate the API responses, allowing frontend developers to continue building and testing their applications as if interacting with the backend services. We want to take you through this paradigm in detail, showing how it works, the advantages for all development teams, and how you can build mock API tests into your CI CD pipelines.
Think about platform engineering holistically, and it's what you've been doing already, but for your internal teams, now just bringing it out into the open," –Michael Levan
We’re in the age of serverless. Serverless functions, serverless storage, serverless gateways, serverless everything. Serverless computing has revolutionized the way we build and deploy applications. In 2023, the global market for serverless architecture was over $15 billion. This will only grow as more and more use cases for this technology are found. But even as serverless grows and benefits organizations, that doesn’t automatically mean it will work for you. It’s common for developers to jump on the latest technologies. Serverless works well for the specific use cases it was built for, but sometimes organizations can waste a lot of time and resources going down the serverless rabbit hole only to find it doesn’t fit what they are trying to do.
Modern web applications rely on Application Programming Interfaces (APIs) to handle client requests and transfer data between entities. API rate limiting is used to protect web resources and services by preventing the frequency of transactions from exceeding a set maximum number. In this article, you’ll learn: What rate limiting is,
Authentication Insights with Keith Casey