I'm creating an application for users to create and manage their own data objects via a web app. I've done some exploring with the C# SMO class and have successfully create a web api with repo and UoW using entity framework. My main job is managing a data warehouse and building reporting solutions. Programming is more of a hobby for me.
I was hoping for some high level design suggestions to abstract the SMO part from the API. Or, alternatives if SMO is not an ideal class to use.
I tried to translate what i learned from my web api project to fit my needs, but i don't know how to implement it without db context.
Right now im thinking of having an api to access the admin tables that have meta data on the objects being created by users and then another api designed for the actual creation of those objects.
To be clear i have no problem getting this to work. I'm mainly looking for design suggestions to simplify maintenance down the road.
I guess simply I'm wondering how to properly implement a repository
pattern with SMO and the server connection. Or, if there is a better design pattern to consider.
Any advice would be gladly appreciated. Thank you
1
