Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

El Carro: Run Oracle Databases on Kubernetes

github.com

Post reply on HN
Print view View original

21–28 of 28 posts

Re: El Carro: Run Oracle Databases on Kubernetes

#21

Post by killingtime74 »

gravypod wrote: post #3
dijit wrote: post #2

Note: i never really considered putting oracle in kubernetes to be a technical problem; since you can pass a “raw” block device from a distributed block storage. I consider it to be a licensing nightmare as the normal oracle license means you’ll need to license every single vCPU on the cluster. The express edition used here has some relatively anaemic usage limits which you could brush up against very quickly: “Oracl…

I've never used Oracle and, given it's reputation, never will. Is there anything that it does better than other databases?

Suing it's users

Re: El Carro: Run Oracle Databases on Kubernetes

#23

Post by dijit »

hyperman1 wrote: post #12
zepolen wrote: post #11

Earlier quoted context omitted.

This is legit the biggest wtf I've read today, this is an over 20 year old enterprise db...

What's really weird is the Stockholm syndrome of the Oracle users: They are proud of these limitations. I've heard all of these: * Boolean: You don't really need it, just use 0/1 or Y/N (or J/N or O/N or whatever NLS equivalent of Y/N you want). You might have to implement a few different mappers for the same data type, so what? * Strings: Semantically, a null string and an empty string are the same. You should be gr…

Had a CTO before insisting on tinyints instead of bools because you can have "third behaviour modes".

I wish I remembered the logic behind that, but it was essentially akin to extending feature flags.

Re: El Carro: Run Oracle Databases on Kubernetes

#24

Post by orthoxerox »

hyperman1 wrote: post #12
zepolen wrote: post #11

Earlier quoted context omitted.

This is legit the biggest wtf I've read today, this is an over 20 year old enterprise db...

What's really weird is the Stockholm syndrome of the Oracle users: They are proud of these limitations. I've heard all of these: * Boolean: You don't really need it, just use 0/1 or Y/N (or J/N or O/N or whatever NLS equivalent of Y/N you want). You might have to implement a few different mappers for the same data type, so what? * Strings: Semantically, a null string and an empty string are the same. You should be gr…

There are better date/time data types in Oracle, and the implicit nullability of empty strings is great in practice, but these goddamn booleans annoy me to no end. You can use them in sprocs just fine, but a boolean column? No, that's too hard for Oracle to implement.

Re: El Carro: Run Oracle Databases on Kubernetes

#25

Post by salmo »

Oh my goodness, this is an awful idea. Oracle just runs hosted Exadata for OCI last I checked.

RAC requires shared block storage and L2 private network. Cloud SDNs and storage require gross hacks with horrible performance consequences. Even “modern” virtualization is painful, but can work.

Oracle isn’t going to fix all the bare-metal spaghetti assumptions in their clustered DB stack, and has been pretty clear about that.

This could be useful for throwaway dev/test environments. Or maybe for apps that aren’t performance intensive or critical that are in “maintenance mode” and folks want to lift-and-shift. But they’ll probably spend more time on that than fixing/replacing/retiring the app. And all will require smaller data sets than what I see with big company legacy systems.

And typically those systems are using Oracle to access data populated by another system, which makes me die a little inside.

Pretty clearly a play to get big companies into GCP contracts, more than anything real.

It’s to sell to execs who want to do the cool thing without paying to fix the old thing. ahem Thomas Kurian cough.

Re: El Carro: Run Oracle Databases on Kubernetes

#27

Post by [deleted] »

hyperman1 wrote: post #12
zepolen wrote: post #11

Earlier quoted context omitted.

This is legit the biggest wtf I've read today, this is an over 20 year old enterprise db...

What's really weird is the Stockholm syndrome of the Oracle users: They are proud of these limitations. I've heard all of these: * Boolean: You don't really need it, just use 0/1 or Y/N (or J/N or O/N or whatever NLS equivalent of Y/N you want). You might have to implement a few different mappers for the same data type, so what? * Strings: Semantically, a null string and an empty string are the same. You should be gr…

[deleted]
Post reply on HN