Building the protection system based on Postgres DBMS
Why would you need the domestic DBMS? 1. Because of law requirements: only domestic DBMSes are appropriate for data protection. 2. In terms of formalization: currently, it is impossible to purchase MS in Russia legally. 3. In terms of pricing: the licensing mechanism of foreign DBMS systems significantly increases the expenditures on protection. 4. In terms of performance: it depends on the optimization of information protection tools, which are currently developed for domestic DBMS systems (in order to reveal why you may refer to the first paragraph). 5. In terms of practice: by the end of last year we’ve finished transition to the domestic databases and everything works smoothly. What else does an information security officer need?
Слайды
ЧуриковВидео
Видео доступно участникам мероприятия, выполнившим вход в личный кабинет
Другие доклады
-
45 мин
Alfred Stolyarov ООО "Еваппс" (EvApps)How we switched Oracle for PostgreSQL for a client, before it became mainstream
The history of import substitution did not start last year after well-known events. Its launch dates back to 2014. It was from this year that state and near-state companies began to think of switching to the so called "recommended software". One of these companies approached us back in 2020 with a project to move from Oracle to PostgreSQL. This project was designed to solve the accumulated architectural problems (imperfect storage system for telemetry data, the DBMS itself worked inside a virtual machine), and optimize the use of disk space (make space in the main storage, debug saving archived data, ensure correct backup). Since the customer's system should have worked uninterrupted 24/7, it was necessary to switch from one DBMS to another "seamlessly" without downtime, with simultaneous operation of both to ensure step-by-step translation of subsystems and the ability to control the correctness of the data. And, of course, the work had to be completed as quickly as possible.
In the report we will discuss how we managed to solve this case.
-
45 мин
Vasiliy Puchkov ОООOdyssey of corporate-scale migration to PostgreSQL
- Scylla Charybdis of project management;
- Sirens of personal goals:
- Circe for IT professionals:
- Polyphemus of information security.
The tricky part of taking the journey in less than ten years.
-
45 мин
Василий Тимощенко ПКТБ-ЦЦТ ОАОExperience of migration a highly loaded system from DB2 for z/OS to PostgresPro in multimaster configuration
The developer shares his experience of migration a highly loaded system in the field of railway transport from IBM DB2 for z/OS to PostgresPro in a multimaster configuration. The main focus is on the nuances of working with a cluster operating in multimaster mode, what problems had to be faced and how to solve them.
-
22 мин
Igor Kosenkov Postgres ProfessionalCorosync-Pacemaker HA cluster. Work on mistakes
I will talk about the common mistakes when setting up a Corosync-Pacemaker failover cluster. Often these mistakes lead to fatal consequences, and, as a result, to the rejection of the chosen solution in favor of others. Would you like to get a recipe for the "right" cluster?