Oracle
Oracle technology in enterprise estates, where the interesting decisions are rarely technical and almost always about cost, licensing and the exit path.
Oracle
Oracle database and applications: performance, licensing and migration, without the sales framing.
Enterprise Architecture
How the parts of a business fit together, and how to change one without breaking the rest.
How we approach Oracle
The expensive question is almost never technical
Oracle decisions in large estates turn on licensing, contract position and audit exposure long before they turn on architecture. A design that is sound and a design that is affordable can be different designs, and the constraint usually arrives from procurement rather than engineering. Establish the licence position first, because it determines which options were ever real.
Getting off is a rewrite in disguise more often than it looks
The data moves. The stored procedures, the scheduler dependencies, the reporting built on vendor-specific behaviour and the integrations nobody documented do not. A migration scoped as a data copy and delivered as an application rewrite is the standard way these programmes overrun. Assess the dependencies before committing to a date, and price the rewrite if that is what it is.
Price the exit at the point of entry
The moment to work out what leaving costs is while you still have negotiating leverage, not three years later under audit. That figure informs the renewal, the architecture and how much vendor-specific capability is worth taking on. It is ordinary risk management and it is the step most commonly skipped.
Every page above is written to be used rather than skimmed, and each links back here and across to the others. Nothing on this page exists only to hold a keyword.
Other topics: Artificial Intelligence, Cloud, Cybersecurity, Enterprise Infrastructure, Data and Analytics.