I'm beginning a small Web development project (maybe 20 tables initially). I would like to use a relational database for transactions, SQL, indexes, etc. I have limited needs for true objects, though.
Although the application will be written in an OO language (Java), most of the domain data work will consist of: 1. Parse JSON and/or HTTP requests from a client. 2. Write the data to the database 3. Answer queries about the data, by executing SQL commands and generating JSON and/or HTTP results.
The domain data won't really do much of anything: There would be little in the way of server-side (domain/persistent) objects collaborating to provide complex behavior. I'm wondering if there is not a principled way to define and work with the data objects that doesn't require turning them into Objects in the traditional OO sense, just so a mapper can turn them into tuples in a table.
My feeling is that if I wing it I will screw it up. I haven't used a non-OO language in ages.
Pointers to papers would be appreciated, as would pointers to tools in the Java space.