171–180 of 471 posts
We've been working on migrating from Oracle to Postgres for a few years now. We are about 2 weeks from being finished. It is not for the faint of heart, but it is totally worth it. The documentation is much much better, performance is equivalent or better, the sql dialect is saner, etc. Other than moving the data itself (ora2pg was invaluable for this), rewriting the queries is what has taken the most amount of time.…
Amazon is considered a paragon of IT, so their expulsion of Oracle is a useful tool at the CIO/CTO level of "nobody ever got fired for IBM" level of reasoning.
Unfortunately, AWS is becoming the new IBM in that reasoning. Great that it took ten years to reach that level of agreement, now hybrid cloud needs to take over the grey haired CIO / CTO level.
Long live Postgresql!
Earlier quoted context omitted.
When they threaten you with lawsuits for using their software, and make their pricing completely opaque so you don’t really know what you owe (Comcast style), why would you knowingly choose that? Postgres is pretty darn good these days. I still love Java, but I won’t be surprised if that language becomes a business risk because of Oracle’s behavior in other spaces.
> Postgres Yes, maybe there will be built in automatic fail over in a few years so you don't have to hack it together using a bunch of scripts. Of course there's overlap in functionality and most companies should probably chose PG over Oracle. But PG is a joke in some areas like the above mentioned.
thanks microsoft !!
Earlier quoted context omitted.
How? Its an Open source implementation of the java vm which they don't own.
> which they don't own They do own it. They own the copyright on the source code (all of it - even if Google or Intel wrote it). They own the trademarks. They own the specifications.
At that point, someone else could attempt a hard fork. Same as what AWS did for Elastic search and MongoDB. The existing release code is still under open source license and so would allow for that. But whoever's attempts that fork, unlike Oracle, would not be allowed to change the license terms beyond what the current open source license allows.
And, someone could also choose to not re-use any code, and re-imement from scratch the spec, like what Google did for Android. That said... the open lawsuit against Google is still deciding of the legalities of that one.
Earlier quoted context omitted.
> My company for technical reasons can't switch to OpenJVM The OpenJDK (not 'OpenJVM', that's not a thing) is literally 100% the same build as Oracle JDK now. There can't be any technical reason.
It's the same now, but in previous versions there were important differences. Might be legacy code that's hard to make forward compatible.
And there are other concerted efforts to keep control from Oracle in releases and the validity of the JDK.
As long as a sufficiently large majority (and AWS is helping here a lot, admittedly) maintain such regimented discipline, the JDK will be ok.
Oracle mostly wanted it to sue google for billions. That suit is basically dead, and Oracle knows the JVM isn't worth any large scale revenue.
Is this not a case study that anyone can leave Oracle now, if an Amazon scale install can?
It is not. Amazon accomplished the task by building their own Oracle replacement. You have to be approximately as large as Amazon for that to be a realistic option. If you'd like to use the alternatives that Amazon built, you can, of course, migrate to Amazon Web Services. Though, if you dislike the vendor lock-in you're experiencing with Oracle, and are considering Amazon as a good place to flee to, you possibly hav…
Earlier quoted context omitted.
Oh man. I used to work at Amazon at a time when this Oracle deprecation was starting up. It's utterly non-trivial. It's not really "switching relational DBs", it's "rebuilding all of the legacy systems to not use relational DBs". Their scale had long since left the realm where it was reasonable to run everything on massive monolithic DBs, but the technical debt hadn't been paid down -- so they just kept putting more…
> but it's actually intended a giant middle-finger to Oracle When they were all cheering, I actually felt bad for Oracle for a nanosecond.
As someone who has never used or worked with Oracle DBs, can someone explain why migrating to another technology is so difficult? With all the database engines available, is there really not another one that can match Oracle without massive customizations?
In theory SQL is SQL, even more so if your App uses a layer of indirection like an ORM. If you don't use any Oracle specific features, procedures and similar, in theory you could just replace it. But that is not what happens. First problem is - majority of mature enterprise systems (which tend to use Oracle), are not designed in such a schoolbook way, so that's you first problem. Codebases are ugly and teams loose th…
In practise, you want to cheap out on paying for training, have your team do their job and learn an entirely new system to expert level at the same time, the "cool new tech" isn't and your team knows that you're trying to sell it as "cool" to pull a fast one on them because you think they're idiot children, and you won't even commit to using it for long enough to make it worth the bother of trying to learn before changing your mind or prioritising something else, and you're humming and hawing about investing in the tools to make the new tech work well because it's free software so why should it cost you any money?
Besides, you won't prioritise maintenance or design, so the codebase is a mess and people are incentivised towards panic-of-the-day fixes and don't-ever-ever-break-anything conservatism - their fault not yours, obviously, it can't be your fault, you don't even work with the tech (you just choose it by fiat).
The video feels like a big middle finger to Oracle. "stop oracle", and the URL https://aws.amazon.com/products/databases/freedom . Not that I'm complaining, Oracle deserves all the hate they get for their business practices. But associating AWS with "breaking free" is extremely ironic. It's just as much of a source for vendor lock in as Oracle. If you are not extremely careful/dedicated with your system design, you a…
RDS probably affords enough flexibility to get your data out, but Dynamo... that's a different story.
The developer carrying it out still using 2015 MBP