Azul Systems headquartered in Sunnyvale is exclusively focused on Java and the Java Virtual Machine (JVM). They build fully supported, standards-compliant runtimes that help enable Java-based businesses. Azul Platform Core (formerly Zulu Enterprise) subscribers get quarterly access to security-only updates (ideal for rapid deployment) plus standard quarterly updates that include security patches, bug fixes, and new features.
N/A
Kubernetes
Score 9.0 out of 10
N/A
Kubernetes is an open-source container cluster manager.
N/A
Pricing
Azul Platform Core
Kubernetes
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azul Platform Core
Kubernetes
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azul Platform Core
Kubernetes
Features
Azul Platform Core
Kubernetes
Container Management
Comparison of Container Management features of Product A and Product B
I would go for Azul Platform Core where someone needs secure JRE and JDK at a cheaper price where they can afford some CPU memory spikes. If you are highly concerned about the high availability of systems, or CPU memory usage, then, in my opinion, Azul Platform Core should be avoided. Also, considering what I believe to be their poor support, you might want to reconsider buying this subscription.
K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.
Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
We have had plenty of contact previously with the Azul Platform Core's support team. They provided us with ways of debugging our JVM crashes and upload data to a provided FTP server where their support employees could assist by reviewing our special cases. The help they provided has been invaluable in optimizing our JVM.
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
