AWS pioneered the idea behind serverless when they introduced AWS Lambda: focus on your business logic down to its atomic parts of your applications — functions — and let them worry about the rest. This whole idea eventually led to the NoOps movement.
Serverless is a great idea! It’s a new paradigm that can be applied to how modern applications are developed and run in the cloud to drastically increase developer focus and productivity.
But there are challenges and even “gotchas”…
After three long months of hard work, we’re proud to announce that the LunchBadger Platform is now the Express Serverless Platform. New name, new features and an opportunity to experience a visual canvas ripe with all the important functionality that developers need, without the hype.
For Developers, DevOps teams and CTOs driving impact in top companies, it’s not just a name change — it’s a game changer and we can’t wait to show you why.
Let’s start with the basics. When you’re developing and launching an application, you’ve got enough to worry…
As a follow up to the last post about getting started with application specific metrics using Express Gateway, it’s time for a real time example.
By the end of this post, you’ll be able to:
So, you have everything you need to start building your own plugins and getting metrics on information you care about. Let’s go!
By now, if you’ve been following along you have created your plugin and it’s ready to be used. So, we have to install it in the Gateway and enabled it.
What are JSON Web Tokens? Why do they matter in the context of microservices architectural style?
Glad you asked. There’s a lot to discuss when it comes to JSON Web Tokens, but let’s start with an overview of an API Gateway and then we’ll dive deep into JSON Web Tokens and how to get started (including a great new video tutorial).
You’re probably wondering what is an API Gateway and why does it matter.
TLDR: It’s kind of a big deal.
Here’s a little secret on why: it straddles both the business side and technical side of your business. An…
Unless you’re building a proof of concept or an application that’s not aiming to reach the production, you definitely want to add monitoring and metrics to your system. In this installment we’re going to look how Express-Gateway can help you to add application specific metrics and expose them through an HTTP endpoint that can be queried by an external service, such as Prometheus.
Express Gateway is an API Gateway that sits at the heart of any microservices architecture. Regardless of what language or platform you’re using, it securesdifferent microservices and exposes them through APIs using Node.js, ExpressJS, and Express.js middleware.
Slow on updates. Heads down on the hustle. These two things can sometimes go hand in hand. However; we wanted to take a hot sec and provide more information on the exciting developments since you last tuned in for Express Gateway Release 1.5.0.
This is an important milestone for any open source project and we are particularly excited by the opportunity, trust and collaboration we have experienced from the developer community.
From these collaborations, we have listened thoughtfully to the issues facing teams and collected resolutions to these issues into the latest release. …
In the latest release of Express Gateway 1.5.0, we’ve included support for JSON Web Tokens (JWT). This is the primary update for 1.5.0 and we think you’re going to like it. At the end of this post is a special demo and we’ve provided some getting started code snippets as well so you can get up a running. As always, we love your feedback and support.
So if you’ve got questions or would like to see more of this — holla at your favorite badgers! We’re proud to sponsor this open source project in partnership with Joyent.
So as you…
Always be shipping code! Open source projects are no exception. In the latest 1.4.0 release, we’ve got a set of brand new features and crushed some pesky bugs. In case you’ve been following along at home, you’ll notice that several of the features and bugs that have been included were direct recommendations or contributions from the community. Thank you for the ongoing support.
Now — on to the good stuff!
Express Gateway has a lot of powerful features beyond just auth. Another important feature is rate limiting, which throttles requests to one or more endpoints. Express Gateway has a lot of tuneable options for configuring throttling: you can throttle requests on a per user, per endpoint, or per pipeline basis. In this article, I’ll walk you through a “Hello, World” example of using Express Gateway’s rate limiting policy, and then show a practical use case of rate limiting based on user API keys.
To get started, let’s create a gateway with one endpoint that prints out the requesting user’s IP…
Let’s start by saying, today is an important day for us. In the months since we initially launched Express Gateway at NodeJS Summit, it’s been an incredible journey of learning, giving back to the developer community and above all — checking out some amazing open source projects.
If you’re just joining the conversation, we wanted to make Express Gateway, an open source API Gateway built entirely on Express.js more accessible to developers who have been forced to hand roll this solution.
With Express Gateway, you actually get to leverage the vast ecosystem of Express.js …
Builders of Express Serverless Platform, multi-cloud platform for microservices. Sponsor of @express_gateway, an #opensource #API Gateway built on Express.js.