If you were talking to someone whose organization is considering Oracle Java DB, what would you say?
How would you rate it and why? Any other tips or advice?
This is a fairly stable language, and it's been in the market for several years. In fact, it's been around since about 1995, when the concept of object orientation started. People should use it because it's clever. On a scale from one to ten, I would give Oracle Java DB a nine.
I would rate this solution a six out of ten.
I would rate it an eight out of ten. Not a ten because it's difficult to learn. It's easier for developers but as QA it's difficult to train and deliver. I'd prefer an automation tool that doesn't have as much coding.
We use the on-premises deployment model. I'd rate the solution ten out of ten. When we're interacting with the solution, it's usually other third-party software solutions that interact with Oracle DB. As far as our interaction, it's quite limited. We don't do much unless it's real queries. We use SQL, we use Oracle. There isn't much that we would need from the solution. We're getting the job done at the end of the day.
Please share with the community what you think needs improvement with Oracle Java DB.
What are its weaknesses? What would you like to see changed in a future version?