• Advanced Infrastructure as Code: Open Policy Agent and AWS CDK

    18:00 - Food 🍕 & drinks 🍺
    18:30 - Talk 1: Policy-based control for cloud native environments
    19:30 - Break
    19:45 - Talk 2: Codifying the cloud with the AWS CDK
    20:45 - Drinks and Snacks 🍻 🍷 🥤

    TALK 1: Policy-based control for cloud native environments - Lennard Eijsackers

    Teams in a DevOps organisation should be free to setup and manage the infrastructure for their services. One way to enable your teams is by allowing them to use Infrastructure as Code (IaC) tools to allow teams to declaratively define their infrastructure needs. Terraform for example is a great IaC tool. However, from a compliance and security perspective, you want to place certain guardrails in place. You want to ensure teams still follow all best practices. In this session I will introduce the Open Policy Agent and show how you can leverage it to validate Terraform plans in a continuous manner.

    TALK 2: Codifying the cloud with the AWS CDK - Sander Knape & Sven Rienstra

    There is a new kid on the Infrastructure as Code block! The AWS Cloud Development Kit (CDK) allows you to write Infrastructure as Code in Typescript, Python, Java or .NET and provision it through CloudFormation. Compared to traditional tools such as Terraform and Cloudformation, the CDK provides advantages such as easy code re-use, sane defaults, less glue-ing together resources and being able to use a programming language that you are familiar with. In this talk we'll discuss both the advantages as well as some disadvantages so that you can decide if the CDK is the right solution for you. We'll also give a live demo where we spin up some AWS resources using the CDK.

    Getting there:
    Skyworkz is located in the "Werkspoorkathedraal" - a huge building you can't miss. We are located in Studio N on the second floor. The entrance is left of the main entrance.
    We have ample free parking and are easily reachable via public transport.

  • From Monolith to Microservices & Concurrency models explained


    18:00 - Food 🍕 & drinks 🍺
    19:00 - Changing architecture in production while also migrating to the cloud
    20:15 - Three concurrency models that every developer should know about
    21:15 - Socializing with drinks 🍻 🍷 🥤


    TALK #1 - Changing architecture in production while also migrating to the cloud

    When your application is around long enough making changes to the core architecture is going to be inevitable. A complete rewrite of the application might sound tempting, but often isn't financially viable and might not actually solve the issue. The answer is to evolve your application's architecture.

    But how do you do this when your application is in production and you need to keep delivering value for the business? In this talk, Sven Rienstra is going to explore this subject using a case study. He'll show he migrated from a monolith to a microservices architecture and how the application was moved to the cloud simultaneously.

    TALK #2 - Three concurrency models that every cloud developer should know about.

    Concurrency is everywhere. All systems depend on concurrency. Many languages have built-in concurrency primitives, and we're used to using those. However, we are often looking for the best tool for the job. What if there's another concurrency model that fits better in a particular project?

    In this talk, presented by Mikhail Vaysman, we look at 3 models: Threads and Locks, Communicating Sequential Processes and Actors. I'll talk about each model and show you how you can write the same example using a particular model.

  • Kubernetes night: building and running your clusters

    Tractieweg 41


    18:00 Food & drinks
    19:00 Kubernetes from the ground up: through the looking glass of the Kubernetes internals
    20:15 Kubernetes cool! How do I see what's going on?
    21:15 Socializing with drinks 🍻 🍷 🥤

    Parking is free next to the office. Check out the image below for more information.


    #1 - Sander Knape - Skyworkz - Kubernetes from the ground up: through the looking glass of the Kubernetes internals

    Kubernetes has become the de-facto container orchestration solution. Given this popularity, many managed services have been introduced recently that remove the burden of operating a Kubernetes cluster.

    However, even when using a managed service it's important to understand the internals of your cluster. Without proper understanding of the different components involved in operating a Kubernetes cluster, debugging issues - and you will have issues - is impossible.

    The best way to learn Kubernetes? Building it from the ground up! During this hands-on session I will spin up a Kubernetes cluster in AWS on EC2. While I do this, I explain the different components that I configure and how these components integrate with each other.

    At the end of the presentation you will have a better understanding of how Kubernetes works under the hood. And you'll hopefully have gained the courage to build a cluster from scratch yourself.

    #2 - Lyle Henkeman - Skyworkz - Kubernetes cool! How do I see what's going on?

    Now that I have my pods and clusters running, how do I get insight into them? You can examine application performance in a Kubernetes cluster by examining the containers, pods, services, and the characteristics of the overall cluster.

    *Sidecars and DaemonSets: Battle of containerization logging patterns.
    *Sophisticated and powerful logging with K8s & Prometheus.

    At the end of this session you will be able to understand proactive Logging and monitoring, Cluster visibility and capacity planning, Trigger alerts and notification, Metric dashboards.