I am a research fellow at the university. We are updating the Software Architecture topic with the hope of being “modernized,” and look at some of the learning and co-learning issues that we discovered in the past semesters.
Students are encouraged to quickly prototype their architecture using Eclipse.
For perseverance, we sent students to HSqlDb.
In the last semester, we received significant feedback that it took a long time to record the data access level and compare with OO. This plumbing work can be better spent on more important things, such as scaling, punching, or executing more scenarios.
In the real world, I would choose ORM technology such as Hibernate, but the topic is too complex to teach another technology (and Hibernate is a massive one that learns for IMHO students).
So my questions to the SO community:
- Should we consider providing students with an object-oriented database (if they still exist)? It saves time on ORM and plumbing
- Should we stick to the RDBMS and tell students to flip their own ORM?
- Should we point students to a lightweight, simple ORM?
Remember that this is not the real world, but we would like to teach as much as possible the skills of the real world. ORM training is not as important as getting students to quickly prototype a system that meets the scenarios.
I am C # dev, but students are only familiar with Java when they enter the topic.