| <!doctype html> |
| <html lang="de"> |
| <head> |
| <meta charset="utf-8"> |
| <meta name="viewport" content="width=device-width,initial-scale=1"> |
| <title>Software Architektur</title> |
| <meta name="description" content="Interaktive Referenz zu Softwarearchitektur: Monolith, Microservices, Events, APIs, Cloud Native, Daten, Security und AI Systems."> |
| <style> |
| :root{--bg:#f7f9fc;--card:#fff;--text:#152033;--muted:#64748b;--line:#dfe6ef;--a:#2563eb;--b:#4f46e5;--soft:#eef4ff} |
| *{box-sizing:border-box} |
| body{margin:0;font-family:Inter,ui-sans-serif,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",sans-serif;background:linear-gradient(180deg,#fbfdff,#f7f9fc);color:var(--text)} |
| .wrap{max-width:1160px;margin:auto;padding:40px 20px 70px} |
| .hero{background:linear-gradient(135deg,#fff,#f1f5ff);border:1px solid var(--line);border-radius:24px;padding:34px;box-shadow:0 14px 38px rgba(15,23,42,.06)} |
| .tag{display:inline-block;padding:7px 10px;border-radius:999px;background:var(--soft);color:var(--a);font-size:.78rem;font-weight:800;text-transform:uppercase;letter-spacing:.08em} |
| h1{font-size:clamp(2rem,5vw,3.8rem);line-height:1.02;letter-spacing:-.04em;margin:17px 0 12px} |
| .lead{font-size:1.06rem;line-height:1.65;color:var(--muted);max-width:830px} |
| .section-title{margin:34px 0 14px;font-size:1.35rem} |
| .stack{display:grid;gap:12px} |
| .layer{display:grid;grid-template-columns:230px 1fr;gap:18px;padding:18px;border:1px solid var(--line);background:#fff;border-radius:18px} |
| .layer h2{font-size:1rem;margin:0 0 6px} |
| .layer p{margin:0;color:var(--muted);font-size:.9rem} |
| .chips{display:flex;flex-wrap:wrap;gap:8px;align-content:start} |
| .chip{padding:8px 10px;border-radius:999px;background:var(--soft);color:#334155;font-size:.88rem;border:1px solid #dbe6ff} |
| .table-wrap{overflow-x:auto;background:#fff;border:1px solid var(--line);border-radius:18px} |
| table{width:100%;border-collapse:collapse;min-width:780px} |
| th,td{padding:15px 16px;text-align:left;border-bottom:1px solid var(--line);vertical-align:top} |
| th{font-size:.82rem;text-transform:uppercase;letter-spacing:.05em;color:var(--muted);background:#fbfdff} |
| td{font-size:.92rem;line-height:1.45} |
| td:first-child{font-weight:750} |
| .note{margin-top:18px;padding:16px 18px;border-left:4px solid var(--a);background:#f8fbff;border-radius:12px;color:#475569;line-height:1.55} |
| .footer{margin-top:34px;border-top:1px solid var(--line);padding-top:20px;color:var(--muted);font-size:.9rem} |
| .footer a{color:var(--a);text-decoration:none} |
| @media(max-width:720px){.layer{grid-template-columns:1fr}.wrap{padding:22px 14px 50px}.hero{padding:24px 20px}} |
| </style> |
| </head> |
| <body> |
| <main class="wrap"> |
| <section class="hero"> |
| <span class="tag">Softwareentwicklung · Architektur</span> |
| <h1>Wie moderne Softwaresysteme aufgebaut sind.</h1> |
| <p class="lead">Eine kompakte Referenz zu Architekturentscheidungen – von Anforderungen und Domänen über Monolithen, Microservices und Events bis zu Betrieb, Security und AI Systems.</p> |
| </section> |
|
|
| <h2 class="section-title">Architektur in 7 Ebenen</h2> |
| <section class="stack"> |
|
|
| <article class="layer"> |
| <div> |
| <h2>1. Anforderungen & Domäne</h2> |
| <p>Was soll das System leisten?</p> |
| </div> |
| <div class="chips"><span class="chip">Funktionale Anforderungen</span><span class="chip">Nichtfunktionale Anforderungen</span><span class="chip">Domain-Driven Design</span><span class="chip">Bounded Contexts</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>2. Architektur-Stil</h2> |
| <p>Wie wird das System grundlegend strukturiert?</p> |
| </div> |
| <div class="chips"><span class="chip">Monolith</span><span class="chip">Modularer Monolith</span><span class="chip">Microservices</span><span class="chip">Event-Driven Architecture</span><span class="chip">Serverless</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>3. Schnittstellen</h2> |
| <p>Wie kommunizieren Komponenten?</p> |
| </div> |
| <div class="chips"><span class="chip">REST</span><span class="chip">GraphQL</span><span class="chip">gRPC</span><span class="chip">Webhooks</span><span class="chip">Messaging & Events</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>4. Daten</h2> |
| <p>Wie werden Daten gespeichert und konsistent gehalten?</p> |
| </div> |
| <div class="chips"><span class="chip">Relationale Datenbanken</span><span class="chip">NoSQL</span><span class="chip">Caching</span><span class="chip">Transaktionen</span><span class="chip">Eventual Consistency</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>5. Plattform & Betrieb</h2> |
| <p>Wie wird Software bereitgestellt und betrieben?</p> |
| </div> |
| <div class="chips"><span class="chip">Container</span><span class="chip">Kubernetes</span><span class="chip">CI/CD</span><span class="chip">Infrastructure as Code</span><span class="chip">Observability</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>6. Qualität & Security</h2> |
| <p>Wie wird das System robust und sicher?</p> |
| </div> |
| <div class="chips"><span class="chip">Testing</span><span class="chip">Secure by Design</span><span class="chip">Least Privilege</span><span class="chip">Rollback</span><span class="chip">Reliability Engineering</span></div> |
| </article> |
| <article class="layer"> |
| <div> |
| <h2>7. AI Systems</h2> |
| <p>Wie werden KI-Komponenten integriert?</p> |
| </div> |
| <div class="chips"><span class="chip">Model APIs</span><span class="chip">RAG</span><span class="chip">Coding Agents</span><span class="chip">Tool Use</span><span class="chip">Agentic Workflows</span></div> |
| </article> |
| </section> |
|
|
| <h2 class="section-title">Architekturstile vergleichen</h2> |
| <div class="table-wrap"> |
| <table> |
| <thead> |
| <tr><th>Stil</th><th>Grundidee</th><th>Stärke</th><th>Herausforderung</th></tr> |
| </thead> |
| <tbody> |
| <tr><td>Monolith</td><td>Eine Anwendung, ein Deployment</td><td>Einfacher Start, geringe verteilte Komplexität</td><td>Kann bei großer Kopplung schwerer skalierbar werden</td></tr><tr><td>Modularer Monolith</td><td>Ein Deployment, klare interne Module</td><td>Gute Balance aus Einfachheit und Struktur</td><td>Modulgrenzen müssen konsequent eingehalten werden</td></tr><tr><td>Microservices</td><td>Viele unabhängig deploybare Services</td><td>Gezielte Skalierung und autonome Teams</td><td>Netzwerk, Monitoring und Datenkonsistenz werden komplexer</td></tr><tr><td>Event-Driven</td><td>Kommunikation über Events</td><td>Lose Kopplung und Asynchronität</td><td>Debugging, Reihenfolge und Event-Versionierung</td></tr><tr><td>Serverless</td><td>Managed Functions und Events</td><td>Wenig Infrastruktur-Overhead</td><td>Vendor Lock-in, Laufzeit- und Observability-Themen</td></tr> |
| </tbody> |
| </table> |
| </div> |
|
|
| <div class="note"> |
| <strong>Faustregel:</strong> Nicht die modernste Architektur ist automatisch die beste. Gute Architektur passt zu Problem, Team, Last, Änderungsrate und Betriebsmodell. |
| </div> |
|
|
| <div class="footer"> |
| <strong>Softwareentwicklung</strong> · Deutschsprachige Ressourcen zu Software Engineering, Architektur, DevOps und AI Coding.<br> |
| <a href="https://huggingface.co/softwareentwicklung" target="_blank" rel="noopener">huggingface.co/softwareentwicklung</a> |
| </div> |
| </main> |
| </body> |
| </html> |
|
|
