API proxy router

ignesia · 2014-04-12T03:28:55+00:00

Hello! On Fri, Apr 11, 2014 at 4:12 AM, info wrote: > Is this a openresty thing or is this also valid for most individual modules > like nginx for Wi...

API proxy router

ignesia

Hi,

I am creating an API proxy router with openresty and I want to know best approach.

My solution right now looks like this:

A GUI generates a JSON document that basically points routes to endpoints. For example:

GET api.myproxy.com/users/{id} -> internal-oauthserver.mydomain.com/users/{id}

Instead of generating all the routes into a static Nginx conf, because I have to restart Nginx every time I change routes I am thinking of putting all routes into Redis.

So Redis will map all possible routes defined in the JSON document by importing the JSON into Redis. Or if the GUI can access Redis directly I will just edit the Redis records.

Every time Nginx gets a request, lua with will look into Redis to see if there is a match on that route, if there is it will proxy the data back and forth. If there is no match it will return an error message.

Is this a good approach? Thanks.

If this has been done already it would be nice to get a hold of that code.

agentzh

Hello!

On Thu, Apr 10, 2014 at 5:57 AM,  ignesia wrote:
> So Redis will map all possible routes defined in the JSON document by
> importing the JSON into Redis. Or if the GUI can access Redis directly I
> will just edit the Redis records.
>
> Every time Nginx gets a request, lua with will look into Redis to see if
> there is a match on that route, if there is it will proxy the data back and
> forth. If there is no match it will return an error message.
>
> Is this a good approach? Thanks.
>

Looking good to me. And you can also use the lua_shared_dict to cache
your redis results in the shared memory.

> If this has been done already it would be nice to get a hold of that code.

Yes, there is a similar demo example:

    http://openresty.org/#DynamicRoutingBasedOnRedis

Regards,
-agentzh

peter_booth

I think the key questions are "how often will new routes be added / roved?" "How often will the proxy irks be called ? " and "what performance guarantees do you need?"

Openresty is a great toolkit for building complex proxies - it's robust and fast .

Sent from my iPhone

On Apr 10, 2014, at 8:57 AM, ign...@gmail.com wrote:

Hi,

I am creating an API proxy router with openresty and I want to know best approach.

My solution right now looks like this:

A GUI generates a JSON document that basically points routes to endpoints. For example:
GET api.myproxy.com/users/{id} -> internal-oauthserver.mydomain.com/users/{id}

Instead of generating all the routes into a static Nginx conf, because I have to restart Nginx every time I change routes I am thinking of putting all routes into Redis.

So Redis will map all possible routes defined in the JSON document by importing the JSON into Redis. Or if the GUI can access Redis directly I will just edit the Redis records.

Every time Nginx gets a request, lua with will look into Redis to see if there is a match on that route, if there is it will proxy the data back and forth. If there is no match it will return an error message.

Is this a good approach? Thanks.

If this has been done already it would be nice to get a hold of that code.

.