Shared DB Access layer

[joshbooker]

Yes. This is a great idea.

Furthermore, the ability to create a separate 'server tier' for each datasource and then attach to that in another project (via swagger or OData) could be expanded so that relationships between separate datasources can be defined and enforced. Like mashup Customers from CRM with Salespersons in MSGraph and Tickets in ZenDesk.

Idea: optionally create server tier for non-SQL data sources

SQL data sources generate a .NET server tier to expose the database via OData. Non-SQL data sources do not generate the server tier. It would be nice to have the ability to optionally create a server tier for non-SQL data sources. This would allow a middle-tier where we could use partial methods to customize the CRUD methods like so: Thanks for listening