The solution could be more user-friendly. It comes with baggage so it should be simple to use. The PLS QL and the queries are efficient, but there isn't a major difference between the normal Java and Oracle Java DP. So, it should be a little more user-friendly and developer friendly. Additionally, handy release notes could be included in the next release because they will indicate the difference between the previous and the latest versions. For example, we couldn't find the use cases when we were doing the research. So whenever a search is done in the new DB, and we research Mongo or Cassandra, we get a lot of use cases from these communities. This solution is lacking because it's a giant, and everyone knows that most enterprise scales DBs are either used by Oracle products or in core banking. However, for Java DB, there should be more use cases, so it's easier for the developers and the users to pick and choose the right platform, application, domain, and how to utilize them.
