Tag : tech-talk

Last week, Ben Hall came and talked to us about how Docker can be used, even within a Windows-hosted platform. This was really interesting, and has opened up a few lines of experimentation; thanks Ben!

Abstract

Container based deployments are rapidly becoming the de-facto standard for system deployments ranging from small wordpress sites to how Google deployment their clusters.

During this talk, Ben will discuss how you can architecture your applications for use with Docker and a container based deployment approach. Ben will introduce the current Container Patterns and approaches that are moving us towards a containerised future.

At the end, developers, testers and system administrators will understand the issues associated with this new way of thinking, how production environments need to change to support containers and the advantages they bring for maintainability across multiple environments and clusters.

Ben Hall

Ben is the founder of Ocelot Uproar, a company focused on building products loved by users. Ben’s worked as systems administrator, tester, software developer and launched several companies. Still finds the time to publish a book and speak at conferences. Ben enjoys looking for the next challenges to solve, usually over an occasional beer.

Ben recently launched Scrapbook (joinscrapbook.com), a hosted online environment for developers. Scrapbook helps break down the barriers to learning new technologies such as Docker & containers.

Recording

Tech talks at JUST EAT

This is one of the reciprocal tech talks that we arrange at JUST EAT. See full details here.

On 22nd September 2015, we were delighted to host Stefano Germani from TheTrainLine, who gave us a talk about building Anti Fragile systems.

The abstract is:

When building a software system the biggest problem we face is change. Requirements change, technologies change, traffic on our web application changes, everything changes and our software that was perfect just a moment ago, now is broken and no longer suitable for our purpose.

The usual solution to this problem is to ignore it or, even worse, to resist changes. So we end up with a requirement change that requires the system to be completely rewritten or with a spike of traffic that will collapse it.

Antifragile systems instead of fighting the change, embrace it. This is the story of the Trainline journey into the antifragile world.

This was the third in a series of reciprocal tech talks that we’re organising with companies that also have interesting things to say about shipping software. We’re always on the lookout for more speakers!