We would like to apologise for the problems users reported today when they wanted to order and purchase tickets for our conference.

Even though we had prepared everything on our side and tested everything thoroughly, unexpected situations lead to unforeseen results.

A new platform and necessary changes for GDPR in the purchasing flow caused untested scenarios which lead to a delayed availability of the shop with payment issues as a result. We’re working closely with our team to solve reported issues swiftly and ensure everyone receives their tickets.

As a precaution we have temporarily closed the ticket sales for our sponsors and speakers. The early bird ticket sales will be available for ticket purchase according to availability of tickets. The early bird period will last until December 5 or when all our tutorial tickets have been sold (whichever comes first). Only then regular ticket sales will be available for combo tickets (tutorial and conference) and for regular conference only tickets.

These are the available workshops given on Friday morning 25th January (in no particular order).

A coffee/tea break will be held halfway through and after the workshop you can enjoy delicious lunch in the main hall which is included in the workshop ticket. Please do register at the reception at least 15 minutes before the workshop starts.

In this workshop we will take a look at common security failings from a new perspective: that of the hacker. You’ll be provided with a set of different sites each exhibiting a different security flaw, the challenge will be to find and exploit it and in doing so learn how to protect your own sites.

All the sites will be run locally inside docker containers so don’t worry about breaking any laws! Obviously this means that you will need to bring a laptop which is capable of running docker containers in order to participate in this workshop.

Kubernetes, the flagship project from the Cloud Native Foundation, has become the de facto standard for running our container workloads.

Unfortunately, Kubernetes is a fast moving, ever evolving, sea of complexity. From Pods to Deployments, ConfigMaps to Secrets, and PersistantVolumeClaims to StatefulSets; this workshop will get you on-course.

In this workshop, David will walk you through a series of labs that will teach you everything you need to know to take your container based application and deploy it as a self-healing, redundant and resilient application on top of Kubernetes.

Let’s set sail.

Other Information

David is an active contributor and advocate of Docker, Kubernetes, and Cloud Native communities.

He has run Kubernetes workshops locally in the UK and Europe for European Training companies

Automated testing is an incredibly useful tool for any developer. From emerging design with unit tests to preventing regression bugs with acceptance tests, getting a computer to run tests instead of testing manually is a huge step forward and saves vast amounts of time.

Where do you start with automated testing? It’s an intimidating topic and can be confusing to understand what all the techy speak means, let alone how you get going. But writing automated tests shouldn’t be difficult, and can and should be part of your daily workflow once you understand exactly what to test, and how to test it.

In this workshop, we’ll introduce WHY and HOW you can get started with unit and acceptance tests, and touch on integration testing. By the end of the workshop, you’ll understand how you can leverage automated testing in new and existing projects, and be ready to save time and energy when developing.

One of the challenges we face on a day-to-day basis is getting the right and correct information from our product owners or clients. This can be both frustrating and decremental to the velocity of your team. No one likes to work on features that when delivered someone says “well… that wasn’t exactly what I had in mind” But now we have Stickies! So many stickies! It’s a whirlpool of stickies, what is this madness?

In this interactive workshop, we will explore all the facets of Event Storming as a modelling technique to get a clear and precise mental model of how a feature is supposed to work, all using the power of stickies! As we go through the user story, we’ll explain the different types of stickies, why they matter, and show why EventStorming is such an effective format.

Everything starts to be an API today. Unlike web interfaces APIs can’t be tested manually, by hand. So there is no other option than writing automated tests. Codeception provides the best set of tools to test REST effectively: data checks, structure checks, deep integration with frameworks. Come to this tutorial to learn how to make stable APIs with tests. In this session we will cover:

Using REST module with PhpBrowser or a framework of choice

Testing data structures with JSONPath and JSONType

Authentication in tests

Managing test data

Extending Codeception to validate responses with JSONSchema or Swagger

Idea behind commands is to encapsulate all of the information needed for an action: making our domain less fragile and simple. Event pattern help us decouple code and make it easily extendable: without modifying user registration process we can easily add more features like send ‘welcome SMS’ or ‘notify support to check new user’.

Goal of this workshop will be to build a small app using commands and events and show you how nice and cool it is!

Web development is not just about delivering a response. It is also about writing good code. The state pattern will help you move complexity from being all over your code to one or more state machines. This workshop will introduce state machines, implement them, show how to identify uses of them and implement them in your Symfony application in an object oriented manner using the Symfony Workflow component.

Other Information

As participant you’ll do some actual work and thinking. This is not a workshop where you can just “listen in”

Everyone is very anxious to hear if they were selected for our 10th anniversary conference. Our CFP team is working hard to select the talks that will be given at the conference, but they have to make really hard choices and some of them are still in debate.

So we’re already contacting the already approved list of speakers to ensure that they can make it to our conference.

Meanwhile it will give us time to discuss about the remaining talks and speakers who will be contacted later this week.

Of course we can’t select all the people who have submitted one or more talks to our call for papers, so once we are sending out the remaining speakers we will also be sending out our “Dear John” letters to those who didn’t made it to our schedule.