When you change your code, how do you upgrade the underlying database in the way that you want and also fit into the new code? Some cases, it's not simple as add a new field, or rename a field. Takes for example: refactor a big project, etc.
Other stuffs should be of concern is permission based. For example: user A may see some items in the list, but user B see other items. Or some lists user A can see while user B cannot.
Validation and error handling?
Where is the configuration for database? I imagine in some hibernate configuration files. This is just an example, but are you prepared for growth senario that much more complicated project requires larger than linear effort? What I tried to say here is that if default is not good enough, or a function was not provided, a work around should be also very easy, and there must always be aworkaround for anything not supported. |
java.net RSS Feeds
