Oracle used to charge us per physical core on our production nodes, with a discount for development and backup/spare.
Then suddenly they changed how it was licensed and our bill jumped up 4x (we're talking a six figure increase).
We negotiated it down somewhat (closer to a 2.5x increase as a "goodwill discount"), but since then have been quietly making changes to the code-base to make a future SQL Server migration easier. We have four years left in this contract, and we hope to be ready by then.
We're on Oracle at all because we used to use their application development suite (ADF, Forms, etc), but those all either got discontinued or turn so sour you don't want to be using them, so now Oracle DB is just a remnant.
Also curious, what made you decide not to use PostgreSQL (or EnterpriseDB if you need entreprise solution)? Was it a technical reason or are you more comfortable with MS solutions in general?
I am asking because I have mostly used MySQL (pre-Oracle) and now PostgreSQL, and have always wondered what made people choose either Oracle or SQL Server. I have met both in different jobs - I hate Oracle with passion because of their licensins shenanigans, and wasn't impressed by SQL Server (though that might be in part that I was using it with SharePoint, which was... something).
You can use this to get a very ballpark idea:
https://wintelguy.com/mssql-ent-licensing-calc.pl
From actual quotes at full price, we'd be paying around the same to Microsoft for SQL Server Enterprise than we were paying Oracle BEFORE the price hike/license changes. However that doesn't include discounts which most organizations running any Microsoft software at all would be eligible for.
So in other words: Almost always cheaper than Oracle Database. Varies between a little cheaper and substantially cheaper. Both companies are trying to drag you towards Cloud however, so there's deeper discounts there right now (it's a trap!).
> Also curious, what made you decide not to use PostgreSQL (or EnterpriseDB if you need entreprise solution)?
No one person decided. This is a large organization that moves slowly and is fairly conservative. Plus the costs of migration are high, if migration fails people in management will suffer (either to their career or just outright be transferred/fired).
So in other words "nobody gets fired for buying Microsoft" or w/e. It certainly doesn't hurt that it is much easier to hire/contract in SQL Server talent than PostgreSQL. Technical considerations play a part, but only up to the point where it has to have what we need.
> I am asking because I have mostly used MySQL (pre-Oracle) and now PostgreSQL, and have always wondered what made people choose either Oracle or SQL Server.
That's because you're considering what is best using logic, reason, and technical facts. In the enterprise space more often than not major companies just follow the crowd, with a handful of trailblazers setting the standard. Oracle and SQL Server are popular because they're already popular, in a fully circular way.
If I started a business tomorrow I'd use PostgreSQL. But if I was a C-level in an enterprise and my career is on the line, I am going to be sticking with SQL Server.
The alignment between product support and product builder is muddier for c-levels to follow.
Keep in mind that MSSQL enterprise comes with a lot of tools beyond just a RDBMS. That was always the hangup when I have tried to move companies from MSSQL to something like PG.
I built and managed a data warehouse/internal reporting system for a fairly large telecom. I used ~100 ETL packages built in SSIS to pull in data from systems all over the company, SSAS to process the data and SSRS to build reports. It worked pretty well at the time 10+ years ago.
If you license all the physical cores you can run as many copies of SQL Server as your infrastructure will allow.
If you want to run SQL Server as a partial part of a private cloud then licensing per virtual core could be a significant savings in some circumstances. This is because physical cores used for other things won't require a license.
This article has more info:
https://blogs.flexera.com/elo/2017/06/an-introduction-to-mic...
If anything, I've seen a lot of non-programmers disguised as Java programmers. Armies of them in enterprise teams. A truckload of expense for not much gain.
I'm not saying it's everywhere like that of course. I've met brilliant Java developers when I contracted for SAP.
So how do you deal with such a risk?
If I had to hire I'd search programmers of less popular languages -- and only 3-5 of them. These people tend to be insanely productive and have very good perspective and culture.
I guess the day has come to make use of this feature.
Oracle audits are basically just sales tactics to get you to buy their cloud services so they can turn around and pretend they're a leader in the cloud.
A bunch of their stuff phones home too.
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.)
Oregon sued and ended up settling ostensibly for $100 million, but in actuality, it was $60 million in "customer service" and $25 million in legal fees.
Obviously, Oregon's government is culpable as well, but it's another data point to suggest Oracle is a dodgy sales/legal company posing as an engineering company.
Oracle bought Sun in the first half of 2009, completing in 2010. They actually moved to release Java 7 pretty quickly after that, there was a flurry of activity - mostly meant to reassure the ecosystem about their commitment to the platform, I think. After Java 8, new additions like lambdas seemed to have somewhat rebooted the scene. The ecosystem looks more lively now than 10 years ago, in many ways. It’s definitely a better language to work with, it feels rather less “enterprise” than before.
The move to monetize the JDK is annoying but almost understandable as a compromise between the renewed push to evolve the JDK (with yearly releases) and Oracle’s inclination to spend as little as possible on support. They don’t care if some of that support activity ends up generating money for others (via alternative JDKs), they just don’t want to be on the hook for it.
I’m hardly a fan of Oracle (the cloud move is such a fraud), but to be honest I think their Java strategy does make sense. It certainly makes more sense than Sun’s.
I sometimes wonder how much would it take to buy back Java from Oracle. Basically to buy back the Trademark, TCK and the official stewardship. ( Although I have to admit they are doing a pretty good job so far with Java )
Problem is Java is open source , and companies like Google , Amazon , Redhat have their own JVM implementations... So it’s not so much an issue.
In fact it’s the opposite , having to acquire something as big as Java comes with huge responsabilities to maintain it and make it evolve.
Hence these days , Rust and Golang really got popular , it wouldn’t make sense for anyone to buy back Java...
Amazon got the gov cloud contract. Oracle's suing, but all they have is that someone jumped from the DoD to Amazon. https://www.nextgov.com/it-modernization/2019/02/pentagon-in...
Also, I've heard stories at other .gov datacenters where they're trying to phase out Oracle as fast as they can because they're tired of their crap. Like last time I checked Oracle DB charged based on the number of CPUs you _could_ be running on. So if you have a modern env that dynamically provisions across a datacenter, then they charge for all of the cores in your datacenter.