DevConf :: Storage - cast your vote for your favorite database until May 31 / DevConf Blog

There is a lot of competition for choosing a database in the Storage section of the DevConf 2016 program - only the best and most interesting reports should remain.

Voting will last until May 31, we will form a program together!

We present to your attention 11 candidates for participation:

Wings, legs and tails: the strengths of MySQL and when PostgreSQL will conquer the world
Alexey Kopytov
In our hybrid age, both developers and administrators often have to deal with many different DBMSs. Knowing the strengths and weaknesses of each product is becoming an increasingly important skill, but the information on these issues that can be found on the network has a number of problems: the rapid loss of relevance due to the constant and rapid development of popular DBMSs, fragmentation, as well as bias and often incompetence of authors.

Master replication in Tarantool
Konstantin Osipov
I'll tell you how it works and how to use the master replication in Tarantool:

• cluster initialization
• add and remove nodes
• conflict resolution
• disaster recovery
• condition monitoring.

Let's look at performance together.

MariaDB 10.1 - what's new
Sergey Petrunya The
report will be an overview of the new features of MariaDB 10.1 - the latest stable release of MariaDB. The most important of them: Optimistic

• concurrent replication
• Integration with Galera Cluster
• ANALYZE STATEMENT, EXPLAIN FORMAT = JSON, and other optimizer improvements
• Data encryption

Database evolution: from client server to mobile devices and vice versa
Vladimir Fedorkov
How are storage systems changing? Analysis of evolution and comparison of client-server and mobile platforms.
Let's talk about MySQL, MyRocks and SQLite. When to use what? When is MySQL not needed? What are the strengths and weaknesses of MyRocks and SQLite? Comparison of performance and differences of use from the point of view of the developer. Is it possible to assemble a cluster from a database for mobile applications?

New features of MySQL 5.7
Dmitry Lenev
MySQL 5.7 is the most recent stable branch of the MySQL DBMS. This report
focuses on the new features introduced in this version.

PostgreSQL for application developers
Pavel Luzanov
What do application developers need to know about databases in general and PostgreSQL in particular? Maybe the basics of SQL are enough? Or can you rely on ORM in everything?
The report is primarily addressed to developers and application architects, but it will also be of interest to database administrators and all those who participate.

MySQL performance: what's new?
Alexey Kopytov
MySQL 5.7 offers a huge number of performance improvements for almost all components: InnoDB, partitioning, backups, replication, DDL, and the query optimizer.
In this report, we will consider these optimizations in detail, and also talk about the problems that remain relevant so far, possible methods for solving them and planned further optimizations in MySQL 8.

New technologies for data replication in PostgreSQL
Alexander Alekseev
The first half of the report is devoted to the basics of replication in PostgreSQL - how synchronous replication differs from asynchronous replication, how to make a faylover and so on, as well as the innovations that await us in PostgreSQL 9.6. In the second half, we will consider the issue of setting up an auto-filer for PostgreSQL - the pros and cons of the approach itself, an overview of existing solutions to this problem, including those that appeared recently, and which one should you choose.

Review Tarantool DB
Vasily Soshnikov
I will tell about:

• real production user cases using Tarantool DB;
• about which libraries are used in place with Tarantool DB, and why they are needed;
• several architectural solutions;
• what kind of RPS to expect from these solutions.

Partitioning large tables in PostgreSQL
Ivan Frolov The
report is devoted to methods for partitioning tables in PostgreSQL and new developments in this area. Read more

Why EXPLAIN FORMAT = JSON?
Sveta Smirnova
EXPLAIN FORMAT = JSON was first introduced in 2012 in version 5.6, but it is still not used as widely as its predecessor: regular EXPLAIN. The most publicized use of this extension: Visual EXPLAIN in MySQL Workbench. However, EXPLAIN FORMAT = JSON can do much more: it displays additional information about the queries, which can help find a solution to complex performance problems.

Voting will last until May 31, your vote is important!

Developers community conference organizers:MoscowPython.ru , PHPClub.ru , RailsClub.ru , MoscowJs.ru ,

Partners in 2016 were: TASS, Badoo, Postgres Professional, ItSoft, Sesmik CMS

News and discounts on participation in our channel @devconf_ru in Telegram See you at DevConf 2016 June 17 in Skolkovo!