Re:Yandex.Mail's successful migration from Oracle to Postgre...
by niftich on Tuesday September 13, 2016 @12:58PM
(#12490122)
So, they say 'shop.oracle.com' was their 'main reason' for switching but that reads as a half-joke, half-serious riff on Oracle's famous ability to extract money from people; the other salient points I can find are:
- PL/SQL was harder to deploy than PL/pgSQL (as stated later)
- Only synchronous interface in Oracle's OCCI
- Problems with Oracle's development environments
- Not very responsive support from Oracle.
But the dev environment and support for Postgres are not talked about.
Also I can't quite figure out if "3x more hardware" is supposed to be a good thing on their last slide. It's possible that it's a good thing (if it's, say, we can replicate to more servers), but to me it doesn't read like one.
Re:Yandex.Mail's successful migration from Oracle to Postgre...
by postila on Tuesday September 13, 2016 @01:09PM
(#12490228)
Details were in the talk itself, watch the video https://www.youtube.com/watch?v=-SS4R1sFH3c. In particular, they mentioned how Tom Lane fixed a bug they found and did it just in 38 minutes.
Re:Yandex.Mail's successful migration from Oracle to Postgre...
by elmigranto on Tuesday September 13, 2016 @03:17PM
(#12491343)
> I can't quite figure out if "3x more hardware" is supposed to be a good thing
Initial architecture with 2 servers was set up that way to save money on Oracle per-core licensing. They wanted to add more, but that was too costly.
2. The other concern was Oracle's slow bugfixing and reaction to feedback.
So, this is a good case showing how a company can stop wasting millions of $ for proprietary software, joining Open Source community, contributing to it and taking benefits from tech collaboration with core developers of the product.