Why Oracle APEX Is Still One of the Most Underrated Tools for Enterprise Apps
from codexbuilder@programming.dev to programming@programming.dev on 31 Mar 08:02
https://programming.dev/post/48059361

I’ve noticed that Oracle APEX rarely comes up in developer discussions, especially compared to modern frameworks and cloud native stacks.

But in enterprise environments, it seems to handle data heavy applications, internal tools, and workflows surprisingly well, especially when paired with a solid database setup.

From what I’ve seen, it reduces a lot of the overhead you would normally have with full stack development while still being scalable if designed properly.

Curious to hear from others. Are people actually using APEX in production, or is it still considered niche?

#programming

threaded - newest

Gonzako@lemmy.world on 31 Mar 08:07 next collapse

Sorry mate I ain’t touching anything with oracle in its name

iamtherealwalrus@lemmy.world on 31 Mar 08:52 next collapse

Try not to get hired by any large company, otherwise you might find you need to change your mind.

Senal@programming.dev on 31 Mar 09:05 next collapse

The are plenty of large companies that don’t use oracle.

Gonzako@lemmy.world on 31 Mar 09:34 next collapse

My opinions will not change but i’d work on it for 200k a year

esc@piefed.social on 31 Mar 09:42 next collapse

I’ve worked in large companies that didn’t use anything oracle, also worked in one that used oracle db and that’s it, I think that oracle is pretty north america specific.

technocrit@lemmy.dbzer0.com on 31 Mar 15:13 collapse

My organization used Oracle when I started but eventually phased it out. Good move.

Nighed@feddit.uk on 31 Mar 15:04 collapse

Fine to continue using it if you have it, but you would have to be crazy to start using any of their stuff if starting from scratch!

talkingpumpkin@lemmy.world on 31 Mar 10:39 next collapse

License: Oracle Technical Network License (proprietary)

No, thanks

Phantaminum@lemmy.zip on 31 Mar 12:19 next collapse

Hey I use Apex on Salesforce, does that count in this context?

Apex is part of its native stack and it works good enough, I would say that it is mainly because their database is really solid as you said.

dantel@programming.dev on 31 Mar 13:57 collapse

I hate to admit it, but I do work with Oracle Apex quite a bit. 15 years of experience to be precise. I’ve created several big applications with it which are running in production right now.

And still, if I had the choice I’d avoid it like the plague. This is 100% vendor lock in with very little benefit.

The only reason I’m using it is because it was already in use when I came into the picture and there was some know how in the team already. But guess what, those people left and now I’m the only one who really knows what’s going on and has meaningful knowledge and experience in PLSQL, which you absolutely need if you want to create anything non trivial with Apex.

And of course finding people who actually know PLSQL at the level required to maintain those systems is very’hard. Who is going to learn an archaic procedural language which will only ever work within an Oracle database? Nobody within their right mind.

We tried introducing several rookies into this - all of them run away.

Another big reason to avoid it is that if you ever have the need to do something which is outside of what the generator accounts for, you will be fighting the framework constantly to still make it work and pray to the gods that no Apex update will break whatever you had to hack in.

There is really no reason any sane company should introduce this. It is not cheap. It is not easy outside of trivial things. The vendor lock in is huge.

Avoid!