Oracle APEX vs PostgreSQL

• Easy upgrade path from Forms, allowing reuse of code and a low learning curve for Forms developers.
• Very quick to develop in. Ideal for prototyping or iterative development which is how we usually work.
• Comes with cross browser and mobile compatibility out of the box.
• Easy to incorporate other web technologies.
• Development environment runs straight from a browser. This has proved to be a life saver when issues crop up on a weekend.

Read full review

• As I mentioned before, Postgres has an incredibly flexible and simple-to-use user/role management system. First, there are users--login information so that you can hand out to individual users. Then, there are roles, which specify read and/or write access to all the tables that you can assign to users. Through this system, you can easily control who can read and update which tables, and the system is very well-tested, so there's no concern with users accessing or writing to data that they shouldn't be unless your Postgres admin really messes up!
• I could write pages on this and would need to reference the Postgres manual itself to do this justice, but Postgres is dang scalable! There are so many ways to scale it. Postgres has undergone active development by some of the brightest engineers for over 30 years now, and the result is that Postgres has so many ways you can scale it besides just upping the SSD and CPU and memory speed. You can scale reads horizontally through multiple slaves that handle all the reads. You can add highly optimized indices to your tables. You can change columns to JSONB types for super fast JSON queries. You can turn on special caches to bulk writes so they don't overwhelm the disk. Between those three options and other tips and tricks experienced Postgres admins have, you can get a lot out of them. There's a reason Yahoo stuck with Postgres for decades up until their main database even past the point of 4 Petabytes and 10k writes/second!
• Postgres, simply put, has achieved super-wide industry adoption (6% market share), which means it's really easy to integrate it into your stack and hire knowledgeable developers to service Postgres. All the major database libraries of the common web frameworks that I know are out there (e.g. Rails-ActiveRecord, Spring-Hibernate, Play Scala-Slick) have out-of-the-box deep Postgres support, with no extra configuration needed to get your web app to start reading and writing to Postgres. I also know many universities in the US include Postgres in their curriculum too (e.g. UC Berkeley). It's really easy to hire either new grads or experienced software engineers for positions that require Postgres knowledge.
• If you are comparing Postgres to MySQL and you want to use JSON, know that Postgres has better performance and features on indexing JSON blobs simply because Postgres beat MySQL to the JSON game by several years. I haven't used MySQL's JSON support before, but that's what my co-workers say (and it's true that Postgres definitely started support mySQL years earlier).

Read full review

• 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.

Read full review

• Deployment gets difficult for folks who are habituated with commercial databases.
• We cannot write our own database engine unlike MySQL.
• PostgreSQL do not allow us to execute batch of statement. we have to embed it in a function to achieve this.

Read full review

• In the mid-size organization, we had a BI tool that had a significant license cost involved. With Oracle back-end we were able to switch to APEX and move all reporting at literally zero cost.
• For Oracle PL/SQL users the learning curve is very quick and easy, there are ready templates that you can start with and eventually create complex reports.
• You can track authorization and authentication on data editing and usage. High performance as it is native oracle sql codes.
• Centralized data capturing, makes your datawarehouse writable for lookup tables or reference tables.

Read full review

• By pushing a lot of logic into database views and triggers, PostgreSQL provides the ability to write much slimmer and more maintainable controller code, reducing development costs.
• PostgreSQL's upsert capabilities enabled us to go to scale much more easily and quickly, allowing us to increase our number of customers.

Read full review