Support for alternative SQL engine providers

[mjaric]

Hi Guys,

Would be possible to add a layer where we could swap store providers? So instead of Postgrex, one could configure Tds or Mariaex.... I'm willing to contribute but I will need your guidance since I haven't scanned code yet.

Thanks

[slashdotdash]

@mjaric Making EventStore back-end agnostic has been mentioned a few times (e.g. #22).

The EventStore.Storage module would be the most suitable place to define a behaviour that could then be implemented by alternate storage providers. The existing modules in lib/event_store/storage are Postgres-specific and could be renamed appropriately (e.g. EventStore.Storage.Postgres).

[slashdotdash]

I would be interested to hear which alternative SQL databases people would like to use.

Please feel free to add a comment, or +1, to this issue to show your interest.

[fire]

Cockroachdb should be the easiest one and it mimicks postgresql.

[fpauser]

SQLite would be great.

[ronlobo]

YugaByteDB would be perfect.

[aschrijver]

Also fan of SQLite support. For a server app where that's used for lightweight uses and ability to swap to Postgres if the workload demands it.