Hi, I saw that, we are cleaning up the registry/user-manager APIs for C5 and re-writing some stuff. So I was wondering, if we can use JPA instead of writing our own SQL scripts and writing the DAOs and maintaing them in the platform. Having our own SQL scripts and the SQL in the code can be a bit messy and it can get complicated when supporting new databases and so on.
So, by simply using a JPA provider, we offload all these complexities of generating SQL for different types of database and all to the JPA implementation. And also, with this, we can also possibly support non-RDBMS data stores as well, like MongoDB, which is supported by EclipseLink and DataNucleus. I guess, the only concern with JPA would be any possible performance implications, but I guess now a days JPA implementations must be pretty optimised, and must be generating good SQL or maybe even better than our custom ones, where as, they can generate custom SQL per database type. And in the case of data stores such as MongoDB, we may want to check how transactions and all would work. So if possible, we can do a PoC and see how it can work out. Cheers, Anjana. -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
