PgConf.Russia 2017

1. Why is it time to consider switching to PostgreSQL?
2. 1С and PostgreSQL interoperability.
3. Why should we start with Windows?
4. The first experience of migrating big enough 1С databases to Postgres.
5. Large-scale projects on high-load systems, in figures.

Do you test your PostgreSQL releases prior to Production in a dedicated test environment? Are you sure that your test environment (shortly Test) is equal to Production and in an appropriate state?

In Skype we were facing multiple challenges associated with database testing:
- Simplifying complex Production architecture of thousands of PostgreSQL instances, interconnected with RPCs and replications, infrastructure servers and external DB scripts, into their Test counterparts.
- Constantly growing hardware requirements, insufficient cleanup of data generated in Test.
- Differences between Test and Production were appearing and accumulating. Recognizing and fixing them required lots of effort.

Most of the main Skype services use a database platform based on PostgreSQL and other open-source technologies, such as Skytools, plProxy, pgBouncer, etc. This platform consists of several hundreds of servers with thousands of databases, which process hundreds of thousands of transactions per second. At the same time, the platform architecture allows its users (applications and their developers) to work with "logical" databases, without any worries about their real “physical” structure.

Our Skype Database Platform team is responsible for the database platform infrastructure. We develop automation systems for various processes that help us ensure service reliability and facilitate development, testing, and deployment of code. In this presentation, I will outline the database platform architecture, review its main components, and tell you about the methods we use in our every-day work to ensure high availability, scalability, replication, fault tolerance, and more.

This talk is about migrating an electronic document management system from MS SQL to PostgreSQL 9.5 or higher as part of the import phaseout initiative. We will touch upon architecture specifics, as well as describe the problems we encountered when migrating T-SQL code to pgsql, and how we resolved them.

Learn more at https://pgconf.ru/news/94168

VIDEO