Home

Awesome

Special infrastructure for web applications

hu en theories

This document is the result of several hundreds of real-life incidents. #SaaS

My policy on providing services is to use specialized service providers, not popular ones, never free ones.

WWW

🪨 The World Wide Web is part of the Internet, so we need to connect to the Internet and provide web services.

Infrastructure

Enterprise ready server provider

"Cloud" really means virtualization and server clusters. Many so-called cloud providers only virtualize a single physical server.

  1. Software defined and redundant network
  2. Software defined and redundant storage
  3. Software defined and redundant servers (CPU+memory) 👈🏻 this is very-very hard
  4. Thin, thus performant virtualization layer

OS, middleware, runtime

  1. Build on Debian GNU/Linux
  2. Know each software on your server; uninstall all unused
  3. Keep every file on your server under control (e.g. packages, git)
  4. Monitor the kernel, the filesystem and every server software with functional tests, not just "pings"

Middleware

The Web Application

Write as little code as it is possible. Build on well-tested packages and specialized providers.

Run production environments without humans. Every problem should be solvable with CI and anonymized staging environments.

💡 Recognize your tech debt when you are manually working on a production environment.

Only 1 Tech Debt Day per month can tip the scales from stress to joy.

Cooperating with providers, software authors

Your application depends on others!

Analyze your service providers

Know the software authors you depend on