Oracle APEX (or Oracle Application Express) is an online low-code application builder that allows users to develop a database-drive application, customize the application's UI, and then give their users access to the application via URL. Oracle APEX includes a suite of pre-built productivity applications and examples, such as a Survey Builder, Bug Tracking, P-Track project management, etc
$0.32
OCPU per hour
PostgreSQL
Score 8.7 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
Oracle APEX has delivered a strong positive ROI by significantly reducing development time, lowering costs, and improving operational efficiency through automation and real-time reporting. While there are some limitations around frontend flexibility and DevOps, the overall …
Our company was preparing a comparison of Oracle APEX against other low-code technologies. The focus was primarily on Mendix and Microsoft Power Apps. As with any technology, each platform has its pros and cons. I would choose Oracle APEX because clients often already have an …
Oracle APEX and Oracle Visual Builder are both low-code development platforms within the Oracle ecosystem, but they serve different purposes. Oracle APEX is more suited for the people who are familiar with SQL, PLSQL. It provides rapid application development features based on …
Outsystem is better than any system but it is too expensive also and Oracle apex is better than Liferay. Although Oracle Apex is cost effective as compare to Liferay and provides more feature than Liferay. But liferay provide the feature to move the program from one server to …
If you are expert in SQL and PLSQL and use Oracle Database, then the best choice is Oracle Application Express. The functionality is already complete and very easy to use, so it's useless to find another tool if you are using Oracle. You don't use Oracle APEX only if: (1) you …
I did not evaluate any other Rapid Application Development tool. I wanted a quick and simple solution just for my personal use so I directly tried using APEX since I work with Oracle databases and have a good background on the SQL and PL/SQL languages. I am currently replacing …
I am an IT professional with a degree in computer science, decades of experience, have used multiple programming languages and development frameworks over the years. It is a more daunting time than ever to be an IT professional with more alternatives available now than ever …
Oracle Application Express isn't just a CMS or similar software. You have a metadata-driven data model and a very data-near architecture. It is intuitive to use and you are able to get an application up and running in no-time. Many existing components are allowing you to create …
They are from the same developer. So because of this, they both work very well. We probably do use PeopleSoft a little bit more as not every employee has access to the developer suite in Oracle Application Express.
Easy integration with other Oracle products and oracle database makes it a great fit. UI is clean and aesthetically pleasing compared to similar applications I have used.
Very well suited for data reporting. Auditing of data and reports stored in database can be checked from the browser or even on the phone. So, with Oracle APEX work can be done on the fly...
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
Based on our organization's experience, Oracle APEX is a versatile and powerful tool, but its suitability depends on specific business needs, technical requirements, and the nature of the application being developed. Scenarios where Oracle APEX fits well: Business Process Automation/Workflows Reporting and Dashboards for Data Analytics AI based systems such as Select AI Chatbots for data insights based on LLMs Native-like Mobile Applications using PWA feature of APEX Scenarios where Oracle APEX may be less appropriate: Very Complex and highly interactive applications Use cases based on a non-oracle Database
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
Perhaps is our problem, since we haven’t explored it deeply, but I think that a better portability to mobile devices would help the adoption of APEX.
Applications weren’t as light as we thought, and we had to move the APEX server to the same data center where our data base was running, due to performance issues. When we started, we supposed that that situation would not be an issue.
At least in Argentina and Brazil, you can not find as many programmers with experience in APEX as you can find with other technologies.
The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
I felt very comfortable using Oracle Application Express from the start. I designed my data model and quickly developed the basic CRUD pages for master tables. Then I designed the main functionality and was able to test and deploy it in a couple of days work. I will probably share the app with other members of the team and continue adding some features in the short term.
Oracle APEX has delivered a strong positive ROI by significantly reducing development time, lowering costs, and improving operational efficiency through automation and real-time reporting. While there are some limitations around frontend flexibility and DevOps, the overall business value—especially in data-driven enterprise applications—has been substantial.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Very active and knowledgeable community support includes quick and helpful responses from the Oracle employees on the product development team. I've never had to raise an official support request - everything is dealt with via forums and user groups - or via direct emails. The supposrt commuinty is one of the great things about Apex.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Using it on the cloud is really simple, the entire process of configuring and provisioning an Oracle Database takes only a few minutes (less than 10) and then Oracle APEX is already deployed on the database, so you just have to start using it. I would strongly recommend using APEX on Oracle Cloud Free Tier.
Our company was preparing a comparison of Oracle APEX against other low-code technologies. The focus was primarily on Mendix and Microsoft Power Apps. As with any technology, each platform has its pros and cons. I would choose Oracle APEX because clients often already have an Oracle database, but they don't always realize they can use it with Oracle APEX. This easily accessible platform is a great web-based interpretation of the database.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
There have been numerous cases where solution development using Oracle's "RAD Stack" (ORDS, RDBMS & APEX) has saved many ten's of thousands of dollars in cost that would have otherwise been incurred by following vendor recommendation and/or other alternatives.
Impact on overall business objectives has been completely positive: low cost of maintenance, seamless easy upgrades, reduced development time