I'm looking to get some feedback on the best approach to designing a new system.
Basically our company like to keep all the business logic contained within the database(stored procedures), its always been like this and needs to stay the same. So we have been asked to come up with new layered applications using the latest .NET Core with VS2017 (MVC & WPF MVVM). The reason these 2 have been mentioned is that they are the best way forward in terms of web and windows based applications...do correct me if I'm wrong.
My question is...What would be the best way to design layers around keeping business logic in DB?
Having not used any of these technologies I'm looking to find good examples of how I can approach setting up layered architecture, based on our business needs.
Could we use EF7 using stored procedures or EF using LINQ? or just use plain old ADO.net without EF?
Could we still use layers like so with or without EF (Presentation Layer, Service Layer(API), Business Layer, Data Layer)? Either way any examples would be great.
And could both technologies both benefit using these layers -> Service Layer(API), Business Layer, Data Layer for reusability?
Any feedback most welcome and appreciated.