EntityFramework should not be the only option for storage.

[HawpT]

I would love to use TickerQ as a replacement for an older cron system, but our team will not use a product that uses EF. It would be nice to have an interface that allows us to implement our own storage for Models. A simple get/create/update/delete would do.

[dogsteven]

I think it should be provide an ADO.NET provider because EF Core is only meaningful for persisting objects that participate in decision making. I don't want to see a SaveChanges(Async) call that persists both scheduling data and decision making data.