1 |
On Mon, Aug 1, 2016 at 3:16 AM, J. Roeleveld <joost@××××××××.org> wrote: |
2 |
> |
3 |
> Check the link posted by Douglas. |
4 |
> Ubers article has some misunderstandings about the architecture with |
5 |
> conclusions drawn that are, at least also, caused by their database design and |
6 |
> usage. |
7 |
|
8 |
I've read it. I don't think it actually alleges any misunderstandings |
9 |
about the Postgres architecture, but rather that it doesn't perform as |
10 |
well in Uber's design. I don't think it actually alleges that Uber's |
11 |
design is a bad one in any way. |
12 |
|
13 |
But, I'm certainly interested in anything else that develops here... |
14 |
|
15 |
> |
16 |
>> And of course almost any FOSS project could have a bug. I |
17 |
>> don't know if either project does the kind of regression testing to |
18 |
>> reliably detect this sort of issue. |
19 |
> |
20 |
> Not sure either, I do think PostgreSQL does a lot with regression tests. |
21 |
> |
22 |
|
23 |
Obviously they missed that bug. Of course, so did Uber in their |
24 |
internal testing. I've seen a DB bug in production (granted, only one |
25 |
so far) and they aren't pretty. A big issue for Uber is that their |
26 |
transaction rate and DB size is such that they really don't have a |
27 |
practical option of restoring backups. Obviously they'd do that in a |
28 |
complete disaster, but short of that they can't really afford to do |
29 |
so. By the time a backup is recorded it would be incredibly out of |
30 |
date. They have the same issue with the lack of online upgrades |
31 |
(which the responding article doesn't really talk about). They really |
32 |
need it to just work all the time. |
33 |
|
34 |
>> I'd think that it is more likely |
35 |
>> that the likes of Oracle would (for their flagship DB (not for MySQL), |
36 |
> |
37 |
> Never worked with Oracle (or other big software vendors), have you? :) |
38 |
|
39 |
Actually, I almost exclusively work with them. Some are better than |
40 |
others. I don't work directly with Oracle, but I can say that the two |
41 |
times I've worked with an Oracle consultant they've been worth their |
42 |
weight in gold, and cost about as much. The one was fixing some kind |
43 |
of RDB data corruption on a VAX that was easily a decade out of date |
44 |
at the time; I was shocked that they could find somebody who knew how |
45 |
to fix it. interestingly, it looks like they only abandoned RDB |
46 |
recently. |
47 |
|
48 |
They do tend to be a solution that involves throwing money at |
49 |
problems. My employer was having issues with a database from another |
50 |
big software vendor which I'm sure was the result of bad application |
51 |
design, but throwing Exadata at it did solve the problem, at an |
52 |
astonishing price. Neither my employer nor the big software provider |
53 |
in question is likely to attract top-notch DB talent (indeed, mine has |
54 |
steadily gotten rid of anybody who knows how to do anything in Oracle |
55 |
beyond creating schemas it seems, though I can only imagine how much |
56 |
they pay annually in their license fees; and yes, I'm sure 99.9% of |
57 |
what they use Oracle (or SQL Server) for would work just fine in |
58 |
Postgres). |
59 |
|
60 |
> |
61 |
> Only if you're a big (as in, spend a lot of money with them) customer. |
62 |
> |
63 |
|
64 |
So, we are that (and I think a few of our IT execs used to be Oracle |
65 |
employees, which I'm sure isn't hurting their business). I'll admit |
66 |
that Uber might not get the same attention. Seems like Oracle is the |
67 |
solution at work from everything to software that runs the entire |
68 |
company to software that hosts one table for 10 employees (well, when |
69 |
somebody notices and gets it out of Access). Well, unless it involves |
70 |
an MS-oriented dev or Sharepoint, in which case somebody inevitably |
71 |
wants it on SQL Server. I did mention that we're not a world-class IT |
72 |
shop, didn't I? |
73 |
|
74 |
-- |
75 |
Rich |