Oracle Application Express (APEX) Reviews

The APEX database is based on a SaaS service. We use a distributor based in Malaysia for that. We integrate this with other Oracle technologies. To use Oracle Apex, you require a licence. We rely on our distributors for the service, and then we advise our end users and support them. Our clients invest in Oracle technology for their application platform. Still, the devil is in the detail with the contract, explaining how the new technology enhances their solution.

It is risky to move to a new staging instance or new solution, which may cause an issue. In Malaysia, we don't need to take any risks. It is a mostly new architecture. Our clients are mainly in government. 

Our clients use this solution continuously. It has a well-designed architecture and is a simple 3rd party application. Our clients really like the new version. It does not need to be maintained very often. 

It has been reported that the technology is tough to learn, and the service is expensive. The online supporting documentation could be better and offered in other languages, as Malaysian does not seem to be covered. Oracle could improve server and data migration from the cloud. This is achieved easier via a hybrid version. Sometimes we perform migrations and have to roll them back, as there are unforeseen issues.

We have been using APEX since 2020. It's a cloud service, with a cloud structure.

Oracle is stable, as it is a data container, and it includes advanced framework development.

We have considered Azure Cloud, Oracle Cloud, Google GCP and Microsoft Azure. Oracle has value in that they have related products. We have been looking at products to standardise, and hence is why we chose Oracle as a uniform solution.

The implementation for clients is the responsibility of the distributor or reseller. The consultants must go directly to the users to understand their requirements. Implementation is usually carried out on-premise.

Pricing is expensive overall on an enterprise system, but we consider that it gives corresponding value to the product. It becomes more expensive when more products are added to the main product. The Apex element itself is free to use, so it's useful for learning individually.

I would rate Apex 10 out of 10.

The only feature which is useful is that it makes it easier to quickly create publicly accessible applications. We were using it to make these applications.  

We used it in addition to Forms and Report Services because Forms and Report Services at that time were client-server applications. It used to be an addition to the Oracle development environment.  

Right now I am working on two projects. One of them is using Oracle Forms and APEX.  

The valuable feature is the basic use case: it makes the process of creating publicly accessible applications easier.  

The first thing I can think of that needs to be improved with this product is that there is a problem with security. In all of the applications I saw, they stored the passwords in the configuration files. I think this is a big issue. The security module is supposed to be included in the APEX connection component, but people connect to the Oracle HTTP Server and the password goes to the HTTP server. It is using the HTTP server for the security part. We did some analysis and we figured out that we had to move to another product.  

Because security is not satisfactory, we created our own connection mechanism in ORDS. It was a better way to keep the passwords encrypted and to make access to the APEX applications a little bit more secure. But the way APEX causes applications to store the security information is a big issue and a security vulnerability. ORDS is pretty straightforward and Oracle WebLogic Server is very flexible and a very nice feature.  

Also, the Oracle application page is supposed to be able to cancel access to the application. From what we found, this is not done properly. The connection is hanging and sometimes different people who connect to the application use the same ID. This can seriously interfere with users who are already connected. These are both very bad security issues.  

There is also a disadvantage in that it is pretty hard to fix bugs in APEX. It is very tricky. Basically, the Oracle objects generate the HTML code and cast it to the HTTP server. You have to be very careful with the HTTP Syntax for the sake of compatibility. Some browsers accept the code that gets generated and some browsers not. It is very hard to debug these coding issues.  

We have been using Oracle Application Express (APEX) since 2015.  

Applications are usually accessible by thousands of users at a time without stability issues.  

You can use multiple servers and the scalability of APEX is really pretty good from an end-user standpoint.  

I do not think there is really much of a limitation on how many people can use the generated applications. This is one thing it is good at.  

I used to work with other Oracle products like Fusion Middleware, Forms, and Reports. Since 2016, I worked less with APEX because there are other solutions that I prefer. My experience with APEX is that it is a little limited right now. Because of that we actually moved most application development to ORDS (Oracle REST [Representational State Transfer] Data Services).  

ORDS is more efficient and easier to use. APEX is compatible with ORDS as well. The problem with APEX is mostly that I do not like to use different vendors for HTTP server and Oracle WebLogic Server. ORDS is supposed to be more of a native, all-in-one solution. So we try to use ORDS for development projects because Oracle HTTP Server is not supported anymore by Oracle and this is a problem for APEX security. You have to use a Tomcat server or something else with APEX.  

I worked with APEX to do the initial setup and I have never set up the environment fully on my own. It is complex enough that I do not think I would want to do it without their help.  

APEX is a pretty old application and a pretty old environment. Most people are usually trying to get rid of it rather than bringing it onboard. For anyone still considering it, I strongly suggest going to the cloud application because the general strategy of Oracle Corporation is to support applications on the cloud. There are multiple other solutions to consider from Oracle or other vendors as well.  

On a scale of one to ten where one is the worst and ten is the best, I would rate Oracle Application Express depending on the task. For some tasks, it is just perfect. You can say it would be an eight or nine-out-of-ten for quickly creating an application that does not need strong security. But for some tasks, like when you try enhancing an application, the score is pretty low. In that case, I would give the product a three or a four.  

I used this to deploy some web pages. It did not have a difficult or complex architecture.

Oracle APEX allows our company to complete webpage projects easily in a fast turnaround time.

Oracle's simplicity is the most valuable aspect. You are able to deploy simple websites that have several pages easily. Minimal consideration is required for design. You can just make a few configurations and your website is ready to use. It is as quick as making the coffee.

Occasionally when trying to un a page, I would be faced with an error number; however, not much information would be provided on the error itself outside of the programming language. It would be nice if more information could be provided.

