Hey,
thanks for your intrest! yes, other databases can be supported,
but adapters have to be implemented for it. all storages are
interfaces and can easily be replaced. currently, in memory and
rethinkdb are supported / implemented. if you need assistance let
me know.
before you go ahead and start hacking, i suggest to check out the demo and play around with the CLI and HTTP api. if you encounter bugs, ask here, in gitter or on github! this is right now the best way you can help and you will learn to use hydra and see if it really fits your needs!
if it's possible, i recommend to stick with the rethinkdb backend. rethinkdb was chosen because it supports pub/sub. this allows hydra to keep all data in memory and make it super fast and reliable. every request to your api will be authorized using hydra, so it's important to keep it fast :) with traditional polling based databases, this is not possible without using caches.
right now, hydra is in a state of bugfixing and preparing a stable release. if you decide to stick with mongodb, it might be good to wait for some fixes to land, so you have less work!
best
--
You received this message because you are subscribed to the Google Groups "ory-hydra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ory-hydra+...@googlegroups.com.
To post to this group, send email to ory-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ory-hydra/fcc3bd7c-2e67-45d8-af4c-4a55a72a493e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "ory-hydra" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ory-hydra/9a6l8iQGak4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ory-hydra+...@googlegroups.com.
To post to this group, send email to ory-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ory-hydra/6686396b-975f-450b-a3e2-af12e6520a2f%40googlegroups.com.
gorethink is the concrete adapter for connecting to rethinkdb. the abstraction is in hydra, e.g. here:
https://github.com/ory-am/hydra/blob/master/client/manager.go
usually all storage interfaces are called manager.go
You received this message because you are subscribed to the Google Groups "ory-hydra" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ory-hydra+...@googlegroups.com.
To post to this group, send email to ory-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ory-hydra/CACXNKutoeTwZt04PA-xTHO98CmQCorTasaeNO_OuuTXA4dLfJQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ory-hydra/0440c736-4d51-57ec-19aa-7b60c9d4576f%40serlo.org.
if you keep data in memory you need a mutex lock, because http
handlers (who access the manager) are called in parallel
If you don't keep data in memory, you don't need a mutex :)
No it's not mandatory, but it saves network roundtrips and
reduces latency significantly. depending on your use case, this
might be important. keep in mind that hydra might get hit often,
for example when validating access tokens.