Using Kubernetes for handling second screen experience of european tv show About us Thomas Hector Head of IT Operations Key Qualifications ● 12+ years’ experience with development and operations operations ● Automating everything ● Been handling Kubernetes clusters in production for 2 years Jan-Erik Revsbech CTO Key Qualifications ● 20+ year of experience in web-development & operation/hosting

AWS services such as adding /removing files in S3 bucket, updating Amazon DynamoDB tables, HTTP request from Amazon API Gateway etc. Audience This tutorial is designed for software programmers who .................................................................................... 64 Error Handling in NodeJS ..................................................................................... .................................................................................... 76 Error handling in Java for Lambda Function ...................................................................

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name

Protocol specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 7.2.1 Request header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 7.2.2 Connect . . . . only brief messages to the console each time a request is served. With this option, the web service prints much more de- tailed data about every request and the COM methods that those requests are mapped procedure call typically consists of two “message” being passed, where each message is a plain-text HTTP request with a standard HTTP header and a special XML document following. This XML document encodes the name