Serverless architecture poses a new challenge to developers - COST. We will discuss ways to find and optimize your application cost in this session.

Serverless has changed the way we build software for the better. But it’s also a paradigm shift that challenges many of our pre-existing practices and habits, like how we test our code and how we monitor their health. In this session, Yan Cui will share many of the lessons he has learned from running serverless in production over the last five years. Including tips on testing, observability, and how to keep your AWS cost in check.

***Please note that the audio turns on at the 45 second mark*** How Lumigo Monitors Its Production Monitoring your production is challenging. Lumigo processes more than 1.5B Lambda invocations per month and digests 25TB of data monthly. Many things can go wrong. In this session, I will explain how Lumigo operates its production from tools to processes.

When bugs inevitably make their way into production firmware, defensive programming practices give you peace of mind that your devices will keep running despite issues occurring in the background. However, defensive programming can lead to more issues than it solves if not used carefully. Often the better approach to take is to use the practice of offensive programming, which will help surface issues more quickly and easily and help you iterate towards bug-free firmware and a better overall product experience.

## Follow Cribl

Welcome to Shipa's Office Hours.

## Follow Cribl

One of the greatest things about Apache Flink (and there are many!) is that it’s available in a variety of programming languages: from the low level APIs accessible in Java and Scala all the way to Python and SQL. The Flink SQL APIs offer very powerful SQL with many useful features and functions: spanning from the definition of time windows, late events or aggregations and also covering advanced topics like pattern detection via MATCH_RECOGNIZE.

New ICMAD bugs require immediate attention and patching for SAP systems The dust has not yet settled on the CVSSv3 10.0 score Log4j security vulnerability that hit in December 2021. Last week, a new group of three security vulnerabilities were published by SAP, which all relate to SAP’s Internet Communication Manager (ICM or ICMAD). Once again, one of these vulnerabilities has a CVSS v3.0 base score of 10/10. In contrast to Log4j, the latest threats only impact SAP customers, but they need immediate attention.

"CFEngine: The Agent Is In" is our monthly webinar series, where we show new features, teach best practices, and keep the community informed about everything CFEngine.