BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Pentabarf//Schedule 0.3//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALDESC;VALUE=TEXT:Databases X-WR-CALNAME;VALUE=TEXT:Databases X-WR-TIMEZONE;VALUE=TEXT:Europe/Brussels BEGIN:VEVENT METHOD:PUBLISH UID:10803@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200201T180000 DTEND:20200201T185000 SUMMARY:AMENDMENT LumoSQL - Experiments with SQLite, LMDB and more DESCRIPTION:
LumoSQL is an experimental fork of SQLite, the embeddable database library founding everything from Android to iOS to Firefox. As a replacement for fopen(), SQLite is a good choice for singer-writer applications and disconnected, slow and small devices. Modern IoT and application use cases are increasingly multi-writer, fast, high-capacity and internet-connected, and LumoSQL aims to address these very different modern needs. LumoSQL initially aims to improving speed and reliability, by replacing the internal key-value store with LMDB, by updating and fixing a prototype from 2013, and allowing multiple storage backends. Next up we are designing the architecture for replacing the write-ahead log system (as used by all other open and closed source databases) with a single-level store, drawing on LMDB as an example of a single-level store in production at scale. Challenges so far involve code archeology, understanding and updating benchmarking, designing a system for keeping parity with upstream code changes, file format migration and identifying bugs in both SQLite and LMDB.
Please do join us in testing and improving at https://github.com/LumoSQL/LumoSQL .
In this talk we welcome questions and contributions. This conference has many SQLite users and developers. What do you want to see?
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Databases URL:https:/fosdem.org/2020/schedule/2020/schedule/event/lumosql/ LOCATION:K.1.105 (La Fontaine) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Dan Shearer":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9230@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T090000 DTEND:20200202T095000 SUMMARY:SECCOMP your PostgreSQL DESCRIPTION:SECCOMP ("SECure COMPuting with filters") is a Linux kernel syscall filtering mechanism which allows reduction of the kernel attack surface by preventing (or at least audit logging) normally unused syscalls. Recent security best-practices recommend, and certain highly security-conscious organizations are beginning to require, that SECCOMP be used to the extent possible. The major web browsers, container runtime engines, and systemd are all examples of software that already support SECCOMP.
This talk covers SECCOMP applied to PostgreSQL via 2 different methods -- namely top-down using systemd, and at the session level using a PostgreSQL extension called pgseccomp. The two methods will be explained and compared. We will also discuss how and why the two methods might be used in conjunction. Finally, a process to determine the list of expected/legitimate PostgreSQL kernel syscalls is described.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Databases URL:https:/fosdem.org/2020/schedule/2020/schedule/event/seccomp/ LOCATION:K.1.105 (La Fontaine) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Joe Conway":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9123@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T100000 DTEND:20200202T105000 SUMMARY:dqlite: High-availability SQLite DESCRIPTION:SQLite has proven extremely successful at providing applications with a powerful, portable and embeddable SQL engine that can handle most of their data storage needs.
Unfortunately, SQLite is neither replicating nor fault tolerant. These two features are however very important for the rising Edge/IoT market: dqlite delivers both of them.
dqlite is a C library which exposes a SQLite database over the network and replicates it using the Raft algorithm, with built-in automatic failover.
It allows to build and operate a fault-tolerant cluster of nodes each running an instance of the user application.
dqlite was created to support clustering in the LXD container management project, where it has been used for over a year. In this talk we will look at its design, implementation and various use cases.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Databases URL:https:/fosdem.org/2020/schedule/2020/schedule/event/dqlite/ LOCATION:K.1.105 (La Fontaine) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Free Ekanayaka":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9014@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T110000 DTEND:20200202T115000 SUMMARY:MySQL Goes to 8! DESCRIPTION:The latest and greatest version of MySQL is MySQL 8.
Currently the most used version of MySQL is MySQL 5.7. This talk will highlight what is new in MySQL 8.0 - a huge step forward for our users. MySQL 8.0 delivers significant improvements on all fronts, such as dramatically improved SQL, GIS, and JSON support. The talk will also cover the MySQL Document Store (MySQL = NoSQL + SQL) and MySQL InnoDB Cluster (HA out of the box) as well as MySQL Shell which ensures power, freedom, and flexibility for the Developer.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Databases URL:https:/fosdem.org/2020/schedule/2020/schedule/event/mysql8/ LOCATION:K.1.105 (La Fontaine) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Geir Høydalsvik":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:9174@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T120000 DTEND:20200202T125000 SUMMARY:SWIM - Protocol to Build a Cluster DESCRIPTION:SWIM - is a relatively new protocol to discover and monitor cluster nodes, to disseminate events and data between them. The protocol is extremely lightweight, decentralised, and its speed and load per node do not depend on cluster size.
The protocol solves several tasks at once. First - build and keep up to date topology of a cluster without explicit configuration. The task is quite intricate because:
According to the protocol, cluster nodes broadcast packets and send p2p ping requests. Broadcast helps to discover new nodes, p2p pings help to detect failure of a known node.
A second task - events dissemination in a cluster. Event is a node failure; UUID change; IP address update; new node appearance - anything that affects cluster state. Sometimes users define their own event types. When a node learns about an event, it needs to disseminate the event to other nodes. SWIM protocol describes an algorithm how to detect and disseminate events, and gives the following guarantees:
In the talk I tell about how SWIM works, how and with which essential improvements it was implemented, how to use SWIM, and what are the practical performance results.
Implementation is a part of Tarantool DBMS. Tarantool is the biggest Russian Open-Source DBMS. Tarantool currently goes toward better scalability, improvements in horizontal scaling, in cluster-wide calculations, and better cluster management. In scope of that roadmap SWIM protocol implementation was recently released.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Databases URL:https:/fosdem.org/2020/schedule/2020/schedule/event/swim/ LOCATION:K.1.105 (La Fontaine) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Vladislav Shpilevoy":invalid:nomail END:VEVENT END:VCALENDAR