Bad dancer...
Many of you read on the recent Estonian elections. And here's an interesting facts.
The Estonian government hired an IT vendor Helmes to create a system of operational data during the last Estonian parliamentary elections. They (Helmes) built a brand new system, and apparently didn't check her before the elections. It is not surprising that the system fell, and the statistics were submitted with delay on an hour.
Why am I writing about this? Because Helmes accuses PostgreSQL in the delay. It's like that the driver after getting into a car accident will blame the engine manufacturer, although he raced a red light. "If only the engine was a little stronger," complains Helmes, "we could have skipped the damn intersection even before the moment the other car will take off!"
Assuming that Google Translate is adequate in his translation, Helmes gave a truly bizarre explanation for the lack of testing:
"The only way to prevent this situation would have been pre-loading 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 a certain amount of pseudo-data."
In other words, Helmes never tested the system with a fully filled database. A 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 New Zealand) is much higher than the population of Estonia, and nobody in those places has not reported the failure of elections because of the performance issues. Hell, I saw the electoral system on the basis of SQLite, and they work fine because they were designed correctly.
The same Estonian Skype handles more than 6% in long distance calls in the world using PostgreSQL. It is about a billion transactions per day. Around the world, PostgreSQL maintains many systems that handle volumes of several Estonian elections... every hour, every day.
My advice to the Estonian government: fire Helmes. You do not need a company that is unable to fulfill the order, and then blames their tools.
If any of the readers know Estonian, please translate this message and share it with the people of Estonia.
(Also, I can hear the apologists MySQL are 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.)
Article based on information from habrahabr.ru
The Estonian government hired an IT vendor Helmes to create a system of operational data during the last Estonian parliamentary elections. They (Helmes) built a brand new system, and apparently didn't check her before the elections. It is not surprising that the system fell, and the statistics were submitted with delay on an hour.
Why am I writing about this? Because Helmes accuses PostgreSQL in the delay. It's like that the driver after getting into a car accident will blame the engine manufacturer, although he raced a red light. "If only the engine was a little stronger," complains Helmes, "we could have skipped the damn intersection even before the moment the other car will take off!"
Assuming that Google Translate is adequate in his translation, Helmes gave a truly bizarre explanation for the lack of testing:
"The only way to prevent this situation would have been pre-loading 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 a certain amount of pseudo-data."
In other words, Helmes never tested the system with a fully filled database. A 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 New Zealand) is much higher than the population of Estonia, and nobody in those places has not reported the failure of elections because of the performance issues. Hell, I saw the electoral system on the basis of SQLite, and they work fine because they were designed correctly.
The same Estonian Skype handles more than 6% in long distance calls in the world using PostgreSQL. It is about a billion transactions per day. Around the world, PostgreSQL maintains many systems that handle volumes of several Estonian elections... every hour, every day.
My advice to the Estonian government: fire Helmes. You do not need a company that is unable to fulfill the order, and then blames their tools.
If any of the readers know Estonian, please translate this message and share it with the people of Estonia.
(Also, I can hear the apologists MySQL are 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.)
Комментарии
Отправить комментарий