Fri 11:45am to 12:15pm (7/21/23)

DDEV - centerpiece of your local development platform

mirom — Mon, 22 May 2023 21:07:52 +0000

DDEV - centerpiece of your local development platform

Room

HS1 (Ground level)

mirom Mon, 05/22/2023 - 23:07

Time Slot

Fri 11:45am to 12:15pm (7/21/23)

Session length

Short session - 25min, including Q&A

Audience

All Attendees

Session Category

DevOps & Quality Assurance

With the increasing number of technologies necessary to run your projects it’s important to make onboarding and switching of developers as efficient as possible. Docker is a huge help, but it also means an additional technology to master. That’s where DDEV comes for rescue.

DDEV is a Docker wrapper allowing you to run your services in containers without deep Docker knowledge. On top of that it provides you with an ecosystem of add-ons, hooks and scripts.

At Jobiqo we’re using DDEV to build our local development platform. In this session we will explain why we picked DDEV, we will showcase its features and how we’re leveraging it (not only) on localhost.

Speaker(s)

Miro Michalicka

DevOps Lead at Jobiqo

Speaker biography

Miro Michalicka is an experienced DevOps engineer based in Slovakia. For the past three years he has been working with Jobiqo with their DevOps team. In this position he extended his experiences of various local development platforms and helped to bootstrap Jobiqo's cloud hosting platform.

Session Keywords

DevOps

An introvert’s guide to open source communities

Shriaas — Mon, 22 May 2023 09:35:25 +0000

An introvert’s guide to open source communities

Room

HS4 (Ground level)

Shriaas Mon, 05/22/2023 - 11:35

Time Slot

Fri 11:45am to 12:15pm (7/21/23)

Session length

Short session - 25min, including Q&A

Audience

All Attendees

Session Category

Open Web & Community

Abstract: Open source is not just about code, it's also about community. In this session, I will share my personal story of how I discovered the world of open source and Drupal, and how I went from being an introvert to founding my voice in the global community and even landing my first job. I will also talk about how the Drupal community inspires me to contribute and give back, and how I mentor others to join the Drupal movement. We will discuss how easy it is to get involved in open-source communities, all you have to do is show up and be yourself.

Topics: In this session, I will talk about:
- How contributing back to the community helped me, an introvert, to open up and find myself.
- How I learned to communicate and collaborate, not only with my fellow contributors but also with the larger global community.
- How the Drupal community motivates me to be part of something bigger than myself, and how giving back to the community can be a joyful and rewarding experience
- How I got involved in multiple communities, including Drupal, ACM, and Meta Developer Circles through code and non-code contributions, and how I got scholarships to attend various events like Grace Hopper Celebration India and DrupalCon Europe 2021
- How I mentored college students and introduced them to the world of Drupal, and what challenges and opportunities I faced along the way
- How I plan to continue my journey of open source and Drupal, and what are my goals and aspirations for the future
- The power of showing up: how being present and consistent can help you build your reputation and network in the open source world

Speaker(s)

Aastha Shrivastava

Full Stack Developer at QED42

Speaker biography

Aastha Shrivastava is a Drupal developer with 6 years of experience in the open-source ecosystem. She has been actively involved in the Drupal and other open-source communities, attending and organizing various events and meetups. She has also contributed patches to Drupal core and modules, and shared her knowledge and insights at local events. She strongly believes in the open source philosophy and she is passionate about creating and collaborating on innovative solutions that benefit everyone.

Session Keywords

Being Human

Community

Contribution

Why we moved the database drivers to their own modules

daffie — Sat, 22 Apr 2023 09:51:10 +0000

Why we moved the database drivers to their own modules

Room

HS13 (2nd floor)

daffie Sat, 04/22/2023 - 11:51

Time Slot

Fri 11:45am to 12:15pm (7/21/23)

Session length

Short session - 25min, including Q&A

Audience

Intermediate

Session Category

Innovation & The future

In Drupal 9.4 the database drivers for MySQL, MariaDB, PostgreSQL and SQLite were moved to their own modules. This session is about why we did that and what we want to do next.

We had a number of problems with the old situation:

1. Having contributed modules with a database driver copy their driver files to the directory drupal_root/drivers is not very composer friendly.

2. The database driver classes are unfortunately not enough to make Drupal work for a specific database. All database drivers need to override things like (views and other) plugins and entity storage classes. Those overrides need to live in a module

3. Tests are not always the same for every database driver. Those overrides also need to live in a module.

4. The by Drupal core supported database drivers are the example for contributed database drivers. Just like the Drupal core module and themes are the example for the contributed module and themes.

5. Database drivers should be able to extend another database driver. Just like modules can do.

Having the by Drupal core supported database drivers in their own modules makes it possible to do:

A. Create a new database driver for MySQL that allows queries to be run asynchronously. For instance with multiple blocks on a page, the block data can be loaded in parallel from the database instead of synchronously. PHP 8.1 has added the Fibers functionality and that allows I/O and database queries to run asynchronously. The database driver for MySQLi allows Drupal to use asynchronous queries.

B. Store content entity data in a document format. Content entity data is now stored in multiple tables and with a high number of entities, getting entity data out of the database will become slow. When used in combination with authenticated users and a lot of content, will result in Drupal becoming slow. Storing content entity data in a document format will make it fast again. The only database that a the moment has enough functionality to make it work with Drupal is MongoDB.
Using caching is great, but has it limitations. If we make hard Drupal calls a lot faster, we can use Drupal without any caching or with a lot less. PHP is fast enough for this. Databases are fast too. Only storing data following the relational database rules makes will result in complicated queries for getting the data out of the database. Complicated queries with large amounts of data will result in a performance nightmare. That is why we are using so much caching with Drupal sites. For anonymous users this is not a problem, only with authenticated users is caching a lot of times not possible. The solution is to store content entity data in a document format. In that way we almost always can get the data out of the database with a simple query (and therefor a fast query). When all queries are simple queries, the resulting Drupal page call will be fast.

I have already build a database driver for MongoDB. The driver is in the form of a Drupal module and the project can be found here: https://gitlab.com/daffie/mongodb867. It is based on Drupal 8.6.7 it hacks Drupal core with a >1.5 MB patch file. This is totally not maintainable. To fix that problem I have started to work on Drupal core to make the MongoDB database driver module work without patching/hacking Drupal core.

I would like to end with a group discussion about what we want to do next. What does the group think. Do they have other/new ideas. Hopefully get other people involved in what is next. This can also happen after the official session.

Speaker(s)

David Bekker

Drupal developer at Finalist

Speaker biography

David Bekker

I am the main contributor in having the database drivers moved to their own modules, I am also the subsystem maintainer for the Database API and I have over 500 Drupal core commit credits.

Session Keywords