Skip to content

A better and more reusable API GTW

José Bonnet edited this page Feb 9, 2018 · 12 revisions

This wiki page summarizes the thoughts and discussions behind 5GTANGO's issue #225 (pictures' source available here).

This is a WiP!

Context

In SONATA's v3, the Gatekeeper has the architecture shown below.

The Gatekeeper's high level architecture.

This architecture has served us very well, but we can improve it in order to make the Security Gateway and the Gatekeeper API more re-usable (namely for the 5GTANGO project, where there'll be a Validation&Verification Platform with similar needs in terms of an API Gateway).

Discussion

The Security Gateway and the Gatekeeper API modules shown above can be made generic so that they can also serve the V&V Platform.

The result would be something like it is shown in the next picture.

Proposed API Gateway, to serve both V&V and Service Platforms.

Eventually, more modules could also be made autonomous in order to be re-used (e.g., the Package Manager).

This API Gateway could be re-used as shown in the next picture:

How the API Gateway could be re-used

This clearer separation would allow for a (later) replacement of this API GTW by another one, like AWS's, Kong's, etc. This is not done at the moment since we would have to pay for AWS sooner or later and using Kong would mean to migrate User Management, KPIs, etc, to their plugins.

Conclusion

Clone this wiki locally