Cloud DB War: Autonomous Databases
blog.panoply.io
blog.panoply.io
Oracle is the living god of RDBMS and they should take advantage of that yet they don't. It has nothing to do with AI, ML, NN, or any other word du jour, just plain tables lightning fast.
that wont do it
Google, Microsoft and Amazon invest billions _per quarter_ in R&D.
It doesn't matter what you want. Humans are no longer the customers; we are now the products and the slaves of machines.
At least that's what the article makes it sound like.
--
I'm dreaming about building a relational language and by the way build a RDBMS on top of maybe sqlite. I think exist a lot of potential for a relational store with more flexibility
Think: with both in-memory and on-disk data storage, fixed schema (as normal) + dynamic (like JSON) + Flexible.
By flexible I mean to use Union Types and return mixed rows:
//A union of several schemas: Table Log = | Customer | Order | OrderLine
SELECT Log =
Customer(1,...). Customer(2,...) Order(1, ...) OrderLine(1, ...)
Also, maybe allow to directly acces indexes (so a index is just a KV store!), to allow logical log manipulation, etc.
In short, what about a relational-redis?
The problem is that using sqlite it also embed a functional query engine, when a simple data format requiere extra layers to make it work.
So even better is to have a sqlite-like engine that allow partial/streamable reading/writes.
Lol sounds like a great place to work.
Past a certain point, I'm not solving issues -- I'm creating them. On any horizon over a week, I'm better off sleeping, eating, exercising, etc than trying to smash every hour into working. Keeping my brain on a routine and properly nurtured is more productive than crazy hours, by a wide margin.
But I guess looking busy can be as important as results.
I don't want to apply a fix written at 3:14AM by a developer with sleep deprivation. That's the same as being proud that drunk developers fix the most critical bugs.
Example 1
---------
Me: "Create a new Customer Record"
DB: "Customer Entity doesn't exist, shall I create it?"
Me: "Yes"
DB: "Customer Entity created. What is the Name of your Record?"
Me: "Larry Ellison"
DB: "Customer, Larry Ellison created"
Example 2
---------
Me: "How many customers are there?"
DB: "There are 123 customers"
Example 3
---------
Me: "How many customers have accounts that are past due"
DB: "I did not understand past due"
Me: "How many customers have accounts where past due is true?"
DB: "There are 5 customers where account past due is true"
Me: "Send me an email of those customers"
DB: "Email has been sent"
One day AI will be smarter than a college degree, but it's a while off.
If you want a simple subset there's heaps of CRMs.
[1] http://oracle-help.com/articles/oracle-18c-future-database/
I know its hard to imagine, but it is true and most devops teams look to a shiny new tech they saw at a meet up than (like you said) fix 90s era technologies.
Nice database you got there, it'd be a shame if it couldn't grow. Eight figures later.
If ml can expect, select and plant my data closer to the end user then my core rdbms engine can grow, otherwise you're just moving pieces on the monopoly board. Fat pipes, willing victims and a little ingenuity can go a long way.
#18c sounds bold
Oracle is so late to the game its gonna take a miracle for them to make a dent in AWS
Eventually, that will drain off their customer base. If whatever the big 3 cloud providers are selling as a database is "good enough", then "better" won't be enough to keep Oracle's current position in the market.
I think later clouds have advantages and not just missing/worse features -- they got to design their architecture after seeing others try, and definitely learned some lessons.
This one might be longer, say 15 or 20 years...but it's coming.
If the price is good (and considering you would not have to pay for salaries as well) you would be a fool not to take it.
That's not Oracle's historical strong suit.