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

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 the program together!

We present to your attention 11 candidates for participation:
')
Wings, legs and tails: MySQL's strengths and when PostgreSQL conquers the world
Alexey Kopytov
In our hybrid age, both developers and administrators often have to deal with many different DBMSs. Knowledge of the strengths and weaknesses of each product is becoming an increasingly important skill, but the information on these issues, which can be found online, has a number of problems: the rapid loss of relevance due to the constant and rapid development of popular DBMS, fragmentation, as well as bias and often the incompetence of the authors.

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

• cluster initialization
• adding and removing 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

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

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

MySQL 5.7 New Features
Dmitry Lenev
MySQL 5.7 is the most recent stable branch of the MySQL database. This report
It is devoted to the new functionality that appeared in this version.

PostgreSQL for application developers
Pavel Luzanov
What do application developers need to know about databases in general and PostgreSQL in particular? Might be the basics of SQL? And can everything rely on ORM?
The report is primarily addressed to developers and application architects, but will also be of interest to database administrators and all the "companions".

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

New data replication technologies 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, how to make a file server and so on, as well as innovations that await us in PostgreSQL 9.6. In the second half, we will discuss the issue of setting up auto-file for PostgreSQL — the pros and cons of the approach itself, a review of existing solutions to this problem, including those that have appeared recently, and which one should be chosen.

Review Tarantool DB
Vasily Soshnikov
I will tell about:

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

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

Why do you need 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: the usual EXPLAIN. The most publicized use of this extension is the visual EXPLAIN in MySQL Workbench. However, EXPLAIN FORMAT = JSON can do much more: it displays additional information about queries, which can help find a solution to complex performance problems.

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

Organizers of the developer community conference: 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 on June 17 in Skolkovo!