I'm also seeing big stodgy companies getting more comfortable with things like Postgres. It will take a while, but barring some big change, Oracle is headed down long term.
I'm also seeing big stodgy companies getting more comfortable with things like Postgres. It will take a while, but barring some big change, Oracle is headed down long term.
Competitors have gotten a lot better over the last 10 years. Oracle has mostly just raised pricing. It works for a while, but at the current path I don't see Oracle the company existing in 20 years.
So basically they have a shrinking value proposition and they are rising prices. ( Why does that sound so much like Apple, Now I am worried )
Using Apple Pay also makes so much sense for the consumer as it limits your CC data being at every retailer since Apple Pay tokenizes the sensitive information.
If you want to see where Apple is going, checkout the Apple Healthkit API:
https://developer.apple.com/documentation/healthkit/samples/...
While it is too soon to say that Apple will own the market, Apple is the only big tech company that has positioned itself for privacy and trust, giving it the best chance to own this market of the big four.
Not to mention that figuring out the connection strings is so miserably complicated that you basically need a trained expert to figure it out. The docs were worthless.
I think I can spin up an entire blank MySQL instance faster than I could connect to an existing Oracle database back then.
I think you missed the word "new" in there. Amazon finally is cutting ties with its Oracle DB this year. While I won't be surprised if AWS starts offering "migrate off Oracle" as a consulting service, Oracle was still the standard through the 2000s. I think they have built up so much negative goodwill though that no startup would ever consider using Oracle even if they gave the first five years away for free.
If AWS can offer a database that satisfies the Mongo API (DocumentDB), then why couldn't Amazon offer a database that satisfies the Oracle DB API, complete with automatic migration?
The day that happens is the day Oracle stock goes straight in the toilet.
Those things that make working on OracleDB today difficult is what made it so dependable for people with money in the last 20 years.
It also runs on a lot of architectures that today's software is not really running on anymore.
My understanding, and I’m not a lawyer so don’t consider this legal advice, is that you can’t copy a commercial api or it’s infringing on their intellectual property.
Oracle won the last round, Google asked the Supreme court to look at it in January. Guess we'll know some time soon.
I would have to think so many organizations have random scripts, etc. that the risk vs. reward still won still be high er than you think, especially when say the CTO of JPMorgan's job depends on "knowing Oracle."
Personally, I think IBM will likely crash and burn way before Oracle does.
Java is in a rather secure place right now. Everyone that chases the new shiny is long gone but it’s not yet at the point where it is difficult to hire for (e.g. COBOL).
So young buck comes to the CTO and says 'let's do a rewrite in Go' and the CTO says 'why in the world would I want to do that?' Then young buck says 'okay, what about just coding the new frobinator in Go?' CTO still says no, because then he’d have to hire Go programmers and Java programmers or at least waste time cross training. Young buck's less honest compadres have probably gone ahead and put Go into production here or there without permission, but I don’t think that’s a danger to Java.
What really changes this dynamic is when schools stop teaching Java.
Java is what you write in, if what you're selling isn't the code but some service that the code provides, and you aren't a startup, and you can afford a support team and want a lot of devs.
Go is what you write in when you're selling the thing you made directly, like say it's a DB engine, or you're a startup and want low effort support and only want a few devs.
Java makes maintaining a feature easy, and the programmers hired can be average and still be able to make something of acceptable quality, in an acceptable timeframe.
A startup rather wants to move fast. Java is harder to move fast at - but Go probably has that in spades. I do believe Go will not succeed in a large, beaurocratic place. And as a start up grow out to become more and more beaurocratic, the tech transitions with it.
Meanwhile there are lots of frameworks in the JVM world, some of them "heavy" with features, but if you want frameworks that are much smaller, github is overflowing with them.
Kotlin eliminates most of the boilerplate, leaving you with a slimline language, a powerful runtime and a wide choice of libraries. Go doesn't have much to compete with that.
+ or software engineering, etc.
So, basically, companies need to move from Oracle JDK 8 to OpenJDK 11. And pay Oracle until they are done. It's a fair amount of testing and verification for some big companies. Now that it's costing them license money, they'll do it.
Edit: And, of course, many will also be incented to move off Java altogether.
But the OpenJDK is the reference implementation and almost certainly has everything you need. The only reason to use OracleJDK is if you want to buy a support contract from oracle (NB there are companies, including very big ones, that will sell you a support contract for OpenJDK.)