Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

How to do KVS #51

Open
viktorklang opened this issue Jul 18, 2019 · 3 comments
Open

How to do KVS #51

viktorklang opened this issue Jul 18, 2019 · 3 comments
Labels
backend platform Issues related to the backend platform enhancement New feature or request user platform Issues related to the different user target platforms

Comments

@viktorklang
Copy link
Contributor

Having support for Key-Value style state management would be interesting,
it could either be implemented on top of CRUD #50 by the Entity being a Map.

This also impacts the user-facing API as they would not have to deal with anything but the inbound commands (not events), by adding/modifying/removing the values in the Map.

@viktorklang viktorklang added enhancement New feature or request user platform Issues related to the different user target platforms backend platform Issues related to the backend platform labels Jul 18, 2019
@kwehden
Copy link

kwehden commented Aug 6, 2019

We should consider doing this on Postgres, to demonstrate that we work with other persistence stores outside of Cassandra. This I think is a perceived bias that we've seen in some feedback.

@viktorklang
Copy link
Contributor Author

@kwehden Agreed—I'm a big fan of Postgres as an RDBMS

@andyczerwonka
Copy link

@kwehden & @viktorklang using native hstore and/or JSONB within Postgres may make sense for this use case

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend platform Issues related to the backend platform enhancement New feature or request user platform Issues related to the different user target platforms
Projects
None yet
Development

No branches or pull requests

3 participants