Show HN: I've built Routify, a global serverless API gateway (routify.to)

8 points by hakanshehuu 2y ago ↗ HN

Hello HN, for the past couple of months I've been working on Routify and wanted to share the progress made so far and hopefully get your opinion/feedback on it. Routify is a global serverless API gateway which handles routing, authentication, rate limiting, load balancing, monitoring, transformation etc (with more coming soon).

Routify makes it easier to manage and secure public APIs. It's distributed across many regions globally and acts as a proxy between your clients and your services. You can configure it through the interface in a matter of minutes (no code required).

There are three main concepts:

- Routes - paths that define different operations in your API (can be with dynamic/optional/catch-all parameters) - Backends - a cluster of endpoints where the requests will be proxied to - Middlewares - functions that are executed in a specific order in Routify edge proxies and define how requests are processed.

You can use it as a reverse proxy, as a gateway between your APIs in different cloud providers, as a geo load balancer or simply as a monitoring tool for all requests going through your API. It also provides multi-region healthchecks and alerts based on the requests.

So far, it has processed 100+ million requests without any issue. The average processing time for route matching and middleware processing is ~1ms (this does not include the network operations when proxying the requests).

For those interested, Routify is in public beta and free to use at https://routify.to.

You can check a demo of how it works here: https://www.youtube.com/watch?v=iDisClPv09A

Thank you!

2 comments

[ 3.1 ms ] story [ 16.6 ms ] thread

hackistio 2y ago ↗

It looks incredibly easy to use, which is a huge plus for small to mid-sized businesses that need a powerful API gateway but don't want all the complexity that comes with it. This really fills in a gap, from a reverse proxy that lacks features and an enterprise solution which is overkill and expensive.

riadasllani 2y ago ↗

We have started using this for two different features.

We provide a solution for multiple clients, and based on a key issuer we are redirecting request directly to the client, this served helpful with deploying updates directly for clients without a need for any change on our end, giving this possibility to the closest locations to users, and also logging and showing useful data directly to clients utilizing Routify!