Devops

Serverless computing allows you to build and run applications without provisioning, scale or manage any servers. The main benefits are: no server management, flexible scaling, automated high availability, flexible payment model/pay as you go.

So how does Drupal fit here? How can you transform the well know LAMP stack to be serverless?

After the session you will know the answers of these and several other questions:

MySQL replication has been common practice for years. But leveraging master/slave or master/master replication in order to achieve high availability still proves to be challenging:

Redis is an in-memory data structure store that can be used as a distributed cache, as a NoSQL database, and even as a message broker.

Unlike Memcached, which is considered its predecessor, Redis offers built-in master/slave replication.

In this presentation, we will have a look at this replication feature, and figure out how we can leverage this from a high availability point of view.

Questions we will answer:

You've tried to troubleshoot a problem using a remote debugger, a profiling tool, a tracer, various dd/dump/var_dump statements, but you're still stuck? This session will explore the various tools you can use from the server-side to troubleshoot PHP - or any other language.

Slides can be found at https://slides.com/legovaer/noops-lando

In a fast evolving digital world, your teams need evolve together with you. Is your development team still using XAMP for setting up a local environment? At the beginning of a project; do you still spend hours in order to get your DevOps flow ready? It's time for a change.

During this session I will cover following topics:

While drupal.org offers a great infrastructure to host modules sometimes you just want a little more. With the use of Travis CI it's easy to run all kinds of tasks to ensure you only release high quality code for the rest of the world to use. Allow pull requests for your module instead of working with patch files? Easy! In this session you will see how you can host your module basically anywhere but still have it available the way everyone expects. And yes, your commits can still be recognized by drupal.org when you take this approach.

Serverless does not mean there are no servers; those are only just hidden from you. Scale with ease without provisioning server and without paying for idle...is this for real? Yes it is! Can Drupal also be part of a serverless architecure? You bet! Can Drupal itself run serverles? Maybe... After this talk you will understand why serverless architecture is great and you will be excited to create your own serverless solutions to make your life easier. And last but not least...it's lot's of fun!