You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Memphis's core value is to build streaming use cases faster, with a low amount of code.
This feature is a milestone - building a modular framework, easy-to-modify, adjust, and scale connectors framework
that will eliminate the need to create consumers/producers that only collect and push data from/to popular sources.
Context
Based on multiple requests by our users asking to have ready-to-use connectors to pull and push data from and directly to Memphis or out. The number of connectors cannot lean on Memphis team resources and should be built to enable users to quickly implement their type of connector in case they can't find the connector they need in the Hub.
Value
Build fully operational streaming pipelines in a low-code manner
Persona(s)
Data Engineers
Developers
The text was updated successfully, but these errors were encountered:
I finished syslog-adapter and started to look on old issues
Connectors and Framework are two appealing words
But not clear at least for me what should be done
How we can discuss this feature?
Summary
Memphis's core value is to build streaming use cases faster, with a low amount of code.
This feature is a milestone - building a modular framework, easy-to-modify, adjust, and scale connectors framework
that will eliminate the need to create consumers/producers that only collect and push data from/to popular sources.
Context
Based on multiple requests by our users asking to have ready-to-use connectors to pull and push data from and directly to Memphis or out. The number of connectors cannot lean on Memphis team resources and should be built to enable users to quickly implement their type of connector in case they can't find the connector they need in the Hub.
Value
Build fully operational streaming pipelines in a low-code manner
Persona(s)
The text was updated successfully, but these errors were encountered: