Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
I have a SQL database to which I store and from which I read several objects into my C++ code.
I wrote a single database wrapper which handles all the reads and writes to the DB.
Of course this class got too large. I could make a Database wrapper for each business object but then I have to instantiate all these different wrapper classes.
Since this seams like a pretty generic situation, I am wondering what's the text book way of wrapping a database?
You have to have the same amount of code, regardless whether it all lives in a single large class or several smaller classes!
An ORM can help you write this code, but if we're talking about organisation of higher level DB repository for your business objects, you don't have much choice. Its easy to create many classes to handle DB transactions between business objects though, group related schema elements together and create a class for each (eg one for Customers, one for Stock or whatever your system works with).
Once thing that is useful is to ability to split your business objects into horizontal slices and maintain them completely separately (ie a microservice architecture), so bearing this in mind might make the decision of which DB areas to split into smaller classes easier.