I have been using this solution for two months.

Due to sanctions, many users in Iran are not able to access support. For those who can, it is not an easy process.

Before the Oracle APEX, we used the traditional tool or write your web page by PHP, HTML, etc. And as a database, we used to use MySQL, Cassandra, and other options. I don't know why the company decided to use Oracle APEX.

As a programmer, the setup was very easy. I do not know what the setup looks like for database administrators.

I do not think this would be an ideal option for a small sized company or a startup when considering the salary requirements for Oracle DBA'a and developers.

Oracle APEX would be great for a big company and with a strong client base where project web pages are needed as soon as possible. The product reduces the time to market for your product and you can write websites by different configurations.

Overall, I would rate the product an eight out of ten.

Our primary use is to develop secure applications for the Oracle Database. It is like an administrator for data processing functions.

This product allows us to manage our data processing using simple screens.

The most valuable feature is the ease of use.

The user interface is not complex.

Workflow capabilities should be added.

Better connection and integration with non-Oracle databases is needed.

I have been using Oracle APEX for the past four to five years.

We have not had a problem where it has crashed. However, it may be that our application is not complex enough.

We have approximately eight people using Oracle APEX. At this point, we are trying to reduce our usage.

I have not personally been in contact with technical support.

We did use another similar product before implementing APEX.

The initial setup is not very complex. Our deployment took four or five months.

A consultant assisted us with implementation and deployment.

We are currently in the process of migrating from APEX to Microsoft PowerApps.

My advice for anybody who is implementing APEX is to use the default parameters and do not do anything that is customized.

I would rate this solution an eight out of ten.

The valuable feature is simplicity. It is easy to learn and implement.

I would like to see more flexibility and productivity.

We have been using this for two years.

There were no issues with deployment.

There were no issues with stability.

There were no issues with scalability.

The most valuable feature is how fast you can do applications compared to other frameworks, like Java and PHP. It will take you three times longer to do what you can do in Apex. You don’t have to cut through a lot of layers to get to the data in your database with Apex.

From a cost perspective, you can use less resources to build applications. Time to market is another improvement, because you can make applications very quickly. We used to create a NBC project with another framework and write our own modules to access the data, but Apex gives you access to data in your database in a more straightforward way.

From a technical perspective, Apex is not yet well received from developers because they think it is not mature. From my experience, I think it is just like any other NBC framework that is out there. The approach is a little bit different, and it is a different part line, but you can still achieve the same stuff.

There are some improvements that could make Apex more robust as well, like integration with third party frameworks in order to have more components. They give you a stock of components that are enough to create a range of applications, but if you need more complex features or are creating something for end users or commercial users you have to build your own. However, being able to create your own features is another advantage.

I’ve never had to open a ticket. I’m familiar with web technologies so sometimes when I find an issue I just know how to resolve it myself, but the Oracle forums are very responsive and used by a large community of people. It is a strong environment, particularly because not everyone can submit a ticket since you need an account with access to the ticketing system in order to have Oracle look into an issue for you.

Apex is already installed in your database, so you kill a lot of steps in that. If Oracle Database is already installed, you pretty much just need to execute one line of code and you will be up and running. It is very straightforward.

If you are looking for performance and speed for your application, I would choose Apex. I would rate it a seven out of ten.

Apex is part of your database. Everything, program logic included, is happening directly where data is, so it's fast, it's centralized and it's easy to use. It's declarative.

Apex can help you centralize many things. You can replace spreadsheets that are being sent back and forth with Apex, for example. It increases efficiencies and reduces man-hours.

Apex runs in a browser, so using the latest technology, like push notifications, would be good. It could also have better connections and better reporting in terms of getting files out of it. It could create a PDF rather than just showing data on the screen.

This is definitely a tool that is stable, and you can use it even in point zero versions.

It simply scales with the database. There are absolutely no problems with scalability.

It is a really straightforward deployment. You just run a script and then copy a directory of files to a server. It's probably the easiest tool that Oracle provides.

I wouldn’t recommend an official training by Oracle. They are too long and expensive; however, there is tons of information on the web, many books, and a lot of third party trainers that run reduced versions of the introductory seminars. Apex even provides a two-day tutorial that I think is pretty good. It shows you the basic concepts like how to use the tool and what is available.

The most valuable feature is how fast you can do applications compared to other frameworks, like Java and PHP. It will take you three times longer to do what you can do in APEX. You don’t have to cut through a lot of layers to get to the data in your database with APEX.

From a cost perspective, you can use less resources to build applications. Time to market is another improvement, because you can make applications very quickly. We used to create a project with another framework and write our own modules to access the data, but APEX gives you access to data in your database in a more straightforward way.

From a technical perspective, APEX is not yet well received from developers because they think it is not mature. From my experience, I think it is just like any other framework that is out there. The approach is a little bit different, and it is a different part line, but you can still achieve the same stuff.

There are some improvements that could make APEX more robust as well, like integration with third party frameworks in order to have more components. They give you a stock of components that are enough to create a range of applications, but if you need more complex features or are creating something for end users or commercial users you have to build your own. However, being able to create your own features is another advantage.

I’ve never had to open a ticket. I’m familiar with web technologies so sometimes when I find an issue I just know how to resolve it myself, but the Oracle forums are very responsive and used by a large community of people. It is a strong environment, particularly because not everyone can submit a ticket since you need an account with access to the ticketing system in order to have Oracle look into an issue for you.

APEX is already installed in your database, so you kill a lot of steps in that. If Oracle Database is already installed, you pretty much just need to execute one line of code and you will be up and running. It is very straightforward.

If you are looking for performance and speed for your application, I would choose APEX. I would rate it a seven out of ten.