Oracle Java Cloud Service Reviews

I use the solution in my company to store and analyze data to increase performance and reduce costs. I am not the cloud specialist on my team, but I know just the basics.

The most valuable feature of the solution is that it is flexible in the work, more accessible, and you can make changes in the cloud. It is pretty easy to use. The security part of the tool is less strong. The product's flexibility compensates for the lack of strength in the area of security.

The security part of the tool is not so strong, making it an area I would like to see improved in the solution. When working with a cloud tool, it's never 100 percent secure and it is always something to take into account. I would like to be more comfortable working with it and feeling safer.

In the future, the tool can be made faster.

In the future, I would like to see maybe some AI features in the tool to help automate stuff. You need to be able to create your own models to help create some automated actions.

I have been using Oracle Java Cloud Service for less than two years. I am an end-user of the tool.

Stability-wise, I rate the solution an eight out of ten. The tool is always dependent on servers.

In terms of scalability, it helps if you want to add some stuff, and it is far more easy to work with, as you don't have to add any physical stuff to your project. Scalability-wise, I rate the solution a nine out of ten.

Around 600 people in my company use the tool.

If the company keeps growing, and if we need more users, we surely have to expand it.

The solution's technical support is helpful and responds quickly. As the tool has many users, you can always find answers to frequently asked questions on the internet if you are searching for a problem related to the tool. I rate the technical support a nine out of ten.

Positive

I only use Oracle Java Cloud Service.

The product's initial setup phase was quite stressful at first, but there were no problems to report.

The solution is deployed on a private cloud using AWS services.

The solution can be deployed quickly, and it takes around 20 to 40 minutes.

I have an idea of whether the tool has fetched any financial benefits. When the cloud-based Oracle system was being used, my company had to spend less money on infrastructure, so they saved money. Even after paying for licenses, my company ended up with more financial benefits using the tool. The tool has helped save 30 percent in the area of operational costs.

I did a comparative study on the pricing between Oracle and SAP S/4HANA, but it was related to databases and in the areas associated with the clouds. I can tell that Oracle is a little more expensive right now, but not much compared to SAP. Oracle's prices are very much dependent on the scale of the project and how many users are there. If you have a big project, you should be able to afford the tool, but it can still be a little expensive. I rate the tool's price a six or seven out of ten. My company has to go for a yearly subscription model. The tool offers a basic license, and you pay more for some features.

I am not sure why my company chose the tool in the beginning. It probably depends on the number of users and the good technical support the tool offers.

Three or four people outside the company manage the tool for our organization, and they solve all our problems with it.

There is a need to maintain the tool three times a year.

I recommend the tool to others.

The AI features in the tool are useful for some analytics and data analysis. I have a tool that is already automated and gives me reverts instantly, and I don't have to check everything by myself to make conclusions.

Given the security and the pricing, I rate the tool a seven and a half to eight out of ten.

I use the solution for some government-related purposes in Korea.

The product's high price is an area of concern where improvements are required.

I have been using Oracle Java Cloud Service for fifteen years.

I have contacted the solution's technical support. The solution's technical support is good. I have to raise a ticket with the support team to get an issue resolved. For global support, my organization needs to raise a ticket with Oracle's support team.

I rate the technical support a ten out of ten.

Positive

I am a project manager in my organization. The technical engineer takes care of the installation and setup process related to the product.

The solution is deployed on an on-premises model. In Korea, many government sites use Oracle Database. Nowadays, government sites operate on different cloud services like Azure, AWS, and Oracle Cloud. Oracle doesn't support AWS or Azure.

Oracle Java Cloud Service is an expensive product.

I would say I use the product for the type of applications for which I use it for JSP and React. From a popularity angle, I would say that most of the sites related to the Korean government use Java, along with React and Vue.

I believe that my company probably uses the product for backup purposes. In Korea, many government sites use a backup solution that helps with the recovery part. The solution provides backups like live backup, backup for Oracle, and file backup. The product acts as a total backup solution.

The tool allows my organization to encrypt certain data in the database, specifically in Oracle Database.

I rate the overall tool an eight out of ten.

I've used the product for backend development, where clients send requests to our system, and we generate responses using Java frameworks. I'm involved in the development process involving problem statements and making the necessary changes per the company's requirements.

It's a screen framework requiring us to write the necessary code. The framework supports auto-configuration. A lot of features are already there. It also incorporates annotations and includes packages that align with Java's new features. This makes it reliable and user-friendly to develop code, back-end engineering, or locate specific information such as addresses. It is relevant and easy.

There are issues with the application's development, including small glitches and errors. We're in the process of continuously fixing to address these issues, and once resolved, the application will be ready. I've worked on this internal system application, and I'll give you an example of our specific challenge. There was an issue involving a complex query where data was stored and retrieved from the database. 

The application also had a reporting component that wasn't generating reports or collecting the required information for Excel reports. To address this, I made changes to the query. I focused on the data format issue encountered in the implementation class. However, when implementing these changes under a specific thread, the application server showed an exception. I also made adjustments to resolve the issue.

I have been using this solution for the past two years.

