Spring-cloud-gateway: Provide some default implementations for "persistent" RouteDefinitionRepository

[dennis-menge]

Hey there,

in short - what do you think of adding a few default implementations to store Route Definitions within some storage backend (Mongo/Redis/etc..) in order to share routes across instances?

To provide some context, we currently use Redis and have implemented a custom RouteDefinitionRepository in order to share routes between multiple instances of the Gateway which works really well.

Currently, Spring Cloud Gateway only offers the InMemoryRouteDefinitionRepository which is probably just a "fallback" leaving it up to the user to implement it on their own approach, right?

However, I think it would be quite appealing to add some configurable RouteDefinitionRepository implementations to the Gateway to be usable out of the box.

Whats your opinion?

If you like it, I would like to start working on it :)

[spencergibb]

PRs welcome, especially if you have a working one on based off of redis. Gateway already has support for redis with rate limiting.

[dennis-menge]

Alright, then I will start working on that

[MatheusAThomaz]

How is it going? There is some forecast for this? I'm need something like that and I'm open to help with it. @spencergibb @dennis-menge

[dennis-menge]

The PR is open since November last year. No feedback since then, I would highly appreciate to get this integrated. Maybe also a r2dbc implementation as well.