So, I took the Java web project . The application was written by another developer who now works in another company. Generally speaking, the application is simple, well thought out and fairly documented. The only problem is that the previous developer decided to create his own library of access to the database instead of using the popular structure. Over the years of his programming career, he has created an impressive infrastructure for accessing any database (something similar to lightweight Hiberbate).
Now I have no reason to throw away its code and replace the data layer with a more ordinary JPA layer, as the current code works very well (although it is tempting!). But I was wondering if a more traditional framework should be used with new features. The application stack is simple and I can easily hook in Hibernate or JPA. Thus, the old pages (with new corrections) will use the old structure, and the new page will use the new framework.
One of the drawbacks of this approach is that it can confuse a new developer. However, I can also continue to use the old structure, expanding / fixing it as needed. Like I said, it works!
source
share