DevOps + Performance

Introduction

Continuous Integration is a software development practice where team members intergrate their work frequently and idea of this practice is to reduce integration problems and allow teams to develop cohesive software more rapidly. Cohesive software developmet needs tools to run automated builds.

Travis + Gulp

CI always excited me and while looking for good Opensoure CI tools for Drupal Projects, I wasn't able to find any. Some of the things which I wanted in the CI tools were

In early web development, there was only one place to do calculations and logic work: on the server, in advance. Then javascript gained popularity and offered a second option, allowing us to utilize the end user's machine to do additional work in the browser. With Edge Side Includes (ESI), a third possibility enters the scene, namely doing region specific and independently cacheable work on servers at the edge of your content delivery network.

Having trouble with performance? Come learn about accurately diagnosing problems with your Drupal application. This talk will cover everything you want in your toolbox: performance profiling, database query analysis, cache troubleshooting, logging for specific scenarios, and a survey of common missteps in building and operating Drupal sites. (Useful for developers of all skills levels.)

As a web application developer, there should be as little friction as possible setting up your dev environment to begin contributing code to a new project.  The more complex the application, the more there is to setup.  You can document the 20 steps to get started working on a project in a `README` file in your project root, but really, who wants to follow a list like this just to contribute code to your project:

Installation Instructions

Learn how the central IT organization at The University of Iowa maintains over 450 websites, in two models- a free “standard service” and a cost recovery “custom service” - with a small team using Symfony and Acquia Pipelines.

Slides: https://docs.google.com/presentation/d/19PYct0iNmqbYdVf76qBizF6jZQp-39j9...

HighWire Press hosts more than 2,000 sites. Tired of manually maintaining our sites, and with technical drupalers in high demand, we knew we had to move to a user-friendly UI-based system for maintaining, auditing, and managaing our fleet of Drupal sites. We looked at hosted solutions like Pantheon and AquiaCloud, but our reliance on backend services made these hosted solution untenable. We decided to build it ourselves. 

So you want to make your own Drupal 8 Distribution?

At the University of California, Davis, we are developing a distribution that will be used by over a thousand sites across campus. We're using Drupal 8 because we want to be on the bleeding edge of the best Web technology available!

With so many moving pieces, many of them new to Drupal 8, we have established a methodology for:

The promise of a blue-green deployment workflow is that you can more easily manage risk through high availability and a failover environment, but there are many moving parts to the process and it can seem daunting. We'll discuss the example blue-green workflows and how to integrate the process with Drupal deployments to reduce maintenance downtime, prevent the loss of data, and eliminate last minute surprises during the deployment.

Main topics:

If you are a solo developer, you might test on your local, merge to master, and then push to the live site (I'm not suggesting that workflow!). As your team grows and your project complexity increases, it makes sense to adjust your development workflow to handle working on lots of features in parallel, peer reviews, QA and automated testing, and keeping your "code publication pipeline" clear for emergencies.

There are many ways you can architect your workflow. We'll talk about: