Azul Intelligence Cloud The Powerful Analytics Solution That Boosts DevOps Efficiency with Insights from Production Java Runtime Data from Any JVM  
Blog chevron_right Java

7 Reasons for Breaking Up with Oracle Java

Has your relationship with Oracle Java lost its sizzle? Oracle Java giving you the blues?

Trading in your honeymoon for big bills and heartaches? We understand. It’s not you, it’s them. Here are seven reasons many companies are ending the love affair they thought would last forever and breaking up with Oracle for good.

7 reasons for breaking up with Oracle Java
  1. Money issues. It’s one of the biggest sources of stress in any relationship. Oracle’s new employee-based pricing is divorced from Java consumption and business value. Make that divorce final.
  2. Communication. Long-term relationships require talking and listening from both sides. If you’re only hearing “Where’s the money,” and not “how can I better support you,” it’s time to get out.
  3. Priorities. What matters most to you? You want to use Java to innovate, have more security and stability, and provide a great customer experience. Find a partner who cares and is 100% focused on your Java needs.
  4. Independence. Hey, you have a life too. When Oracle comes around with its audits, demanding to see where all your Java instances are, that’s a red flag, honey.
  5. Power imbalance. You thought you had a relationship built on mutual respect and equality. Now you’re seeing Oracle as the self-interested entity your friends warned you about, demanding more for the same thing. Life is too short.
  6. Trust. Where’s your Java? How many employees do you have? I know you have contractors. You tell Oracle, “My business is *my* business!”
  7. Respect. So you use an older version of Java. So you use Java 6 or 7. You deserve r-e-s-p-e-c-t for whatever Java you use, including support and backported security updates and fixes.

More Java

70% less expensive typically than Oracle