Bad dancer ...
Many of you have read about the latest Estonian elections. And here are the interesting facts.
The Estonian government has hired IT vendor Helmes to create a system for presenting operational data during the last Estonian parliamentary elections. They (Helmes) built a completely new system, and apparently did not check it on the eve of the elections. It is not surprising that the system fell, and the statistics were submitted with a delay of an hour.
Why am I writing about this? Because Helmes blames the PostgreSQL DBMS for the delay. It is like the driver, after getting into a car accident, will blame the engine manufacturer, although he himself rushed to the red light. “If only the engine was a bit more powerful,” complains Helmes, “we would have slipped through this damn intersection before the other cars started moving!”
Assuming that Google Translate is adequate in its translation, Helmes provided a truly bizarre explanation for the lack of testing:
')
“The only way to prevent this situation would be to preload data with the same amount of information as in the midst of elections. This is not normal, since the launch of the system should not depend on any amount of pseudo-data. ”
In other words, Helmes never tested a system with a fully populated database. Classic mistake beginners.
PostgreSQL currently serves elections in Argentina, New South Wales (Australia), New Zealand, and in several Brazilian states. The population of all these regions (well, maybe, except for New Zealand) significantly exceeds the population of Estonia, and no one in those places reported failure of the elections due to performance problems. Hell, I've seen SQLite-based election systems, and they work great because they were designed correctly.
The same Estonian Skype handles more than 6% of long-distance calls in the world using PostgreSQL. This is about a billion transactions per day. Around the world, PostgreSQL serves many systems that process volumes of several Estonian elections ... every hour, day after day.
My advice to the Estonian government: dismiss Helmes. You do not need a company that is unable to fulfill an order, and then blames its own tools for this.
If any reader knows Estonian, please translate this message and share it with the people of Estonia.
(In addition, I hear MySQL apologists laughing at us now. Now we know how it is, to be blamed because of the curvature of the hands of the users of the system.)
The Estonian government has hired IT vendor Helmes to create a system for presenting operational data during the last Estonian parliamentary elections. They (Helmes) built a completely new system, and apparently did not check it on the eve of the elections. It is not surprising that the system fell, and the statistics were submitted with a delay of an hour.
Why am I writing about this? Because Helmes blames the PostgreSQL DBMS for the delay. It is like the driver, after getting into a car accident, will blame the engine manufacturer, although he himself rushed to the red light. “If only the engine was a bit more powerful,” complains Helmes, “we would have slipped through this damn intersection before the other cars started moving!”
Assuming that Google Translate is adequate in its translation, Helmes provided a truly bizarre explanation for the lack of testing:
')
“The only way to prevent this situation would be to preload data with the same amount of information as in the midst of elections. This is not normal, since the launch of the system should not depend on any amount of pseudo-data. ”
In other words, Helmes never tested a system with a fully populated database. Classic mistake beginners.
PostgreSQL currently serves elections in Argentina, New South Wales (Australia), New Zealand, and in several Brazilian states. The population of all these regions (well, maybe, except for New Zealand) significantly exceeds the population of Estonia, and no one in those places reported failure of the elections due to performance problems. Hell, I've seen SQLite-based election systems, and they work great because they were designed correctly.
The same Estonian Skype handles more than 6% of long-distance calls in the world using PostgreSQL. This is about a billion transactions per day. Around the world, PostgreSQL serves many systems that process volumes of several Estonian elections ... every hour, day after day.
My advice to the Estonian government: dismiss Helmes. You do not need a company that is unable to fulfill an order, and then blames its own tools for this.
If any reader knows Estonian, please translate this message and share it with the people of Estonia.
(In addition, I hear MySQL apologists laughing at us now. Now we know how it is, to be blamed because of the curvature of the hands of the users of the system.)
Source: https://habr.com/ru/post/115264/
All Articles