The gateway from marius321967

gateway's Introduction

Service which provides a central gateway for applications (microservices) to push and pull data via async events or continuous streams. It solves the issues of connection, authorization and credentials keeping. Data producers and consumers are decoupled - this helps to develop applications asychronously.

For example, you deploy an application to your RaspberryPI which measures temperature. The application then sends the data to Gateway via an event of type measurement:weather. Another application - a cloud service - listens for new events of this specific type and processes them once they are received.

For more, read the wiki.

gateway's People

Contributors

Watchers

gateway's Issues

Error code when pushing stream type is undefined

Currently the system does not check whether the client has provided the data type when they are pushing a stream. This error is returned: { "code": "DATA_TYPE_UNAUTHORIZED:streams:undefined" }

Update the code to check whether the type was provided and return some specific error code, then document it in the wiki.

Specify host & port with environment variables

Add the ability to specify the host and port which Gateway listens to.

Store hashed versions of Basic tokens

Storing the hashed version of an auth token instead of the original one would improve security. In case the token file was compromised but not altered, the attacker would be unable to obtain a valid token if they didn't know the hash seed.

Update requires new services for hashing and manipulating the tokens file. There also needs to be a console interface for storing and removing tokens.

Custom token validators without having to fork the project

The service would be easier to use for developers if they could implement their own token validators without having to fork the project and understand existing code.

The implementation should work well with Docker.

Recommend Projects