4 ms·
I've worked with a public company whose stack is Oracle services. Pretty much every company on that field is Oracle as well, that explains (to me) much of how i
by fernandopj 8y ago
I've worked with a public company whose stack is Oracle services. Pretty much every company on that field is Oracle as well, that explains (to me) much of how is Oracle's customer base: this field has been under Oracle & Java database->bus->services->cms since forever, why would one company start and not hire them to have access to the same features, be able to grap a few engineers, and skip "reiventing the wheel"?
What this company (and every other in that field) is doing: moving small, microservice-able tasks to AWS. Scale and costs are way cheaper. But it's a very long-term move: a couple of years pass and bam!, here's another Oracle multi-million extension contract they must pay to continue to have the lights on. But to the executive's perspective, this is just the cost of doing business in that field, it's the same for the competition. You could argue this is the same "no one ever got fired for hiring Microsoft/IBM" mentality.
Oracle stack is obsolete, but as a business they aren't, simply because it will still take a very long time until most companies reliant of their stack be able to move out without great risk to core business.
- tabtab 8y agoOracle blew a great opportunity. Internal CRUD apps developed by Oracle Forms worked pretty well, were quick to make, had a well-fitting CRUD-centric programming API, and did the job. Even though they were ugly and visually out of style, they made CRUD easy. Our Forms developers were about 4x more productive than our MVC devs. The MVC devs can put all kinds of fancy-dancy JavaScript widgets on pages that dazzle users, but they are always breaking. But then Oracle moved their Forms client to Java, creating all kinds of versioning headaches and security risks. They should have stuck with the dedicated stand-alone EXE Forms client: a kind of GUI browser. It was a very practical tool for in-house and specialty apps, but Oracle ruined it with Java.