Users will expect reliability, safety, privacy, ease of use, scalability, and autonomy (ie, they work even when NOT connected to the public Internet). There are ma …

Who do you trust? What do you control? What are your dependencies? Reliability on the Internet is an adrenaline-fueled adventure, but we all want a good night sleep and working service sometimes. Adam Surk takes a closer look at some reliability nightmares and explains how they could be dealt with.

We often hear talks on scale and reliability, mostly based on personal experience and lessons learned. Avishai Ish-Shalom asks what mathematics tells us about reliability and scale. Can math help us scale our systems and companies? It turns out that failure models, probability, statistics, and other domains can help our analysis and provide useful insights

With Apache Kakfa 0.9, the community has introduced a number of features to make data streams secure. Jun Rao explains the motivation for making these changes, discusses the design of Kafka security, and demonstrates how to secure a Kafka cluster. Jun also covers common pitfalls in securing Kafka and talks about ongoing security work.

Building reliable, robust software is hard. It is even harder when we move from deterministic domains (such as balancing a checkbook) to uncertain domains (such as recognizing speech or objects in an image). The field of machine learning allows us to use data to build systems in these uncertain domains. Peter Norvig looks at techniques for achieving reliability (and some of the other -ilities).

Implementing site reliability (SRE) engineering doesn't have to be intimidating, and it isn't only for cloud-native organizations. Liz Fong-Jones and Dave Rensin share eight key lessons Google's customer reliability engineering team learned helping large enterprises adopt SRE as an operations engineering model.

Many companies adopt microservices to break down monoliths, but they soon uncover a hidden cost: How do you manage all these new interconnected things popping up? Michael Hamrah explains how to avoid creating Frankenstein's monster by understanding elements of a microservice platform. . .so you can sleep at night.

Quantopian integrates financial data from vendors around the globe. As the scope of its operations outgrew cron, the company turned to Apache Airflow, a distributed scheduler and task executor. James Meickle explains how in less than six months, Quantopian was able to rearchitect brittle crontabs into resilient, recoverable pipelines defined in code to which anyone could contribute.

Monitoring only sucks when the cost of maintenance scales proportionally with the size of the system being monitored. Recently, tools have emerged that assist with scaling out monitoring configurations sublinearly with the size of the system. Jamie Wilkinson explores time series-based alerting and offers practical examples that can be employed in your environment today.

Tim Kadlec and Patrick Meenan explain how the construction of websites and applications impacts performance as well as how to quickly debug and resolve performance issues. Tim and Patrick dive into how browsers work, how web pages are delivered, backend and frontend issues, optimizations, and techniques to get the best performance and provide hands-on experience for working on web performance.

Tim Kadlec and Patrick Meenan explain how the construction of websites and applications impacts performance as well as how to quickly debug and resolve performance issues. Tim and Patrick dive into how browsers work, how web pages are delivered, backend and frontend issues, optimizations, and techniques to get the best performance and provide hands-on experience for working on web performance.

DevOps brings proven benefits by automating the deployment pipeline. David Hayes explores the benefits DevOps brings beyond automation, explaining the importance of shared operational responsibility on organizational culture, why reliability means both systems and people, and how aggregating alerts helps to maintain situational awareness.

Erlang/OTP has for years been described as the secret sauce to writing scalable and available systems. However, Erlang alone will not perform any magic. Francesco Cesarini walks attendees through the topology patterns of modern distributed Erlang architectures, discussing the trade-offs in scalability and reliability, the actor model, the failure model, and the built-in distribution model.

Containers are considered ephemeral: they can be thrown away, updated, or redeployed. But what if you need persistence or, heaven forbid, you use a database? With some live hacking, Alvin Richards showcases the core Docker componentsMachine, Engine, Swarm, and Composealong with integration with Aerospike so you can deploy persistent database containers across multiple hosts and networks.

Recent advances in transports and frameworks have made it possible to deploy large-scale, low-latency bidirectional communication over HTTP without losing original benefits like scalability and safety. Wenbo Zhu offers an overview of the use cases for enabling bidirectional communication as well as a demo that runs a distributed, shared whiteboard application from a browser.

Many companies have created extremely powerful Hadoop use cases with highly valuable outcomes. The diverse adoption and application of Hadoop is producing an extremely robust ecosystem. However, teams often create silos around their Hadoop, forgetting some of the hard-learned lessons IT has gained over the years. Keith Manthey discusses one such often overlooked featuregovernance.

What if we have reached the point where open source can handle massively difficult streaming problems with enterprise-grade durability? Ilya Ganelin presents Capital Ones novel solution for real-time decisioning on Apache Apex. Ilya shows how Apex provides unique capabilities that ensure less than 2 ms latency in an enterprise-grade solution on Hadoop.