85 Container. 1 Entwickler.
85 Container, 24 Datenbanken, 232 Cron-Jobs — und ein Gründer Wenn ich jemandem sage, dass ich alleine arbeite, kommt meistens dieselbe Reaktion: Ungläubiges Staunen, gefolgt von der Frage, wie das funktionieren soll. Die ehrliche Antwort: Es funktioniert nicht trotz der Komplexität. Es funktioniert wegen ihr. Ich bin seit 14 Monaten dabei, ein System zu bauen, das die operative Arbeit übernimmt.…
85 containers, 24 databases, and 232 automated tasks are part of a complex system built by a single founder. After starting this project 14 months ago, the system has successfully completed 1,087 tasks with an 88% success rate. The founder emphasizes the importance of not automating everything, but rather automating the right things.
The key principle they discovered after many failures and rejected architectures is to focus on automating the most important tasks. The founder explains that they categorized their tasks into three categories: those that could be automated, those that required genuine effort, and those that were truly essential. The system relies on "Guard-Regels" to define clear boundaries for automated tasks, preventing unexpected actions.
The founder emphasizes that these rules must be unambiguous and resistant to interpretation. They also mention a concept called "Crystallization," where decisions made repeatedly become rules, configurations, and eventually part of the system itself. This approach eliminates the need for constant documentation. The founder also highlights the importance of a self-healing system, with three levels of escalation to handle failures.
The system aims to minimize the need for human intervention, with only minimal logging and alerts. Despite a 12% error rate, most of these incidents are situations where human intervention is necessary, serving as valuable learning opportunities for the system to improve.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.