Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage providers #2

Open
Ryccoo opened this issue Nov 22, 2017 · 1 comment
Open

Storage providers #2

Ryccoo opened this issue Nov 22, 2017 · 1 comment

Comments

@Ryccoo
Copy link
Member

Ryccoo commented Nov 22, 2017

Integrate a persistent (preferably) storage into charyf-core.
Should be configurable the application config.

It is important to define the outer contract so different implementation can keep it. The base contract should define a key value storage.
Key should always be string.

Value may be an object

  • it is important to determine how to implement for instance redis like storage -> Object should support to_json method then.
@Ryccoo Ryccoo self-assigned this Nov 22, 2017
@Ryccoo Ryccoo added this to the Version 1.0.0 milestone Nov 22, 2017
@Ryccoo
Copy link
Member Author

Ryccoo commented Mar 30, 2018

In memory-storage provider is available now, which is sufficient. May require a redis version to persist data for production.

Memory providers are used for internal parts and strategies -> app code should be handled on its own. For now, message IDs are mainly stored to avoid dispatching the same message twice (facebook interface sends the message again if it does not get response correctly in time)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant