The most valuable feature of Oracle Linux is that it's a very stable product. It seems to be based on Red Hat. We waited for a few years before adopting it, but now that we've adopted it, it's been very stable for us. The license and adaptability of it is probably be the biggest selling point for us.
In this day and age, we'd be very cautious in terms of licensing, but with the Oracle Linux it's very clear how you license it, and also it's the flexibility of it. Sometimes we find with the Oracle licensing it's quite vague in some of the products. With this here, it was very, very, clear what we had to pay for it, and what we got, and also what we can get in the future.
Room for Improvement:
Oracle's products are quite expensive. The reason why they're expensive is probably the reason why we purchase them, in terms of the stability, and we know that even though we're paying heavily for the product, we can't afford to be going with other inferior products.
We want to run -- we do run -- a High Availability environment. The documentation in and around Oracle Linux and the hosting of WebLogic on Oracle Linux from a clustering point of view was, at best, average. We had to search for many, many articles and get MyOracle support involved to get to the point where we actually ended up with the High Availability solution that our business needed. Again, when they put these products on the market, their documentation needs to be an awful lot clearer about how you get to the places you want to be.
It's incredibly stable. We've had little to no issues with instability.
Before any major software releases or major changes to our infrastructure, everything is tested to a really, really high level. We would never actually go live with anything without being stable, but it took us longer than it should have to get there.
The reason why we went for Oracle Linux ahead of even Red Hat or, originally HP-UX, was because the product licensing was very, very, clear, whereas it was a little bit vague with the other products. In this day and age, there's very much a focus on cost, keeping the costs down, and spending wisely.
The initial setup was difficult. We wanted High Availability, and it was that part in particular that was giving us severe problems. It uses a repository to holder details between the High Availability instances, and we found that that was quite complicated to set up, and even now it's a little bit buggy.
It would have been difficult. We try to have high availability, and in particular the high availability part of it gave us severe problems. It uses what's known as a repository to hold details between your high availability instances, and we found that they're quite complicated to set up, and even now a little bit buggy.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
May 31 2016