DevOps

Our Drupal 8 websites are true applications, often very complex ones.
More and more workload is delegated to external systems, usually microservices, that are used for many different tasks.
Architectures are always more distributed and fragmented.

To trace the lifecycle of a single request that origins in a client, passes throught all Drupal subsytems, reaches external (micro)services and comes back will become mandatory to track down problems and to optimize for performances. This is often time consuming and without the right tools may became very difficult.

CI/CD ara realy trendy and cool expressions but, in the end, everyone do the same: Jenkins + anything else. Have you thought about a solution on AWS with a deployment on EKS? There a lot of elements to build a CI/CD system on AWS in a serverless way - we use it as part of our solution in two big customers - and they are in love with this.

The idea is doing the session the most practical possible and building a castle in the cloud (not in the way that expression sounds ;-) ).

Drupal core provides interfaces and tools for interface translation. But how to combine these tools in a real project and how to deploy interface translations. At LimoenGroen we use a developer friendly approach for managing and deploying interface translations. I will share this approach, our successes and our pains. Demo's and code examples are included.

From this talk you will lean:

In this session I will conduct a beginner's Workshop on local development best practices and share with all participants some very useful tips to speed up your Drupal work.

There are many tools we could use, like DDEV, Launchpad, Lando, Acquia Dev Studio, Pygmy (Lagoon) or Docksal. We will go over the pros and cons of most of them and what tools are best for each situation. Next we will pick one and move to a hands on Drupal setup and development session.

For this workshop you will need your computer running Docker and access to install & run command line tools.

There are plenty of material for frontend developers / site builders on how to optimize web site performance: like minification, JS/CSS aggregation, image size optimization etc.\

This session focuses on the techniques that backend developers should keep in mind:

• Cache metadata
• Existence of reverse proxies and CDN
• Existence of client-side cache

Session will be based on (previously delivered on local Drupal event) https://valthebald.github.io/sessions/perf_be/

Building solutions on top of open source software saves time. But it comes with a cost as well. Keeping the codebase up to date, while fixing problems in custom code can be tedious and frustrating. One might even think that things would be so much simpler if we just forked it all, and kept bugfixes in-house. As your tailor made site goes from off the shelf modules, to a range of custom modules, the open source abandonment might be even more tempting. As you might understand from the title, I want to make the case about the opposite!

A year long story how we incorporated Lando in Drupal 7 and 8 projects and how it affected the efforts to keep websites up to date.