3 ms·
Truth be told, the code quality of electronic banking is often rather questionable. Probably they developed a prototype without any bells and whistles (and with
by iSnow 12y ago
Truth be told, the code quality of electronic banking is often rather questionable. Probably they developed a prototype without any bells and whistles (and without proper guards against code injection, without support for distributed operation) and then were forced to use it as the base of the real product.
- th3iedkid 12y agoOne another reason for loads of standardization in JEE is with performance and scalability guarantees which are not provided by developers but by application container vendors. Writing an E-Banking application on JDBC is certainly possible , but do we write code to make performance guarantees,for transactional isolation,maintainability or do we only write code for the business we need to attend, this is the question that leads to JPA [or JEE] . JEE stack does involve a steeper learning curve but is a different one indeed!
- lukaseder 12y agoIt's just an E-Banking system, i.e. the UI for the core-banking system, which is still written in PL/SQL and Delphi. It has been working fine for many years with no differences between with or without J2EE.