If you clearly understand the mobility architecture of the microservice, dealing with this solution shouldn't be too hard. It all depends on your grasp of the concept and the architecture. 

We have several users for the solution. The process involves different levels, including functional heads, finance, and approval stages. After progressing through these levels, invoices are either approved or rejected based on accuracy. At the finance level, payment processing is handled. Additionally, reports are generated monthly and yearly, providing insights into the total number of invoices generated.

My company has a partnership with Oracle and has acquired licenses for this application. I'm not aware of the pricing details as that aspect is managed by other teams within our organization.

I rate the product a seven out of ten because there are ongoing efforts from various teams within the company working on this application. We're in the process of fixing numerous issues and implementing various modifications.

All custom web applications are developed as Enterprise Applications deployed to Oracle Cloud. I have worked with Java/JEE technologies for more than 18 years. Moving to Cloud has addressed a lot of major concerns related to performance, security, deployments, support.

We have adopted TOGAF architecture framework for more than five years, as agile teams have been working with continuous deployments and JIRA as our ALM tool. Moving to Oracle Cloud has addressed some of our major concerns with having to manage the infrastructure, which needs better scalability, integrated security, and better database access. Moving away from maintenance and support of most infrastructure, and to some extend the applications.

Cloud has provided:

• Cost savings
• Less maintenance
• More security
• Better database management
• Better deployments
• On Demand scalability

Integration with Oracle products is well-supported. The same should be provided for other products that are used in most organizations, like PeopleSoft, CA, etc. 

Our primary use cases include:

• deployment of the Java EE applications on a scalable cloud environment
• leveraging the built-in DevOps capability for managing the application lifecycle
• quick provisioning of environment (non-production), on an as-needed basis.

• Operational overhead and expenses have been reduced due to easy provisioning and decommissioning of dev/test environments.
• Application lifecycle management has become easier with built-in DevOps capabilities.

• Easy provisioning and scalability
• Seamless integration capabilities
• High-availability and ease of management

Since most of our applications are Oracle ADF based on WebCenter, supporting a complete lift and shift of such complex Java EE would help us become completely cloud-based for our web channels.

We have a Spring Framework-based web API application for a telco. This application communicates with company's ESB, it has its own Oracle Database, and runs on Oracle WebLogic Server.

We have dev, test, and production stages. Developers deploy their builds and if we need to scale the environment we can do it quickly. So before going to production, everything is ready.

• Fast deployment
• Easy configuration of the environment

It has been built on Java technology but requires more integration with other APIs and CI tools.

The primary use case for Oracle Java Cloud Service was to increase the productivity of developers and project managers by leveraging the agility of cloud.

The Oracle Java Cloud Service has enabled our developers to focus on what they do best: developing modern Java applications.

In addition, more projects that meet clients' expectations can be completed, increasing our revenues.

Speeds up delivery of projects, making for satisfied clients.

Customer service could be improved.

We are running different applications with different development technology on Oracle Java Cloud Service.

As for technologies, we are running both Oracle Forms applications and Oracle ADF applications on Oracle JCS. These applications are human resources management systems, accounting, portfolio management systems, and document management systems. All these systems are developed in-house and all of them are integrated with Oracle Documents Cloud Service in a way that the documents are linked to the database records and the user can access the document related to the transaction.

We are working in a "hot" region. Most Middle East countries have conflicts and wars. We are able to move from one country to another one, so this solution gives us availability. We can access our database and application any time, anywhere at no additional cost.

Backing up and recovery for my domain are very easy and fast. In addition, applying patches and undoing applied patches is effective and easy to do.

The product is satisfactory but we need more training on managing the machine itself. For example, how do we add more storage, how do we extend a specific portion? I would like to see videos illustrating some of the technical tasks that we often need to do.

The product is very good, fine-tuned, and stable. Support is available 24/7 and is really fast and effective. However, it is somewhat expensive, so I rate it at eight out of 10.

Demoing. Two CPUs, 16GB memory.

Demoing is always an expensive process, from procurement of hardware to installation of software. Now, it is easier, cheaper, and more elastic.

Self-provisioning, easy to choose from WebLogic 11g to 12c. Customer has different requirements and it is easy to provision and choose the version of WebLogic within minutes.

Integration with other Oracle/non-Oracle products.

My primary use case for OJCS includes Java EE applications and ADF web sites on Weblogic Server running on cloud. They have added advantage of high availability and cloud-level security. Further implementations of middleware integration can be accomplished using Oracle SOA CS or Integration Cloud Service.

The concerns of server failure and unplanned downtime have been notably reduced. The automated features of auto-purging in 12c helps clear disk space on a routine basis.

• Getting to choose the Virtual Machine configurations while setting up the server, which is an automated process.
• The ability to manage security and access the server from any location with complete security using SSH is perfect for performing crucial tasks, even while travelling.
• OJCS can seamlessly connect to other cloud offerings like Oracle Database Cloud Service, Oracle Developer Cloud Service, Oracle Storage Cloud Service, etc. 
• The auto-backup, incremental backup and restoration features can be invaluable for management.

Most of the features provided are well designed and implemented. I'd like to learn more about WebLogic Server for solutions to help identify and resolve stuck threads.