Data and storage

Oracle Database

The database underneath a great deal of core enterprise infrastructure, with capabilities and a licensing model that both need to be taken seriously.

When we reach for it

Integration with the systems of record that already run on it. In most large organisations, the Oracle estate is a fact to work with rather than a decision to revisit.

When we would argue against it

We do not recommend it for new systems. Cost and lock-in are the reasons, and neither is controversial.

What it looks like in delivery

Reading from it safely, putting documented APIs in front of it, and taking load off it — usually by moving reporting somewhere else rather than by touching the system of record at all.

Where this appears on the site

Nothing on this site names it yet

We work in Oracle, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.

Working in Oracle?

Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.