mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-07-14 02:40:27 +00:00
8878 lines
342 KiB
HTML
8878 lines
342 KiB
HTML
|
||
<!doctype html>
|
||
<html lang="en" class="no-js">
|
||
<head>
|
||
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width,initial-scale=1">
|
||
|
||
<meta name="description" content="Enterprise-grade curated portal for the modern Cloud Native ecosystem. High-density, AI-driven selection of top-tier resources.">
|
||
|
||
|
||
<meta name="author" content="Nubenetes">
|
||
|
||
|
||
<link rel="canonical" href="https://nubenetes.com/introduction/">
|
||
|
||
|
||
<link rel="prev" href="../helm/">
|
||
|
||
|
||
<link rel="next" href="../kubernetes-tools/">
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="icon" href="../images/favicon-ultra.png">
|
||
<meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.7.6">
|
||
|
||
|
||
|
||
<title>Introduction - Nubenetes V2 | The AI's Cut</title>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="../assets/stylesheets/main.484c7ddc.min.css">
|
||
|
||
|
||
<link rel="stylesheet" href="../assets/stylesheets/palette.ab4e12ef.min.css">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:300,300i,400,400i,700,700i%7CRoboto+Mono:400,400i,700,700i&display=fallback">
|
||
<style>:root{--md-text-font:"Roboto";--md-code-font:"Roboto Mono"}</style>
|
||
|
||
|
||
|
||
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;700&display=swap">
|
||
|
||
<link rel="stylesheet" href="../static/extra.css">
|
||
|
||
<link rel="stylesheet" href="../static/v2_elite.css?v=2.3.44">
|
||
|
||
<script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
|
||
|
||
|
||
|
||
|
||
|
||
</head>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<body dir="ltr" data-md-color-scheme="slate" data-md-color-primary="custom" data-md-color-accent="custom">
|
||
|
||
|
||
<input class="md-toggle" data-md-toggle="drawer" type="checkbox" id="__drawer" autocomplete="off">
|
||
<input class="md-toggle" data-md-toggle="search" type="checkbox" id="__search" autocomplete="off">
|
||
<label class="md-overlay" for="__drawer"></label>
|
||
<div data-md-component="skip">
|
||
|
||
|
||
<a href="#introduction-microservice-architecture-from-java-ee-to-cloud-native-openshift-vs-kubernetes" class="md-skip">
|
||
Skip to content
|
||
</a>
|
||
|
||
</div>
|
||
<div data-md-component="announce">
|
||
|
||
</div>
|
||
|
||
<div data-md-color-scheme="default" data-md-component="outdated" hidden>
|
||
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<header class="md-header md-header--shadow md-header--lifted" data-md-component="header">
|
||
<nav class="md-header__inner md-grid" aria-label="Header">
|
||
<a href=".." title="Nubenetes V2 | The AI's Cut" class="md-header__button md-logo" aria-label="Nubenetes V2 | The AI's Cut" data-md-component="logo">
|
||
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg>
|
||
|
||
</a>
|
||
<label class="md-header__button md-icon" for="__drawer">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M3 6h18v2H3zm0 5h18v2H3zm0 5h18v2H3z"/></svg>
|
||
</label>
|
||
<div class="md-header__title" data-md-component="header-title">
|
||
<div class="md-header__ellipsis">
|
||
<div class="md-header__topic">
|
||
<span class="md-ellipsis">
|
||
Nubenetes V2 | The AI's Cut
|
||
</span>
|
||
</div>
|
||
<div class="md-header__topic" data-md-component="header-topic">
|
||
<span class="md-ellipsis">
|
||
|
||
Introduction
|
||
|
||
</span>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
<form class="md-header__option" data-md-component="palette">
|
||
|
||
|
||
|
||
|
||
<input class="md-option" data-md-color-media="" data-md-color-scheme="slate" data-md-color-primary="custom" data-md-color-accent="custom" aria-label="Switch to light mode" type="radio" name="__palette" id="__palette_0">
|
||
|
||
<label class="md-header__button md-icon" title="Switch to light mode" for="__palette_1" hidden>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 1 3 5v6c0 5.55 3.84 10.74 9 12 5.16-1.26 9-6.45 9-12V5z"/></svg>
|
||
</label>
|
||
|
||
|
||
|
||
|
||
|
||
<input class="md-option" data-md-color-media="" data-md-color-scheme="default" data-md-color-primary="custom" data-md-color-accent="custom" aria-label="Switch to dark mode" type="radio" name="__palette" id="__palette_1">
|
||
|
||
<label class="md-header__button md-icon" title="Switch to dark mode" for="__palette_0" hidden>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 11c0 5.55-3.84 10.74-9 12-5.16-1.26-9-6.45-9-12V5l9-4 9 4zm-9 10c3.75-1 7-5.46 7-9.78V6.3l-7-3.12L5 6.3v4.92C5 15.54 8.25 20 12 21m-3-6.67c1.76 2.17 5.13 2.24 6.97.07.23-.27.08-.68-.26-.74a4.5 4.5 0 0 1-3.18-2.2 4.5 4.5 0 0 1-.32-3.86.453.453 0 0 0-.51-.6c-3.34.62-4.89 4.61-2.7 7.33"/></svg>
|
||
</label>
|
||
|
||
|
||
</form>
|
||
|
||
|
||
|
||
<script>var palette=__md_get("__palette");if(palette&&palette.color){if("(prefers-color-scheme)"===palette.color.media){var media=matchMedia("(prefers-color-scheme: light)"),input=document.querySelector(media.matches?"[data-md-color-media='(prefers-color-scheme: light)']":"[data-md-color-media='(prefers-color-scheme: dark)']");palette.color.media=input.getAttribute("data-md-color-media"),palette.color.scheme=input.getAttribute("data-md-color-scheme"),palette.color.primary=input.getAttribute("data-md-color-primary"),palette.color.accent=input.getAttribute("data-md-color-accent")}for(var[key,value]of Object.entries(palette.color))document.body.setAttribute("data-md-color-"+key,value)}</script>
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-header__button md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
</label>
|
||
<div class="md-search" data-md-component="search" role="dialog">
|
||
<label class="md-search__overlay" for="__search"></label>
|
||
<div class="md-search__inner" role="search">
|
||
<form class="md-search__form" name="search">
|
||
<input type="text" class="md-search__input" name="query" aria-label="Search" placeholder="Search" autocapitalize="off" autocorrect="off" autocomplete="off" spellcheck="false" data-md-component="search-query" required>
|
||
<label class="md-search__icon md-icon" for="__search">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M9.5 3A6.5 6.5 0 0 1 16 9.5c0 1.61-.59 3.09-1.56 4.23l.27.27h.79l5 5-1.5 1.5-5-5v-.79l-.27-.27A6.52 6.52 0 0 1 9.5 16 6.5 6.5 0 0 1 3 9.5 6.5 6.5 0 0 1 9.5 3m0 2C7 5 5 7 5 9.5S7 14 9.5 14 14 12 14 9.5 12 5 9.5 5"/></svg>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
|
||
</label>
|
||
<nav class="md-search__options" aria-label="Search">
|
||
|
||
<a href="javascript:void(0)" class="md-search__icon md-icon" title="Share" aria-label="Share" data-clipboard data-clipboard-text="" data-md-component="search-share" tabindex="-1">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M18 16.08c-.76 0-1.44.3-1.96.77L8.91 12.7c.05-.23.09-.46.09-.7s-.04-.47-.09-.7l7.05-4.11c.54.5 1.25.81 2.04.81a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3c0 .24.04.47.09.7L8.04 9.81C7.5 9.31 6.79 9 6 9a3 3 0 0 0-3 3 3 3 0 0 0 3 3c.79 0 1.5-.31 2.04-.81l7.12 4.15c-.05.21-.08.43-.08.66 0 1.61 1.31 2.91 2.92 2.91s2.92-1.3 2.92-2.91A2.92 2.92 0 0 0 18 16.08"/></svg>
|
||
</a>
|
||
|
||
<button type="reset" class="md-search__icon md-icon" title="Clear" aria-label="Clear" tabindex="-1">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M19 6.41 17.59 5 12 10.59 6.41 5 5 6.41 10.59 12 5 17.59 6.41 19 12 13.41 17.59 19 19 17.59 13.41 12z"/></svg>
|
||
</button>
|
||
</nav>
|
||
|
||
<div class="md-search__suggest" data-md-component="search-suggest"></div>
|
||
|
||
</form>
|
||
<div class="md-search__output">
|
||
<div class="md-search__scrollwrap" tabindex="0" data-md-scrollfix>
|
||
<div class="md-search-result" data-md-component="search-result">
|
||
<div class="md-search-result__meta">
|
||
Initializing search
|
||
</div>
|
||
<ol class="md-search-result__list" role="presentation"></ol>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
<div class="md-header__source">
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
nubenetes/awesome-kubernetes
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
</nav>
|
||
|
||
|
||
|
||
<nav class="md-tabs" aria-label="Tabs" data-md-component="tabs">
|
||
<div class="md-grid">
|
||
<ul class="md-tabs__list">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="https://nubenetes.com/v1/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
🔙 Back to V1 (Exhaustive)
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href=".." class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
The 2026 Vision
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../tags/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Technical Tags
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../videos/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Agentic Video Hub
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ai-agents-mcp/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
AI
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item md-tabs__item--active">
|
||
<a href="../about/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Architectural Foundations
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../chaos-engineering/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Platform & Site Reliability
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ansible/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Hardened Infrastructure
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../GoogleCloudPlatform/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Cloud Providers (Hyperscalers)
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../caching/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Networking & Service Mesh
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../container-managers/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
The Container Stack
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../crunchydata/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Data & Advanced Analytics
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../argo/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Engineering Pipeline
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../ChromeDevTools/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Developer Ecosystem
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-tabs__item">
|
||
<a href="../appointment-scheduling/" class="md-tabs__link">
|
||
|
||
|
||
|
||
|
||
|
||
Career & Industry
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</div>
|
||
</nav>
|
||
|
||
|
||
</header>
|
||
|
||
<div class="md-container" data-md-component="container">
|
||
|
||
|
||
|
||
|
||
<main class="md-main" data-md-component="main">
|
||
<div class="md-main__inner md-grid">
|
||
|
||
|
||
|
||
<div class="md-sidebar md-sidebar--primary" data-md-component="sidebar" data-md-type="navigation" >
|
||
<div class="md-sidebar__scrollwrap">
|
||
<div class="md-sidebar__inner">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--primary md-nav--lifted md-nav--integrated" aria-label="Navigation" data-md-level="0">
|
||
<label class="md-nav__title" for="__drawer">
|
||
<a href=".." title="Nubenetes V2 | The AI's Cut" class="md-nav__button md-logo" aria-label="Nubenetes V2 | The AI's Cut" data-md-component="logo">
|
||
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 8a3 3 0 0 0 3-3 3 3 0 0 0-3-3 3 3 0 0 0-3 3 3 3 0 0 0 3 3m0 3.54C9.64 9.35 6.5 8 3 8v11c3.5 0 6.64 1.35 9 3.54 2.36-2.19 5.5-3.54 9-3.54V8c-3.5 0-6.64 1.35-9 3.54"/></svg>
|
||
|
||
</a>
|
||
Nubenetes V2 | The AI's Cut
|
||
</label>
|
||
|
||
<div class="md-nav__source">
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" title="Go to repository" class="md-source" data-md-component="source">
|
||
<div class="md-source__icon md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M439.6 236.1 244 40.5c-5.4-5.5-12.8-8.5-20.4-8.5s-15 3-20.4 8.4L162.5 81l51.5 51.5c27.1-9.1 52.7 16.8 43.4 43.7l49.7 49.7c34.2-11.8 61.2 31 35.5 56.7-26.5 26.5-70.2-2.9-56-37.3L240.3 199v121.9c25.3 12.5 22.3 41.8 9.1 55-6.4 6.4-15.2 10.1-24.3 10.1s-17.8-3.6-24.3-10.1c-17.6-17.6-11.1-46.9 11.2-56v-123c-20.8-8.5-24.6-30.7-18.6-45L142.6 101 8.5 235.1C3 240.6 0 247.9 0 255.5s3 15 8.5 20.4l195.6 195.7c5.4 5.4 12.7 8.4 20.4 8.4s15-3 20.4-8.4l194.7-194.7c5.4-5.4 8.4-12.8 8.4-20.4s-3-15-8.4-20.4"/></svg>
|
||
</div>
|
||
<div class="md-source__repository">
|
||
nubenetes/awesome-kubernetes
|
||
</div>
|
||
</a>
|
||
</div>
|
||
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="https://nubenetes.com/v1/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
🔙 Back to V1 (Exhaustive)
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href=".." class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
The 2026 Vision
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../tags/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Technical Tags
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../videos/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Agentic Video Hub
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ai-agents-mcp/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
AI
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
|
||
|
||
|
||
|
||
<input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_6" checked>
|
||
|
||
|
||
<label class="md-nav__link" for="__nav_6" id="__nav_6_label" tabindex="">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Architectural Foundations
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<nav class="md-nav" data-md-level="1" aria-labelledby="__nav_6_label" aria-expanded="true">
|
||
<label class="md-nav__title" for="__nav_6">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
|
||
Architectural Foundations
|
||
|
||
|
||
</label>
|
||
<ul class="md-nav__list" data-md-scrollfix>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../about/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
About
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cheatsheets/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cheatsheets
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cloud-arch-diagrams/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cloud Arch Diagrams
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../cloud-asset-inventory/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cloud Asset Inventory
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../customer/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Customer
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../demos/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Demos
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../devops-tools/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
DevOps Tools
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../faq/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Faq
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../git/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Git
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../grafana/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Grafana
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../helm/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Helm
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--active">
|
||
|
||
<input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__link md-nav__link--active" for="__toc">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Introduction
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
</label>
|
||
|
||
<a href="./" class="md-nav__link md-nav__link--active">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Introduction
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
|
||
|
||
|
||
<nav class="md-nav md-nav--secondary" aria-label="Table of contents">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<label class="md-nav__title" for="__toc">
|
||
<span class="md-nav__icon md-icon"></span>
|
||
Table of contents
|
||
</label>
|
||
<ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#table-of-contents" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Table of Contents
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#vision-2026" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Vision 2026
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Vision 2026">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ecosystem-map" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Ecosystem Map
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#application-modernization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Application Modernization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Application Modernization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monolith-to-microservices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monolith to Microservices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Monolith to Microservices">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#automated-refactoring" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Automated Refactoring
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#case-studies" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Case Studies
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#guides" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Guides
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#apis" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
APIs
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="APIs">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#protocols" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Protocols
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Best Practices">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#eda" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
EDA
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#data-management" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Data Management
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Data Management">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#patterns-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Patterns (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Patterns (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#eda-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
EDA (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#evolution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Evolution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monoliths" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monoliths
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#twelve-factor-app" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Twelve-Factor App
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#saas" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
SaaS
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="SaaS">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-tenancy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Tenancy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-debt" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Debt
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Technical Debt">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architecture Patterns">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud-Native Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#artificial-intelligence-and-ml" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Artificial Intelligence and ML
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Artificial Intelligence and ML">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#machine-learning-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Machine Learning Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Machine Learning Engineering">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#python-ecosystem" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Python Ecosystem
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#business-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Business Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Business Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#digital-transformation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Digital Transformation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Digital Transformation">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cultural-dynamics" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cultural Dynamics
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#organizational-structure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Organizational Structure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Organizational Structure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops-culture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps Culture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#career-development" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Career Development
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Career Development">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architect-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architect Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architect Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#skillsets" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Skillsets
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-anti-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Anti-patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#migration-methodology" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Migration Methodology
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud-Native
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud-Native">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hybrid-cloud-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hybrid Cloud Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Hybrid Cloud Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#market-trends" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Market Trends
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Migration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hands-on" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hands-On
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#methodology" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Methodology
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#strategies" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Strategies
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modernization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modernization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Modernization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#reactive-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Reactive Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-cloud-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Cloud Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Multi-Cloud Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#data-management-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Data Management (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#network-and-security" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Network and Security
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#resilience-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Resilience Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#private-cloud" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Private Cloud
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Private Cloud">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hybrid-cloud-strategy-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hybrid Cloud Strategy (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#professional-development" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Professional Development
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Professional Development">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#career-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Career Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-cloud-benefits" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Cloud Benefits
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-cloud-decisions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Cloud Decisions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-architecture-and-infrastructure-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Architecture and Infrastructure Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Architecture and Infrastructure Strategy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#application-design" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Application Design
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Application Design">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#horizontal-scaling" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Horizontal Scaling
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#system-design-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
System Design Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cost-optimization-and-finops" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cost Optimization and FinOps
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cost Optimization and FinOps">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#efficiency-bottlenecks" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Efficiency Bottlenecks
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#deployment-models" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Deployment Models
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Deployment Models">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hybrid-and-private-cloud" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hybrid and Private Cloud
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#high-availability" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
High Availability
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="High Availability">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#core-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Core Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-region-deployments" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Region Deployments
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#market-trends-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Market Trends (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Market Trends (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#open-source-business-models" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Open Source Business Models
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#migration-and-modernization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Migration and Modernization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Migration and Modernization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#enterprise-solutions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Enterprise Solutions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#planning-resources" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Planning Resources
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modern-architectural-paradigms" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modern Architectural Paradigms
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Modern Architectural Paradigms">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#mach-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
MACH Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-cloud-strategy-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Cloud Strategy (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Multi-Cloud Strategy (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-designs" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Designs
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-planning" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Planning
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#business-drivers" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Business Drivers
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#storage-and-hybrid-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Storage and Hybrid Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Storage and Hybrid Systems">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#topology-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Topology Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#automation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Automation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Automation">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#concepts" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Concepts
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="DevOps">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-abstraction" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure Abstraction
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#hybrid-cloud" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Hybrid Cloud
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Hybrid Cloud">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#management-tools" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Management Tools
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#openshift" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
OpenShift
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#openshift-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
OpenShift Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-and-kubernetes-core" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Native and Kubernetes Core
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Native and Kubernetes Core">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#business-value-and-roi" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Business Value and ROI
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Business Value and ROI">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#operational-automation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Operational Automation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Container Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#deep-dive" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Deep Dive
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#future-outlook" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Future Outlook
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#orchestrator-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Orchestrator Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#market-trends-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Market Trends (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Market Trends (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#adoption-analytics" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Adoption Analytics
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ecosystem-evolution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Ecosystem Evolution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#migration-and-modernization-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Migration and Modernization (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Migration and Modernization (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#anti-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Anti-Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#workload-transition" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Workload Transition
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#testing-and-reliability" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Testing and Reliability
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Testing and Reliability">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#control-plane-validation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Control Plane Validation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#virtualization-and-containers" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Virtualization and Containers
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Virtualization and Containers">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#container-anti-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Container Anti-patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modernization-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modernization Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Native Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Native Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#containerization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Containerization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Containerization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-patterns-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Patterns (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Design Patterns (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#operators-and-sidecars" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Operators and Sidecars
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#gitops" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
GitOps
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="GitOps">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Native Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices (3)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#enterprise-solutions-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Enterprise Solutions (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monoliths-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monoliths (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-infrastructure_1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Native Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Native Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#business-architecture-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Business Architecture (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Business Architecture (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-management" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure Management
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#value-proposition" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Value Proposition
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cncf-ecosystem" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
CNCF Ecosystem
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="CNCF Ecosystem">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform-engineering-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform Engineering (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#containerization-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Containerization (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Containerization (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#operations-guide" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Operations Guide
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#industry-standards" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Industry Standards
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Industry Standards">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#market-trends-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Market Trends (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#future-trends" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Future Trends
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#industry-standards-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Industry Standards (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#industry-trends" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Industry Trends
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-tools" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Tools
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#multi-cluster-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Multi-Cluster Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform-engineering-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform Engineering (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#professional-development-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Professional Development (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Professional Development (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#career-engineering-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Career Engineering (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technology-assessment" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technology Assessment
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Technology Assessment">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#compute-paradigms" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Compute Paradigms
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Native Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Native Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform-comparison" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform Comparison
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Platform Comparison">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#openshift-vs-kubernetes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
OpenShift vs Kubernetes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#data-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Data Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Data Engineering">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#education" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Education
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Education">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cookbook" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cookbook
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops-and-cicd" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps and CICD
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="DevOps and CICD">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#continuous-integration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Continuous Integration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Continuous Integration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#developer-experience" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Developer Experience
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-4" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (4)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices (4)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#tooling-ecosystem" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Tooling Ecosystem
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops-automation-and-modern-systems-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps Automation and Modern Systems Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="DevOps Automation and Modern Systems Engineering">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#automation-and-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Automation and Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Automation and Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#operational-efficiency" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Operational Efficiency
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#culture-and-roles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Culture and Roles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Culture and Roles">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#systems-administration-evolution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Systems Administration Evolution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-as-code" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure-as-Code
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Infrastructure-as-Code">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#self-healing-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Self-Healing Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#security-and-governance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Security and Governance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Security and Governance">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#policy-as-code" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Policy-as-Code
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering-principles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering Principles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering Principles">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#programming-languages" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Programming Languages
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-debt-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Debt (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#distributed-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Distributed Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Distributed Systems">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#consensus" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Consensus
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Consensus">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#algorithms" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Algorithms
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#edge-and-iot-orchestration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Edge and IoT Orchestration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Edge and IoT Orchestration">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#embedded-software" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Embedded Software
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Embedded Software">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#automotive-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Automotive Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#emerging-technology" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Emerging Technology
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Emerging Technology">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#quantum-computing" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Quantum Computing
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Quantum Computing">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals-4" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals (4)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#frontend-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Frontend Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Frontend Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-patterns-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Patterns (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Design Patterns (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#bff" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
BFF
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microfrontends" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microfrontends
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microfrontends">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#aws-serverless" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
AWS Serverless
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#introduction" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Introduction
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Infrastructure">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-architecture-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Architecture (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Architecture (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#paradigms" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Paradigms
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-financials" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Financials
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Cloud Financials">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#finops" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
FinOps
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#legacy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Legacy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Legacy">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#mainframe" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Mainframe
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#virtualization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Virtualization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Virtualization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#broadcom-era" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Broadcom Era
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-and-hardware" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure and Hardware
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Infrastructure and Hardware">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#data-center-investments" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Data Center Investments
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Data Center Investments">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#europe" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Europe
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-tools-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes Tools (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes Tools (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#general-reference" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
General Reference
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#methodology-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Methodology (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Methodology (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#careers" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Careers
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Careers">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#enterprise-strategy" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Enterprise Strategy
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#development" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Development
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Development">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#learning-resources" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Learning Resources
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#documentation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Documentation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Documentation">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#governance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Governance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#engineering-leadership" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Engineering Leadership
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Engineering Leadership">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#governance-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Governance (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-debt-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Debt (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#metrics" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Metrics
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Metrics">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-debt-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Debt (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#quality" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Quality
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Quality">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#embedded-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Embedded Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#roles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Roles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Roles">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-governance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud Governance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technical-debt-4" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technical Debt (4)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-5" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (5)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices (5)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#anti-patterns-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Anti-Patterns (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Anti-Patterns (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#failure-modes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Failure Modes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#lessons-learned" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Lessons Learned
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#data-management-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Data Management (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Data Management (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#event-driven-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Event-Driven Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-patterns-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Patterns (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Design Patterns (3)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#catalog" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Catalog
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#dotnet" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DotNet
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#event-driven" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Event-Driven
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#reference-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Reference Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-principles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Principles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Design Principles">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#core-principles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Core Principles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#evaluation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Evaluation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#frameworks" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Frameworks
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Frameworks">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#ecosystem" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Ecosystem
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#implementation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Implementation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Implementation">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cqrs" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
CQRS
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modernization-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modernization (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Modernization (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#automated-migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Automated Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cdc-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
CDC Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monolith-migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monolith Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#observability" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Observability
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Observability">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#namespaces" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Namespaces
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#orchestration-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Orchestration (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Orchestration (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-and-distributed-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices and Distributed Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices and Distributed Systems">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-evolution" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Evolution
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architecture Evolution">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#abstractions-and-frameworks" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Abstractions and Frameworks
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#curated-reference" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Curated Reference
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-patterns-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Patterns (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architecture Patterns (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#anti-patterns-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Anti-Patterns (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#best-practices-4" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Best Practices (4)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#component-design" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Component Design
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#decision-matrix" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Decision Matrix
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fundamentals-5" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fundamentals (5)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#deployment-models-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Deployment Models (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Deployment Models (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#orchestration-options" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Orchestration Options
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering-principles-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering Principles (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering Principles (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#developer-workflow" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Developer Workflow
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#testing-and-reliability-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Testing and Reliability (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Testing and Reliability (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#fault-tolerance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Fault Tolerance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#operations" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Operations
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Operations">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#disaster-recovery" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Disaster Recovery
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Disaster Recovery">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#cloud-native-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Cloud-Native (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#orchestration-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Orchestration (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Orchestration (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#kubernetes-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Kubernetes (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Kubernetes (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#anti-patterns-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Anti-Patterns (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#dependency-isolation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Dependency Isolation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-6" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (6)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#paradigms-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Paradigms (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#prerequisites" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Prerequisites
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#processes" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Processes
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#twelve-factor-app-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Twelve-Factor App (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#workloads" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Workloads
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#platform-engineering-3" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Platform Engineering (3)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Platform Engineering (3)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#paas-solutions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
PaaS Solutions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="PaaS Solutions">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#market-shifts" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Market Shifts
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#reference-architectures" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Reference Architectures
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Reference Architectures">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#aws" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
AWS
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#azure" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Azure
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#gcp" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
GCP
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#self-service" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Self-Service
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Self-Service">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#case-studies-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Case Studies (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#concepts-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Concepts (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#service-catalogs" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Service Catalogs
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Service Catalogs">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-governance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices Governance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#professional-development-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Professional Development (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Professional Development (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#career-guidance" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Career Guidance
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#reliability-engineering" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Reliability Engineering
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Reliability Engineering">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#resilience-patterns-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Resilience Patterns (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Resilience Patterns (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#infrastructure-stability" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Infrastructure Stability
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#security" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Security
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Security">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-protection" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Protection
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Protection">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#obfuscation" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Obfuscation
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Architecture">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#application-modernization-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Application Modernization (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Application Modernization (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#legacy-migration" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Legacy Migration
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#event-driven-systems" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Event-Driven Systems
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Event-Driven Systems">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#asynchronous-messaging" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Asynchronous Messaging
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-7" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (7)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Microservices (7)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#decomposition-patterns" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Decomposition Patterns
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#design-patterns-4" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Design Patterns (4)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#distributed-transactions" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Distributed Transactions
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#maturity-models" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Maturity Models
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monolith-transition" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monolith Transition
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#technology-selection" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Technology Selection
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#value-proposition-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Value Proposition (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modernization-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modernization (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Modernization (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#strangler-pattern" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Strangler Pattern
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#monoliths-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Monoliths (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Monoliths (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#modular-monolith" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Modular Monolith
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-delivery" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Delivery
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Delivery">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#devops-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
DevOps (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="DevOps (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#industry-trends-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Industry Trends (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architecture-patterns-2" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architecture Patterns (2)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Architecture Patterns (2)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#microservices-8" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Microservices (8)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#education-1" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Education (1)
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Education (1)">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#systems-programming" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Systems Programming
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#full-stack-fundamentals" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Full-Stack Fundamentals
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Full-Stack Fundamentals">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#architectural-roles" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Architectural Roles
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#performance-optimization" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Performance Optimization
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Performance Optimization">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#system-architecture" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
System Architecture
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#web-development" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Web Development
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Web Development">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#nodejs" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
NodeJS
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#software-engineering-practices" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Software Engineering Practices
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Software Engineering Practices">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#developer-productivity" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Developer Productivity
|
||
|
||
</span>
|
||
</a>
|
||
|
||
<nav class="md-nav" aria-label="Developer Productivity">
|
||
<ul class="md-nav__list">
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#roadmaps" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Roadmaps
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
<li class="md-nav__item">
|
||
<a href="#toolkits" class="md-nav__link">
|
||
<span class="md-ellipsis">
|
||
|
||
Toolkits
|
||
|
||
</span>
|
||
</a>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-tools/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Tools
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes-tutorials/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes Tutorials
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../kubernetes/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Kubernetes
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../linux/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Linux
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../matrix-table/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Matrix Table
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../mkdocs/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Mkdocs
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../monitoring/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Monitoring
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../other-awesome-lists/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Other Awesome Lists
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item">
|
||
<a href="../prometheus/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Prometheus
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
</a>
|
||
</li>
|
||
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../chaos-engineering/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Platform & Site Reliability
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ansible/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Hardened Infrastructure
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../GoogleCloudPlatform/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Cloud Providers (Hyperscalers)
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../caching/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Networking & Service Mesh
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../container-managers/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
The Container Stack
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../crunchydata/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Data & Advanced Analytics
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../argo/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Engineering Pipeline
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../ChromeDevTools/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Developer Ecosystem
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<li class="md-nav__item md-nav__item--pruned md-nav__item--nested">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="../appointment-scheduling/" class="md-nav__link">
|
||
|
||
|
||
|
||
<span class="md-ellipsis">
|
||
|
||
|
||
Career & Industry
|
||
|
||
|
||
|
||
</span>
|
||
|
||
|
||
|
||
|
||
<span class="md-nav__icon md-icon"></span>
|
||
|
||
</a>
|
||
|
||
|
||
|
||
</li>
|
||
|
||
|
||
|
||
</ul>
|
||
</nav>
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
<div class="md-content" data-md-component="content">
|
||
|
||
<article class="md-content__inner md-typeset">
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes/edit/master/v2-docs/introduction.md" title="Edit this page" class="md-content__button md-icon" rel="edit">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M10 20H6V4h7v5h5v3.1l2-2V8l-6-6H6c-1.1 0-2 .9-2 2v16c0 1.1.9 2 2 2h4zm10.2-7c.1 0 .3.1.4.2l1.3 1.3c.2.2.2.6 0 .8l-1 1-2.1-2.1 1-1c.1-.1.2-.2.4-.2m0 3.9L14.1 23H12v-2.1l6.1-6.1z"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes/raw/master/v2-docs/introduction.md" title="View source of this page" class="md-content__button md-icon">
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M17 18c.56 0 1 .44 1 1s-.44 1-1 1-1-.44-1-1 .44-1 1-1m0-3c-2.73 0-5.06 1.66-6 4 .94 2.34 3.27 4 6 4s5.06-1.66 6-4c-.94-2.34-3.27-4-6-4m0 6.5a2.5 2.5 0 0 1-2.5-2.5 2.5 2.5 0 0 1 2.5-2.5 2.5 2.5 0 0 1 2.5 2.5 2.5 2.5 0 0 1-2.5 2.5M9.27 20H6V4h7v5h5v4.07c.7.08 1.36.25 2 .49V8l-6-6H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h4.5a8.2 8.2 0 0 1-1.23-2"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
<h1 id="introduction-microservice-architecture-from-java-ee-to-cloud-native-openshift-vs-kubernetes">Introduction. Microservice Architecture. From Java EE To Cloud Native. Openshift VS Kubernetes<a class="headerlink" href="#introduction-microservice-architecture-from-java-ee-to-cloud-native-openshift-vs-kubernetes" title="Permanent link">¶</a></h1>
|
||
<div class="admonition tip">
|
||
<p class="admonition-title">Nubenetes V2 Elite Portal</p>
|
||
<p>You are browsing the AI-Curated V2 Elite Edition. Looking for the exhaustive list of references? Check out the <a href="/v1/introduction/"><strong>V1 Historical Archive</strong></a>.</p>
|
||
</div>
|
||
<div class="admonition info">
|
||
<p class="admonition-title">Architectural Context</p>
|
||
<p>Detailed reference for Introduction. Microservice Architecture. From Java EE To Cloud Native. Openshift VS Kubernetes in the context of Architectural Foundations.</p>
|
||
</div>
|
||
<h2 id="table-of-contents">Table of Contents<a class="headerlink" href="#table-of-contents" title="Permanent link">¶</a></h2>
|
||
<ol>
|
||
<li><a href="#application-modernization">Application Modernization</a></li>
|
||
<li><a href="#monolith-to-microservices">Monolith to Microservices</a><ul>
|
||
<li><a href="#automated-refactoring">Automated Refactoring</a></li>
|
||
<li><a href="#case-studies">Case Studies</a></li>
|
||
<li><a href="#guides">Guides</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#architecture">Architecture</a></li>
|
||
<li><a href="#apis">APIs</a><ul>
|
||
<li><a href="#protocols">Protocols</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#best-practices">Best Practices</a><ul>
|
||
<li><a href="#eda">EDA</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#data-management">Data Management</a><ul>
|
||
<li><a href="#patterns">Patterns</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices">Microservices</a><ul>
|
||
<li><a href="#fundamentals">Fundamentals</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#patterns-1">Patterns</a><ul>
|
||
<li><a href="#eda-1">EDA</a></li>
|
||
<li><a href="#evolution">Evolution</a></li>
|
||
<li><a href="#monoliths">Monoliths</a></li>
|
||
<li><a href="#twelve-factor-app">Twelve-Factor App</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#saas">SaaS</a><ul>
|
||
<li><a href="#multi-tenancy">Multi-Tenancy</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#technical-debt">Technical Debt</a><ul>
|
||
<li><a href="#microservices-1">Microservices</a></li>
|
||
<li><a href="#orchestration">Orchestration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#architecture-patterns">Architecture Patterns</a></li>
|
||
<li><a href="#microservices-2">Microservices</a><ul>
|
||
<li><a href="#cloud-native-infrastructure">Cloud-Native Infrastructure</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#artificial-intelligence-and-ml">Artificial Intelligence and ML</a></li>
|
||
<li><a href="#machine-learning-engineering">Machine Learning Engineering</a><ul>
|
||
<li><a href="#python-ecosystem">Python Ecosystem</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#business-architecture">Business Architecture</a></li>
|
||
<li><a href="#digital-transformation">Digital Transformation</a><ul>
|
||
<li><a href="#cultural-dynamics">Cultural Dynamics</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#organizational-structure">Organizational Structure</a><ul>
|
||
<li><a href="#devops-culture">DevOps Culture</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#career-development">Career Development</a></li>
|
||
<li><a href="#architect-strategy">Architect Strategy</a><ul>
|
||
<li><a href="#skillsets">Skillsets</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-architecture">Cloud Architecture</a></li>
|
||
<li><a href="#cloud-strategy">Cloud Strategy</a><ul>
|
||
<li><a href="#design-anti-patterns">Design Anti-patterns</a></li>
|
||
<li><a href="#migration-methodology">Migration Methodology</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-native">Cloud-Native</a><ul>
|
||
<li><a href="#design-patterns">Design Patterns</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#hybrid-cloud-strategy">Hybrid Cloud Strategy</a><ul>
|
||
<li><a href="#market-trends">Market Trends</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#migration">Migration</a><ul>
|
||
<li><a href="#hands-on">Hands-On</a></li>
|
||
<li><a href="#methodology">Methodology</a></li>
|
||
<li><a href="#strategies">Strategies</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#modernization">Modernization</a><ul>
|
||
<li><a href="#reactive-systems">Reactive Systems</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#multi-cloud-strategy">Multi-Cloud Strategy</a><ul>
|
||
<li><a href="#data-management-1">Data Management</a></li>
|
||
<li><a href="#network-and-security">Network and Security</a></li>
|
||
<li><a href="#resilience-patterns">Resilience Patterns</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#private-cloud">Private Cloud</a><ul>
|
||
<li><a href="#hybrid-cloud-strategy-1">Hybrid Cloud Strategy</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#professional-development">Professional Development</a><ul>
|
||
<li><a href="#career-engineering">Career Engineering</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#strategy">Strategy</a><ul>
|
||
<li><a href="#multi-cloud-benefits">Multi-Cloud Benefits</a></li>
|
||
<li><a href="#multi-cloud-decisions">Multi-Cloud Decisions</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-architecture-and-infrastructure-strategy">Cloud Architecture and Infrastructure Strategy</a></li>
|
||
<li><a href="#application-design">Application Design</a><ul>
|
||
<li><a href="#horizontal-scaling">Horizontal Scaling</a></li>
|
||
<li><a href="#system-design-patterns">System Design Patterns</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cost-optimization-and-finops">Cost Optimization and FinOps</a><ul>
|
||
<li><a href="#efficiency-bottlenecks">Efficiency Bottlenecks</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#deployment-models">Deployment Models</a><ul>
|
||
<li><a href="#comparison">Comparison</a></li>
|
||
<li><a href="#hybrid-and-private-cloud">Hybrid and Private Cloud</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#high-availability">High Availability</a><ul>
|
||
<li><a href="#core-patterns">Core Patterns</a></li>
|
||
<li><a href="#multi-region-deployments">Multi-Region Deployments</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#market-trends-1">Market Trends</a><ul>
|
||
<li><a href="#open-source-business-models">Open Source Business Models</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#migration-and-modernization">Migration and Modernization</a><ul>
|
||
<li><a href="#enterprise-solutions">Enterprise Solutions</a></li>
|
||
<li><a href="#planning-resources">Planning Resources</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#modern-architectural-paradigms">Modern Architectural Paradigms</a><ul>
|
||
<li><a href="#mach-architecture">MACH Architecture</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#multi-cloud-strategy-1">Multi-Cloud Strategy</a><ul>
|
||
<li><a href="#architecture-designs">Architecture Designs</a></li>
|
||
<li><a href="#architecture-planning">Architecture Planning</a></li>
|
||
<li><a href="#business-drivers">Business Drivers</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#storage-and-hybrid-systems">Storage and Hybrid Systems</a><ul>
|
||
<li><a href="#topology-comparison">Topology Comparison</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-infrastructure">Cloud Infrastructure</a></li>
|
||
<li><a href="#automation">Automation</a><ul>
|
||
<li><a href="#concepts">Concepts</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#devops">DevOps</a><ul>
|
||
<li><a href="#infrastructure-abstraction">Infrastructure Abstraction</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#hybrid-cloud">Hybrid Cloud</a><ul>
|
||
<li><a href="#management-tools">Management Tools</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#kubernetes">Kubernetes</a><ul>
|
||
<li><a href="#container-patterns">Container Patterns</a></li>
|
||
<li><a href="#openshift">OpenShift</a></li>
|
||
<li><a href="#openshift-comparison">OpenShift Comparison</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-native-and-kubernetes-core">Cloud Native and Kubernetes Core</a></li>
|
||
<li><a href="#business-value-and-roi">Business Value and ROI</a><ul>
|
||
<li><a href="#operational-automation">Operational Automation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#container-orchestration">Container Orchestration</a><ul>
|
||
<li><a href="#deep-dive">Deep Dive</a></li>
|
||
<li><a href="#fundamentals-1">Fundamentals</a></li>
|
||
<li><a href="#future-outlook">Future Outlook</a></li>
|
||
<li><a href="#orchestrator-comparison">Orchestrator Comparison</a></li>
|
||
<li><a href="#platform-engineering">Platform Engineering</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#market-trends-2">Market Trends</a><ul>
|
||
<li><a href="#adoption-analytics">Adoption Analytics</a></li>
|
||
<li><a href="#ecosystem-evolution">Ecosystem Evolution</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#migration-and-modernization-1">Migration and Modernization</a><ul>
|
||
<li><a href="#anti-patterns">Anti-Patterns</a></li>
|
||
<li><a href="#workload-transition">Workload Transition</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#testing-and-reliability">Testing and Reliability</a><ul>
|
||
<li><a href="#control-plane-validation">Control Plane Validation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#virtualization-and-containers">Virtualization and Containers</a><ul>
|
||
<li><a href="#architecture-comparison">Architecture Comparison</a></li>
|
||
<li><a href="#container-anti-patterns">Container Anti-patterns</a></li>
|
||
<li><a href="#modernization-strategy">Modernization Strategy</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-native-architecture">Cloud Native Architecture</a></li>
|
||
<li><a href="#containerization">Containerization</a><ul>
|
||
<li><a href="#kubernetes-1">Kubernetes</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#design-patterns-1">Design Patterns</a><ul>
|
||
<li><a href="#operators-and-sidecars">Operators and Sidecars</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#gitops">GitOps</a><ul>
|
||
<li><a href="#cloud-native-strategy">Cloud Native Strategy</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices-3">Microservices</a><ul>
|
||
<li><a href="#enterprise-solutions-1">Enterprise Solutions</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering">Software Engineering</a><ul>
|
||
<li><a href="#monoliths-1">Monoliths</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-native-infrastructure">Cloud Native Infrastructure</a></li>
|
||
<li><a href="#business-architecture-1">Business Architecture</a><ul>
|
||
<li><a href="#infrastructure-management">Infrastructure Management</a></li>
|
||
<li><a href="#value-proposition">Value Proposition</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cncf-ecosystem">CNCF Ecosystem</a><ul>
|
||
<li><a href="#platform-engineering-1">Platform Engineering</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#containerization-1">Containerization</a><ul>
|
||
<li><a href="#fundamentals-2">Fundamentals</a></li>
|
||
<li><a href="#operations-guide">Operations Guide</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#industry-standards">Industry Standards</a><ul>
|
||
<li><a href="#market-trends-3">Market Trends</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#kubernetes-orchestration">Kubernetes Orchestration</a><ul>
|
||
<li><a href="#fundamentals-3">Fundamentals</a></li>
|
||
<li><a href="#future-trends">Future Trends</a></li>
|
||
<li><a href="#industry-standards-1">Industry Standards</a></li>
|
||
<li><a href="#industry-trends">Industry Trends</a></li>
|
||
<li><a href="#kubernetes-tools">Kubernetes Tools</a></li>
|
||
<li><a href="#multi-cluster-strategy">Multi-Cluster Strategy</a></li>
|
||
<li><a href="#platform-engineering-2">Platform Engineering</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#professional-development-1">Professional Development</a><ul>
|
||
<li><a href="#career-engineering-1">Career Engineering</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#technology-assessment">Technology Assessment</a><ul>
|
||
<li><a href="#compute-paradigms">Compute Paradigms</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-native-orchestration">Cloud Native Orchestration</a></li>
|
||
<li><a href="#platform-comparison">Platform Comparison</a><ul>
|
||
<li><a href="#openshift-vs-kubernetes">OpenShift vs Kubernetes</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#data-engineering">Data Engineering</a></li>
|
||
<li><a href="#education">Education</a><ul>
|
||
<li><a href="#cookbook">Cookbook</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#devops-and-cicd">DevOps and CICD</a></li>
|
||
<li><a href="#continuous-integration">Continuous Integration</a><ul>
|
||
<li><a href="#developer-experience">Developer Experience</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices-4">Microservices</a><ul>
|
||
<li><a href="#tooling-ecosystem">Tooling Ecosystem</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#devops-automation-and-modern-systems-engineering">DevOps Automation and Modern Systems Engineering</a></li>
|
||
<li><a href="#automation-and-orchestration">Automation and Orchestration</a><ul>
|
||
<li><a href="#operational-efficiency">Operational Efficiency</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#culture-and-roles">Culture and Roles</a><ul>
|
||
<li><a href="#systems-administration-evolution">Systems Administration Evolution</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#infrastructure-as-code">Infrastructure-as-Code</a><ul>
|
||
<li><a href="#self-healing-systems">Self-Healing Systems</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#security-and-governance">Security and Governance</a><ul>
|
||
<li><a href="#policy-as-code">Policy-as-Code</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering-principles">Software Engineering Principles</a><ul>
|
||
<li><a href="#programming-languages">Programming Languages</a></li>
|
||
<li><a href="#technical-debt-1">Technical Debt</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#distributed-systems">Distributed Systems</a></li>
|
||
<li><a href="#consensus">Consensus</a><ul>
|
||
<li><a href="#algorithms">Algorithms</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#edge-and-iot-orchestration">Edge and IoT Orchestration</a></li>
|
||
<li><a href="#embedded-software">Embedded Software</a><ul>
|
||
<li><a href="#automotive-systems">Automotive Systems</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#emerging-technology">Emerging Technology</a></li>
|
||
<li><a href="#quantum-computing">Quantum Computing</a><ul>
|
||
<li><a href="#fundamentals-4">Fundamentals</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#frontend-architecture">Frontend Architecture</a></li>
|
||
<li><a href="#design-patterns-2">Design Patterns</a><ul>
|
||
<li><a href="#bff">BFF</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microfrontends">Microfrontends</a><ul>
|
||
<li><a href="#aws-serverless">AWS Serverless</a></li>
|
||
<li><a href="#introduction">Introduction</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#infrastructure">Infrastructure</a></li>
|
||
<li><a href="#cloud-architecture-1">Cloud Architecture</a><ul>
|
||
<li><a href="#paradigms">Paradigms</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#cloud-financials">Cloud Financials</a><ul>
|
||
<li><a href="#finops">FinOps</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#legacy">Legacy</a><ul>
|
||
<li><a href="#mainframe">Mainframe</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#virtualization">Virtualization</a><ul>
|
||
<li><a href="#broadcom-era">Broadcom Era</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#infrastructure-and-hardware">Infrastructure and Hardware</a></li>
|
||
<li><a href="#data-center-investments">Data Center Investments</a><ul>
|
||
<li><a href="#europe">Europe</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#kubernetes-tools-1">Kubernetes Tools</a></li>
|
||
<li><a href="#general-reference">General Reference</a></li>
|
||
<li><a href="#methodology-1">Methodology</a></li>
|
||
<li><a href="#careers">Careers</a><ul>
|
||
<li><a href="#enterprise-strategy">Enterprise Strategy</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#development">Development</a><ul>
|
||
<li><a href="#best-practices-1">Best Practices</a></li>
|
||
<li><a href="#learning-resources">Learning Resources</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#documentation">Documentation</a><ul>
|
||
<li><a href="#governance">Governance</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#engineering-leadership">Engineering Leadership</a><ul>
|
||
<li><a href="#governance-1">Governance</a></li>
|
||
<li><a href="#technical-debt-2">Technical Debt</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#metrics">Metrics</a><ul>
|
||
<li><a href="#technical-debt-3">Technical Debt</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#quality">Quality</a><ul>
|
||
<li><a href="#embedded-systems">Embedded Systems</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#roles">Roles</a><ul>
|
||
<li><a href="#cloud-governance">Cloud Governance</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering-1">Software Engineering</a><ul>
|
||
<li><a href="#technical-debt-4">Technical Debt</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices-5">Microservices</a></li>
|
||
<li><a href="#anti-patterns-1">Anti-Patterns</a><ul>
|
||
<li><a href="#failure-modes">Failure Modes</a></li>
|
||
<li><a href="#lessons-learned">Lessons Learned</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#data-management-2">Data Management</a><ul>
|
||
<li><a href="#event-driven-architecture">Event-Driven Architecture</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#design-patterns-3">Design Patterns</a><ul>
|
||
<li><a href="#best-practices-2">Best Practices</a></li>
|
||
<li><a href="#catalog">Catalog</a></li>
|
||
<li><a href="#dotnet">DotNet</a></li>
|
||
<li><a href="#event-driven">Event-Driven</a></li>
|
||
<li><a href="#reference-architecture">Reference Architecture</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#design-principles">Design Principles</a><ul>
|
||
<li><a href="#core-principles">Core Principles</a></li>
|
||
<li><a href="#evaluation">Evaluation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#frameworks">Frameworks</a><ul>
|
||
<li><a href="#ecosystem">Ecosystem</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#implementation">Implementation</a><ul>
|
||
<li><a href="#cqrs">CQRS</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#modernization-1">Modernization</a><ul>
|
||
<li><a href="#automated-migration">Automated Migration</a></li>
|
||
<li><a href="#cdc-patterns">CDC Patterns</a></li>
|
||
<li><a href="#monolith-migration">Monolith Migration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#observability">Observability</a><ul>
|
||
<li><a href="#namespaces">Namespaces</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#orchestration-1">Orchestration</a><ul>
|
||
<li><a href="#best-practices-3">Best Practices</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices-and-distributed-systems">Microservices and Distributed Systems</a></li>
|
||
<li><a href="#architecture-evolution">Architecture Evolution</a><ul>
|
||
<li><a href="#abstractions-and-frameworks">Abstractions and Frameworks</a></li>
|
||
<li><a href="#curated-reference">Curated Reference</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#architecture-patterns-1">Architecture Patterns</a><ul>
|
||
<li><a href="#anti-patterns-2">Anti-Patterns</a></li>
|
||
<li><a href="#best-practices-4">Best Practices</a></li>
|
||
<li><a href="#component-design">Component Design</a></li>
|
||
<li><a href="#decision-matrix">Decision Matrix</a></li>
|
||
<li><a href="#fundamentals-5">Fundamentals</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#deployment-models-1">Deployment Models</a><ul>
|
||
<li><a href="#orchestration-options">Orchestration Options</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering-principles-1">Software Engineering Principles</a><ul>
|
||
<li><a href="#developer-workflow">Developer Workflow</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#testing-and-reliability-1">Testing and Reliability</a><ul>
|
||
<li><a href="#fault-tolerance">Fault Tolerance</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#operations">Operations</a></li>
|
||
<li><a href="#disaster-recovery">Disaster Recovery</a><ul>
|
||
<li><a href="#cloud-native-1">Cloud-Native</a></li>
|
||
<li><a href="#devops-1">DevOps</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#orchestration-2">Orchestration</a></li>
|
||
<li><a href="#kubernetes-2">Kubernetes</a><ul>
|
||
<li><a href="#anti-patterns-3">Anti-Patterns</a></li>
|
||
<li><a href="#dependency-isolation">Dependency Isolation</a></li>
|
||
<li><a href="#microservices-6">Microservices</a></li>
|
||
<li><a href="#paradigms-1">Paradigms</a></li>
|
||
<li><a href="#prerequisites">Prerequisites</a></li>
|
||
<li><a href="#processes">Processes</a></li>
|
||
<li><a href="#twelve-factor-app-1">Twelve-Factor App</a></li>
|
||
<li><a href="#workloads">Workloads</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#platform-engineering-3">Platform Engineering</a></li>
|
||
<li><a href="#paas-solutions">PaaS Solutions</a><ul>
|
||
<li><a href="#market-shifts">Market Shifts</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#reference-architectures">Reference Architectures</a><ul>
|
||
<li><a href="#aws">AWS</a></li>
|
||
<li><a href="#azure">Azure</a></li>
|
||
<li><a href="#gcp">GCP</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#self-service">Self-Service</a><ul>
|
||
<li><a href="#case-studies-1">Case Studies</a></li>
|
||
<li><a href="#concepts-1">Concepts</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#service-catalogs">Service Catalogs</a><ul>
|
||
<li><a href="#microservices-governance">Microservices Governance</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#professional-development-2">Professional Development</a></li>
|
||
<li><a href="#career-guidance">Career Guidance</a></li>
|
||
<li><a href="#reliability-engineering">Reliability Engineering</a></li>
|
||
<li><a href="#resilience-patterns-1">Resilience Patterns</a><ul>
|
||
<li><a href="#infrastructure-stability">Infrastructure Stability</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#security">Security</a></li>
|
||
<li><a href="#software-protection">Software Protection</a><ul>
|
||
<li><a href="#obfuscation">Obfuscation</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-architecture">Software Architecture</a></li>
|
||
<li><a href="#application-modernization-1">Application Modernization</a><ul>
|
||
<li><a href="#legacy-migration">Legacy Migration</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#event-driven-systems">Event-Driven Systems</a><ul>
|
||
<li><a href="#asynchronous-messaging">Asynchronous Messaging</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#microservices-7">Microservices</a><ul>
|
||
<li><a href="#decomposition-patterns">Decomposition Patterns</a></li>
|
||
<li><a href="#design-patterns-4">Design Patterns</a></li>
|
||
<li><a href="#distributed-transactions">Distributed Transactions</a></li>
|
||
<li><a href="#maturity-models">Maturity Models</a></li>
|
||
<li><a href="#monolith-transition">Monolith Transition</a></li>
|
||
<li><a href="#technology-selection">Technology Selection</a></li>
|
||
<li><a href="#value-proposition-1">Value Proposition</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#modernization-2">Modernization</a><ul>
|
||
<li><a href="#strangler-pattern">Strangler Pattern</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#monoliths-2">Monoliths</a><ul>
|
||
<li><a href="#modular-monolith">Modular Monolith</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-delivery">Software Delivery</a></li>
|
||
<li><a href="#devops-2">DevOps</a><ul>
|
||
<li><a href="#industry-trends-1">Industry Trends</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering-2">Software Engineering</a></li>
|
||
<li><a href="#architecture-patterns-2">Architecture Patterns</a><ul>
|
||
<li><a href="#microservices-8">Microservices</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#education-1">Education</a><ul>
|
||
<li><a href="#systems-programming">Systems Programming</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#full-stack-fundamentals">Full-Stack Fundamentals</a><ul>
|
||
<li><a href="#architectural-roles">Architectural Roles</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#performance-optimization">Performance Optimization</a><ul>
|
||
<li><a href="#system-architecture">System Architecture</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#web-development">Web Development</a><ul>
|
||
<li><a href="#nodejs">NodeJS</a></li>
|
||
</ul>
|
||
</li>
|
||
<li><a href="#software-engineering-practices">Software Engineering Practices</a></li>
|
||
<li><a href="#developer-productivity">Developer Productivity</a><ul>
|
||
<li><a href="#roadmaps">Roadmaps</a></li>
|
||
<li><a href="#toolkits">Toolkits</a></li>
|
||
</ul>
|
||
</li>
|
||
</ol>
|
||
<h2 id="vision-2026">Vision 2026<a class="headerlink" href="#vision-2026" title="Permanent link">¶</a></h2>
|
||
<div class="admonition quote">
|
||
<p class="admonition-title">The Evolution of Autonomy</p>
|
||
<p>From manual curation to agentic intelligence.</p>
|
||
</div>
|
||
<h3 id="ecosystem-map">Ecosystem Map<a class="headerlink" href="#ecosystem-map" title="Permanent link">¶</a></h3>
|
||
<pre class="mermaid"><code>graph TD
|
||
A[Foundations] --> B[AI & Intelligence]
|
||
A --> C[Hardened Infra]
|
||
B --> D[Agentic Curation]
|
||
C --> E[Enterprise Stability]
|
||
D --> F[Nubenetes Portal]
|
||
E --> F</code></pre>
|
||
<h2 id="application-modernization">Application Modernization<a class="headerlink" href="#application-modernization" title="Permanent link">¶</a></h2>
|
||
<h3 id="monolith-to-microservices">Monolith to Microservices<a class="headerlink" href="#monolith-to-microservices" title="Permanent link">¶</a></h3>
|
||
<h4 id="automated-refactoring">Automated Refactoring<a class="headerlink" href="#automated-refactoring" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://vfunction.com">vFunction</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An advanced, AI-driven application modernization platform designed to refactor monolithic Java applications. Live Grounding verifies that vFunction dynamically tracks codebase interactions and dependency call trees to generate optimal, decoupled microservices.</li>
|
||
</ul>
|
||
<h4 id="case-studies">Case Studies<a class="headerlink" href="#case-studies" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://thenewstack.io/vfunction-transforms-monolithic-java-to-microservices">thenewstack.io: vFunction Transforms Monolithic Java to Microservices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Deep-dive case study covering how vFunction automates the decomposition of complex legacy Java application structures into modern cloud-native APIs. Illustrates mapping monolithic complexity to decoupled Domain-Driven Design (DDD) boundaries.</li>
|
||
</ul>
|
||
<h4 id="guides">Guides<a class="headerlink" href="#guides" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://devops.com/transform-legacy-java-apps-to-microservices">devops.com: Best of 2021 – Transform Legacy Java Apps to Microservices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Strategic and tactical guide addressing the decomposition of legacy enterprise Java systems. Emphasizes modern automated refactoring engines to accurately map boundaries, mitigating migration risks while speeding up time-to-production.</li>
|
||
</ul>
|
||
<h2 id="architecture">Architecture<a class="headerlink" href="#architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="apis">APIs<a class="headerlink" href="#apis" title="Permanent link">¶</a></h3>
|
||
<h4 id="protocols">Protocols<a class="headerlink" href="#protocols" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://nordicapis.com/5-protocols-for-event-driven-api-architectures">nordicapis.com: 5 Protocols For Event-Driven API Architectures 🌟🌟🌟</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores five critical protocols enabling asynchronous API communications: WebSockets, Webhooks, REST Hooks, Pub-Sub models, and Server-Sent Events (SSE). Details how eliminating polling reduces compute overhead and saves bandwidth.</li>
|
||
</ul>
|
||
<h3 id="best-practices">Best Practices<a class="headerlink" href="#best-practices" title="Permanent link">¶</a></h3>
|
||
<h4 id="eda">EDA<a class="headerlink" href="#eda" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://aws.amazon.com/blogs/architecture/best-practices-for-implementing-event-driven-architectures-in-your-organization">aws.amazon.com: Best practices for implementing event-driven architectures in your organization</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--secondary'>[CASE STUDY]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive enterprise whitepaper on establishing organizational patterns for event-driven environments. Focuses on schema management, dead-letter queue (DLQ) operations, idempotency, and distributed tracing strategies.</li>
|
||
</ul>
|
||
<h3 id="data-management">Data Management<a class="headerlink" href="#data-management" title="Permanent link">¶</a></h3>
|
||
<h4 id="patterns">Patterns<a class="headerlink" href="#patterns" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.pluralsight.com/resources/blog/business-and-leadership/sharing-data-in-the-cloud-four-patterns-everyone-should-know">acloudguru.com: Sharing data in the cloud: 4 patterns you should know</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines four distinct cloud-native patterns for shared-data architectures. Evaluates data virtualization, API-driven delivery, direct database sharing, and messaging queues based on security and real-time synchronization requirements.</li>
|
||
</ul>
|
||
<h3 id="microservices">Microservices<a class="headerlink" href="#microservices" title="Permanent link">¶</a></h3>
|
||
<h4 id="fundamentals">Fundamentals<a class="headerlink" href="#fundamentals" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://redis.io/blog/microservice-architecture-key-concepts">redis.com: Microservice Architecture Key Concepts</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive breakdown of core microservices concepts including bounded contexts, service boundaries, and state isolation. Highlights why Redis is a logical fit for high-speed cache and pub-sub across decoupled domains.</li>
|
||
</ul>
|
||
<h3 id="patterns-1">Patterns (1)<a class="headerlink" href="#patterns-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="eda-1">EDA (1)<a class="headerlink" href="#eda-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.kurrent.io/blog/service-oriented-architecture-vs-event-driven-architecture">eventstore.com: Service-Oriented Architecture vs Event-Driven Architecture 🌟</a> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Comprehensively contrasts the request-response paradigm of traditional SOA with the asynchronous, log-centric model of Event-Driven Architectures. Highlights Event Store and event sourcing patterns for strict audit trails.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.equalexperts.com/blog/tech-focus/event-driven-architecture-the-good-the-bad-and-the-ugly">equalexperts.com: Event driven architecture: the good, the bad, and the ugly 🌟</a> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the practical realities of deploying EDA at scale. Evaluates benefits (decoupling, high performance) against complexities (distributed debugging, out-of-order execution, schema evolution management).</li>
|
||
<li><strong>(2017)</strong> <a href="https://martinfowler.com/articles/201701-event-driven.html">martinfowler.com: What do you mean by “Event-Driven”? 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Martin Fowler clarifies the ambiguous term 'Event-Driven'. Outlines four distinct patterns: Event Notification, Event-Carried State Transfer, Event Sourcing, and CQRS, detailing their operational advantages and pain points.</li>
|
||
<li><strong>(2023)</strong> <a href="https://dev.to/aws-builders/un-modelo-de-eda-event-driven-architectures-4d9f">dev.to/aws-builders: Un Modelo de EDA: Event Driven Architectures</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Una guía detallada sobre cómo implementar arquitecturas dirigidas por eventos (EDA) utilizando servicios nativos de AWS como EventBridge, SNS, SQS y Lambda para lograr un desacoplamiento de componentes de backend robusto.</li>
|
||
</ul>
|
||
<h4 id="evolution">Evolution<a class="headerlink" href="#evolution" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.designgurus.io/blog/monolithic-service-oriented-microservice-architecture">designgurus.io: Monolithic vs. Service-Oriented vs. Microservice Architecture: Top Architectural Design Patterns</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares monolithic systems, Enterprise Service Bus (ESB)-based SOAs, and decoupled microservices. Identifies modern trade-offs such as operational complexity, deployment velocity, and distributed transaction management.</li>
|
||
</ul>
|
||
<h4 id="monoliths">Monoliths<a class="headerlink" href="#monoliths" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://devops.com/8-hot-takes-will-we-see-a-monolithic-renaissance">devops.com: 8 Hot Takes: Will We See a Monolithic Renaissance?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the potential return to macro-services or modular monoliths to address the operational overhead, network latency, and complex debugging of over-engineered microservice fleets.</li>
|
||
</ul>
|
||
<h4 id="twelve-factor-app">Twelve-Factor App<a class="headerlink" href="#twelve-factor-app" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://architecturenotes.co/p/12-factor-app-revisited">architecturenotes.co: 12 Factor App Revisited</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Critically evaluates how classic 12-Factor concepts have aged. Addresses the challenges of serverless scaling, API-first interfaces, distributed telemetry, and modern build/release pipelines.</li>
|
||
<li><strong>(2021)</strong> <a href="https://opensource.com/article/21/11/open-source-12-factor-app-methodology">opensource.com: An open source developer's guide to 12-Factor App methodology</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Analyzes the application of 12-Factor methodology to open-source project standards. Highlights maintaining statelessness, dependency isolation, and configuration separation to simplify multi-environment testing and distribution.</li>
|
||
</ul>
|
||
<h3 id="saas">SaaS<a class="headerlink" href="#saas" title="Permanent link">¶</a></h3>
|
||
<h4 id="multi-tenancy">Multi-Tenancy<a class="headerlink" href="#multi-tenancy" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.scaleway.com/en/blog/saas-multi-tenant-vs-multi-instance-architectures">blog.scaleway.com: SaaS Solutions - What is the difference between a multi-instance and a multi-tenant architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares multi-instance setups (dedicated systems per tenant) against multi-tenant models (shared compute/database with strict software isolation). Examines resource scaling, security boundaries, and noisy neighbor challenges.</li>
|
||
</ul>
|
||
<h3 id="technical-debt">Technical Debt<a class="headerlink" href="#technical-debt" title="Permanent link">¶</a></h3>
|
||
<h4 id="microservices-1">Microservices (1)<a class="headerlink" href="#microservices-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.infoq.com/articles/managing-technical-debt-microservices">infoq.com: Managing Technical Debt in a Microservice Architecture</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Investigates the specific vectors of technical debt in microservices, including library drift, API versioning overhead, and domain-model fragmentation. Offers architectural rules of thumb to control distributed sprawl.</li>
|
||
</ul>
|
||
<h4 id="orchestration">Orchestration<a class="headerlink" href="#orchestration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://stackoverflow.blog/2021/05/19/rethinking-system-architecture-can-kubernetes-help-to-solve-rewrite-anxiety">stackoverflow.blog: Using Kubernetes to rethink your system architecture and ease technical debt 🌟</a> 🌟 <span class='md-tag md-tag--critical'>[LEGACY]</span> — Discusses utilizing a migration to Kubernetes as a strategic catalyst to refactor legacy monoliths. Reorganizes monolithic systems into decoupled containers, successfully lowering long-term architectural tech debt.</li>
|
||
</ul>
|
||
<h2 id="architecture-patterns">Architecture Patterns<a class="headerlink" href="#architecture-patterns" title="Permanent link">¶</a></h2>
|
||
<h3 id="microservices-2">Microservices (2)<a class="headerlink" href="#microservices-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="cloud-native-infrastructure">Cloud-Native Infrastructure<a class="headerlink" href="#cloud-native-infrastructure" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.techerati.com/features-hub/microservices-in-the-cloud-native-era">techerati.com: Microservices in the Cloud-Native Era</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores the strategic paradigm shift toward microservices as the de facto structural archetype for scalable cloud platforms. It dissects operational complexities including traffic routing, discovery mechanisms, and failure domain containment through circuit-breakers. A vital read for architects planning monolithic-to-microservices migrations under modern Kubernetes-centric infrastructures.</li>
|
||
</ul>
|
||
<h2 id="artificial-intelligence-and-ml">Artificial Intelligence and ML<a class="headerlink" href="#artificial-intelligence-and-ml" title="Permanent link">¶</a></h2>
|
||
<h3 id="machine-learning-engineering">Machine Learning Engineering<a class="headerlink" href="#machine-learning-engineering" title="Permanent link">¶</a></h3>
|
||
<h4 id="python-ecosystem">Python Ecosystem<a class="headerlink" href="#python-ecosystem" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://sloboda-studio.com/blog/python-tools-for-machine-learning">sloboda-studio.com: Python Tools for Machine Learning</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Overview of essential Python machine learning libraries and toolchains. Details NumPy, Pandas, Scikit-Learn, and TensorFlow integration patterns, showing developers how to bridge data science models with scalable microservices runtimes.</li>
|
||
</ul>
|
||
<h2 id="business-architecture">Business Architecture<a class="headerlink" href="#business-architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="digital-transformation">Digital Transformation<a class="headerlink" href="#digital-transformation" title="Permanent link">¶</a></h3>
|
||
<h4 id="cultural-dynamics">Cultural Dynamics<a class="headerlink" href="#cultural-dynamics" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.lavanguardia.com/economia/20201014/484036217179/transformacion-digital-empresas-foncillas-pf-video-seo-lv.html">lavanguardia.com: Por qué la transformación digital es mentira 🌟</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Un análisis crítico sobre las falacias que rodean el concepto de 'transformación digital' en el mundo corporativo. El autor argumenta que la tecnología por sí sola no arregla procesos rotos, señalando que el verdadero cambio radica en la reestructuración cultural y la optimización organizativa.</li>
|
||
</ul>
|
||
<h3 id="organizational-structure">Organizational Structure<a class="headerlink" href="#organizational-structure" title="Permanent link">¶</a></h3>
|
||
<h4 id="devops-culture">DevOps Culture<a class="headerlink" href="#devops-culture" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://thenewstack.io/study-silos-are-chief-impediment-to-it-and-business-value">thenewstack.io: Study: Silos Are the Chief Impediment to IT and Business Value</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes survey data proving how organizational and technological silos directly impede software delivery velocity and downstream business value. Argues that introducing modern container technology without breaking down departmental silos leads to failed platform transformations.</li>
|
||
</ul>
|
||
<h2 id="career-development">Career Development<a class="headerlink" href="#career-development" title="Permanent link">¶</a></h2>
|
||
<h3 id="architect-strategy">Architect Strategy<a class="headerlink" href="#architect-strategy" title="Permanent link">¶</a></h3>
|
||
<h4 id="skillsets">Skillsets<a class="headerlink" href="#skillsets" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.redhat.com/en/blog/from-sysadmin-to-architect">redhat.com: 5 strategies to shift your career from sysadmin to architect</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Maps professional development strategies for system administrators transitioning to IT architect roles. Emphasizes system-level thinking, mastering cloud-native paradigms, understanding business metrics, and cultivating strong communication skills.</li>
|
||
</ul>
|
||
<h2 id="cloud-architecture">Cloud Architecture<a class="headerlink" href="#cloud-architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="cloud-strategy">Cloud Strategy<a class="headerlink" href="#cloud-strategy" title="Permanent link">¶</a></h3>
|
||
<h4 id="design-anti-patterns">Design Anti-patterns<a class="headerlink" href="#design-anti-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoworld.com: 3 cloud architecture mistakes we all make, but shouldn't</summary>
|
||
<p><strong><a href="https://www.infoworld.com/article/2264771/3-cloud-architecture-mistakes-we-all-make-but-shouldnt.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Highlights three widespread cloud engineering anti-patterns: lift-and-shift migration without modernization, ignoring structural egress cost-profiles, and blindly utilizing proprietary managed services that lead to irreversible vendor lock-in.</p>
|
||
</details>
|
||
<h4 id="migration-methodology">Migration Methodology<a class="headerlink" href="#migration-methodology" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>cloudpundit.com: Don’t boil the ocean to create your cloud 🌟</summary>
|
||
<p><strong><a href="https://cloudpundit.com/2020/09/22/dont-boil-the-ocean-to-create-your-cloud">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Advocates for an incremental, pragmatic approach to cloud migration and platform construction. Warns against the architectural antipattern of designing an overengineered, all-encompassing private or public cloud solution on day one instead of starting with minimal viable platforms.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Prepare to Adopt the Cloud: A 10-Step Cloud Migration Checklist 🌟</summary>
|
||
<p><strong><a href="https://thenewstack.io/prepare-to-adopt-the-cloud-a-10-step-cloud-migration-checklist">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A comprehensive operational checklist for transitioning enterprise applications to public cloud systems. Key steps encompass assessing application dependencies, cost-modeling, security boundaries, containerization feasibility, and shifting deployment pipelines to modern CI/CD tooling.</p>
|
||
</details>
|
||
<h3 id="cloud-native">Cloud-Native<a class="headerlink" href="#cloud-native" title="Permanent link">¶</a></h3>
|
||
<h4 id="design-patterns">Design Patterns<a class="headerlink" href="#design-patterns" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://capstonec.com/2020/10/08/cloud-native-app-architecture-patterns">capstonec.com: You Will Love These Cloud-native App Architecture Patterns 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Investigates key structural patterns that define modern cloud-native systems, focusing on twelve-factor application rules, API-first delivery, resilient circuit breakers, and decoupling persistent storage systems from execution units.</li>
|
||
</ul>
|
||
<h3 id="hybrid-cloud-strategy">Hybrid Cloud Strategy<a class="headerlink" href="#hybrid-cloud-strategy" title="Permanent link">¶</a></h3>
|
||
<h4 id="market-trends">Market Trends<a class="headerlink" href="#market-trends" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://enterprisersproject.com/article/2021/1/5-hybrid-cloud-trends-2021">enterprisersproject.com: 5 hybrid cloud trends to watch in 2021</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Identifies key industry shifts in the hybrid and multi-cloud landscape, focusing on managed hybrid control planes, unified security tooling, and the integration of edge environments with central public cloud architectures to meet data compliance requirements.</li>
|
||
</ul>
|
||
<h3 id="migration">Migration<a class="headerlink" href="#migration" title="Permanent link">¶</a></h3>
|
||
<h4 id="hands-on">Hands-On<a class="headerlink" href="#hands-on" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.pluralsight.com/resources/blog/cloud/3-ways-to-practice-migrating-workloads-to-the-cloud">acloudguru.com: 3 ways to practice migrating workloads to the cloud</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides instructional path frameworks for developers looking to gain hands-on migration experience. Focuses on setting up mock environments, replicating on-premise infrastructure in sandboxes, and utilizing provider-native migration automation tools.</li>
|
||
</ul>
|
||
<h4 id="methodology">Methodology<a class="headerlink" href="#methodology" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://blog.pragmaticengineer.com/typical-migration-approaches">blog.pragmaticengineer.com: Migrations Done Well: Typical Migration Approaches</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Written by Gergely Orosz, this deep-dive highlights technical planning and execution strategies for complex system migrations. Discusses mitigating dual-write issues, rollback preparations, and incremental phased cutovers to manage operational risk.</li>
|
||
</ul>
|
||
<h4 id="strategies">Strategies<a class="headerlink" href="#strategies" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.forbes.com/sites/googlecloud/2021/10/27/3-approaches-to-a-better-cloud-migration">forbes.com: 3 Approaches To A Better Cloud Migration</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Synthesizes high-level corporate strategies for executing cloud migrations. It contrasts rehosting (lift-and-shift), platform optimization (replatforming), and cloud-native rebuilding (refactoring) along security, speed, and cost parameters.</li>
|
||
</ul>
|
||
<h3 id="modernization">Modernization<a class="headerlink" href="#modernization" title="Permanent link">¶</a></h3>
|
||
<h4 id="reactive-systems">Reactive Systems<a class="headerlink" href="#reactive-systems" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://akka.io">lightbend.com: From Java EE To Cloud Native: The End Of The Heavyweight Era 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Lightbend presents the transition of traditional Java enterprise architectures to reactive, cloud-native frameworks (like Akka/Pekko). Evaluates high-concurrency patterns, asynchronous messaging, and horizontal scale-out benefits over synchronous architectures.</li>
|
||
</ul>
|
||
<h3 id="multi-cloud-strategy">Multi-Cloud Strategy<a class="headerlink" href="#multi-cloud-strategy" title="Permanent link">¶</a></h3>
|
||
<h4 id="data-management-1">Data Management (1)<a class="headerlink" href="#data-management-1" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: The 4 Definitions of Multicloud: Part 1 — Data Portability</summary>
|
||
<p><strong><a href="https://thenewstack.io/the-4-definitions-of-multicloud-part-1-data-portability">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Evaluates the concept of data portability within multi-cloud configurations. Focuses on the architectural mechanisms of synchronizing state across varying proprietary cloud databases, minimizing network egress latency, and utilizing modern cloud-native storage interfaces (CSI) for storage flexibility.</p>
|
||
</details>
|
||
<h4 id="network-and-security">Network and Security<a class="headerlink" href="#network-and-security" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Multicloud Challenges and Solutions</summary>
|
||
<p><strong><a href="https://thenewstack.io/multicloud-challenges-and-solutions">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Details the immense architectural friction points of multi-cloud setups, from inconsistent IAM paradigms and distinct networking topologies to high egress fees. Reviews operational abstractions like cross-cloud controllers and unified policy management to reconcile these differences.</p>
|
||
</details>
|
||
<h4 id="resilience-patterns">Resilience Patterns<a class="headerlink" href="#resilience-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Multicloud Paves the Way for Cloud Native Resiliency Models</summary>
|
||
<p><strong><a href="https://thenewstack.io/multicloud-paves-the-way-for-cloud-native-resiliency-models">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Examines how a multi-cloud topology acts as the ultimate disaster recovery tier for highly critical modern platforms. Analyzes how active-active deployments across distinct public cloud providers mitigate regional or cloud-wide service provider outages.</p>
|
||
</details>
|
||
<h3 id="private-cloud">Private Cloud<a class="headerlink" href="#private-cloud" title="Permanent link">¶</a></h3>
|
||
<h4 id="hybrid-cloud-strategy-1">Hybrid Cloud Strategy (1)<a class="headerlink" href="#hybrid-cloud-strategy-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://thenewstack.io/google-and-oracle-cloud-adoption-doubles-among-enterprises-3">thenewstack.io: Are Private Clouds Proliferating?</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines enterprise hybrid cloud data, highlighting why many organizations continue to maintain, build, or modernize private clouds alongside public cloud footprints. Looks at compliance, data sovereignty, predictable workloads, and hybrid architectures (e.g. Anthos, Outposts).</li>
|
||
</ul>
|
||
<h3 id="professional-development">Professional Development<a class="headerlink" href="#professional-development" title="Permanent link">¶</a></h3>
|
||
<h4 id="career-engineering">Career Engineering<a class="headerlink" href="#career-engineering" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.ituser.es/opinion/2020/07/las-principales-habilidades-que-un-arquitecto-cloud-necesita-para-triunfar">ituser.es: Las principales habilidades que un arquitecto cloud necesita para triunfar</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analiza las competencias técnicas e interpersonales críticas para un arquitecto cloud en el panorama empresarial moderno. Destaca la necesidad de dominar no solo arquitecturas multinube, automatización con IaC y seguridad, sino también habilidades de comunicación para traducir decisiones tecnológicas en valor de negocio.</li>
|
||
</ul>
|
||
<h3 id="strategy">Strategy<a class="headerlink" href="#strategy" title="Permanent link">¶</a></h3>
|
||
<h4 id="multi-cloud-benefits">Multi-Cloud Benefits<a class="headerlink" href="#multi-cloud-benefits" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.softwebsolutions.com/resources/multi-cloud-adoption-strategy">softwebsolutions.com: Why enterprises need to adopt a multi-cloud strategy</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the business and technical drivers for enterprise multi-cloud adoption, including risk mitigation, disaster recovery, avoiding vendor lock-in, and optimizing workloads across disparate public cloud provider environments.</li>
|
||
</ul>
|
||
<h4 id="multi-cloud-decisions">Multi-Cloud Decisions<a class="headerlink" href="#multi-cloud-decisions" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://architectelevator.com/cloud/hybrid-multi-cloud">architectelevator.com: Multi Cloud Architecture: Decisions and Options</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyses strategic multi-cloud architectural decisions. Gregor Hohpe presents frameworks to distinguish between cloud integration, portability, and distribution, highlighting that multi-cloud should be a deliberate architectural choice rather than a default risk-mitigation strategy.</li>
|
||
</ul>
|
||
<h2 id="cloud-architecture-and-infrastructure-strategy">Cloud Architecture and Infrastructure Strategy<a class="headerlink" href="#cloud-architecture-and-infrastructure-strategy" title="Permanent link">¶</a></h2>
|
||
<h3 id="application-design">Application Design<a class="headerlink" href="#application-design" title="Permanent link">¶</a></h3>
|
||
<h4 id="horizontal-scaling">Horizontal Scaling<a class="headerlink" href="#horizontal-scaling" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>yellow.systems: How to Make a Scalable Web Application: Architecture, Technologies, Cost 🌟</summary>
|
||
<p><strong><a href="https://yellow.systems/blog/how-to-build-a-scalable-web-application">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A holistic technical guide detailing architectural design patterns necessary to construct web systems capable of scaling to high volumes of traffic. Covers backend optimization, load balancing configurations, database sharding, caching layers, and the architectural shift from single-instance services to highly available distributed designs.</p>
|
||
</details>
|
||
<h4 id="system-design-patterns">System Design Patterns<a class="headerlink" href="#system-design-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>bytebytego.com: System Design - Scale From Zero To Millions Of Users 🌟</summary>
|
||
<p><strong><a href="https://bytebytego.com/courses/system-design-interview/scale-from-zero-to-millions-of-users">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A structured breakdown of modern system scaling, illustrating how a single database configuration evolves into a multi-tiered global architecture. Covers key mechanics like database replication, global CDN routing, horizontal scaling of stateless application nodes, and distributed cache deployment.</p>
|
||
</details>
|
||
<h3 id="cost-optimization-and-finops">Cost Optimization and FinOps<a class="headerlink" href="#cost-optimization-and-finops" title="Permanent link">¶</a></h3>
|
||
<h4 id="efficiency-bottlenecks">Efficiency Bottlenecks<a class="headerlink" href="#efficiency-bottlenecks" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>zesty.co: 10 Cloud Deficiencies You Should Know</summary>
|
||
<p><strong><a href="https://zesty.co/blog/10-cloud-deficiencies">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Highlights ten widespread cloud configuration deficiencies including over-provisioning of EBS volumes, orphaned compute instances, and poor auto-scaling metrics. Outlines practical mitigations for cloud-cost inflation (FinOps) and suboptimal performance caused by rigid resource constraints.</p>
|
||
</details>
|
||
<h3 id="deployment-models">Deployment Models<a class="headerlink" href="#deployment-models" title="Permanent link">¶</a></h3>
|
||
<h4 id="comparison">Comparison<a class="headerlink" href="#comparison" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.pluralsight.com/resources/blog/business-and-leadership/public-cloud-vs-private-cloud-whats-the-difference">acloudguru.com: Public cloud vs private cloud: What’s the difference? 🌟</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demystifies the core operational, fiscal, and regulatory distinctions between public and private cloud models. The article provides a structured baseline for cloud engineering teams to evaluate infrastructure capital expenditures (CapEx) against operational expenditures (OpEx) based on resource control needs.</li>
|
||
</ul>
|
||
<h4 id="hybrid-and-private-cloud">Hybrid and Private Cloud<a class="headerlink" href="#hybrid-and-private-cloud" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Private vs. Public Cloud: How Kubernetes Shifts the Balance</summary>
|
||
<p><strong><a href="https://thenewstack.io/private-vs-public-cloud-how-kubernetes-shifts-the-balance">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Analyzes the architectural shift enabled by Kubernetes in bridging the gap between private and public cloud environments. By decoupling applications from underlying infrastructure, Kubernetes acts as an abstraction layer that permits consistent deployments across heterogeneous footprints, optimizing operational costs and security posture.</p>
|
||
</details>
|
||
<h3 id="high-availability">High Availability<a class="headerlink" href="#high-availability" title="Permanent link">¶</a></h3>
|
||
<h4 id="core-patterns">Core Patterns<a class="headerlink" href="#core-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>towardsdatascience.com: 3 High Availability Cloud Concepts You Should Know</summary>
|
||
<p><strong><a href="https://towardsdatascience.com/3-high-availability-cloud-concepts-you-should-know-93f3bab2cb4a">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Explores three fundamental high-availability cloud strategies: active-active vs active-passive configurations, geo-redundant database replication, and zero-downtime DNS-routed failovers. Discusses mathematical SLA models and network traffic planning required to achieve high service uptime.</p>
|
||
</details>
|
||
<h4 id="multi-region-deployments">Multi-Region Deployments<a class="headerlink" href="#multi-region-deployments" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>engineering.monday.com: monday.com’s Multi-Regional Architecture: A Deep Dive</summary>
|
||
<p><strong><a href="https://engineering.monday.com/monday-coms-multi-regional-architecture-a-deep-dive">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A real-world architectural dissection of how monday.com implemented a highly resilient, multi-regional cloud strategy to improve latency and adhere to strict regional data regulations. Explains state replication strategies, request routing optimizations, and database scaling bottlenecks encountered during global scaling.</p>
|
||
</details>
|
||
<h3 id="market-trends-1">Market Trends (1)<a class="headerlink" href="#market-trends-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="open-source-business-models">Open Source Business Models<a class="headerlink" href="#open-source-business-models" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.websiteplanet.com/blog/what-is-open-source-software/?geo=us&device=desktop">websiteplanet.com: What’s Open Source Software + How It Makes Money 2022</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details the monetization mechanics driving open-source software (OSS) ecosystems, covering models like open-core, dual-licensing, and cloud hosting. Helps engineering leaders assess the long-term sustainability and licensing risks associated with critical software dependencies.</li>
|
||
</ul>
|
||
<h3 id="migration-and-modernization">Migration and Modernization<a class="headerlink" href="#migration-and-modernization" title="Permanent link">¶</a></h3>
|
||
<h4 id="enterprise-solutions">Enterprise Solutions<a class="headerlink" href="#enterprise-solutions" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>deloitte.com/de: EMEA Center of Excellence for Application Modernization and Migration</summary>
|
||
<p><strong><a href="https://www.deloitte.com/de/de/services/consulting/services/center-of-excellence-application-modernization.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Details the strategy of Deloitte's EMEA Center of Excellence for enterprise application modernization. Explains how consulting frameworks assess legacy codebases, evaluate migration paths, and apply cloud-native solutions to modernize large-scale systems.</p>
|
||
</details>
|
||
<h4 id="planning-resources">Planning Resources<a class="headerlink" href="#planning-resources" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>simform.com: Cloud Migration ebook</summary>
|
||
<p><strong><a href="https://www.simform.com/cloud-migration-ebook">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A programmatic playbook detailing the methodologies of migrating legacy infrastructure into public or hybrid cloud topologies. It maps the standard 'R' migration frameworks (Rehost, Replatform, Refactor, etc.), evaluating execution risks, database cutover strategies, and cost-modeling paradigms.</p>
|
||
</details>
|
||
<h3 id="modern-architectural-paradigms">Modern Architectural Paradigms<a class="headerlink" href="#modern-architectural-paradigms" title="Permanent link">¶</a></h3>
|
||
<h4 id="mach-architecture">MACH Architecture<a class="headerlink" href="#mach-architecture" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Transform and Future-Proof Your Architecture with MACH</summary>
|
||
<p><strong><a href="https://thenewstack.io/transform-and-future-proof-your-architecture-with-mach">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Introduces MACH (Microservices, API-first, Cloud-native, Headless) as a modern enterprise blueprint for agile digital experience platforms. This modular paradigm allows businesses to scale individual pieces independently, facilitating seamless integrations and preventing monolithic vendor lock-in.</p>
|
||
</details>
|
||
<h3 id="multi-cloud-strategy-1">Multi-Cloud Strategy (1)<a class="headerlink" href="#multi-cloud-strategy-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="architecture-designs">Architecture Designs<a class="headerlink" href="#architecture-designs" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>simform.com: 6 Multi-Cloud Architecture Designs for an Effective Cloud Strategy 🌟</summary>
|
||
<p><strong><a href="https://www.simform.com/blog/multi-cloud-architecture">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Evaluates six distinct multi-cloud topologies including Multi-Cloud Disaster Recovery, Cloud-to-Cloud Federation, and Split-Brain architectures. The guide explains practical ingress routing, state synchronization, and database replication patterns needed to sustain highly resilient, cross-cloud operations.</p>
|
||
</details>
|
||
<h4 id="architecture-planning">Architecture Planning<a class="headerlink" href="#architecture-planning" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>simform.com: What is Multi Cloud? Why you Need a Multi Cloud Strategy?</summary>
|
||
<p><strong><a href="https://www.simform.com/blog/multi-cloud-strategy">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Decouples the business and technical drivers of multi-cloud architectures, focusing on risk mitigation, vendor lock-in avoidance, and geographical redundancy. The guide contrasts hybrid deployments with multi-cloud topologies to establish clear decision matrices for technical architects.</p>
|
||
</details>
|
||
<h4 id="business-drivers">Business Drivers<a class="headerlink" href="#business-drivers" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://thenewstack.io/reasons-to-opt-for-a-multicloud-strategy">thenewstack.io: Reasons to Opt for a Multicloud Strategy</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines key operational drivers supporting a deliberate multi-cloud migration strategy, centering on geographic expansion, regional regulatory mandates, and optimized billing leverage. The resource emphasizes treating multi-cloud as a strategic framework to optimize application delivery across diverse vendor strengths.</li>
|
||
</ul>
|
||
<h3 id="storage-and-hybrid-systems">Storage and Hybrid Systems<a class="headerlink" href="#storage-and-hybrid-systems" title="Permanent link">¶</a></h3>
|
||
<h4 id="topology-comparison">Topology Comparison<a class="headerlink" href="#topology-comparison" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>blog.min.io: Mono Clouds vs Multi-Clouds & Hybrid Clouds</summary>
|
||
<p><strong><a href="https://www.min.io/blog">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Details the comparative trade-offs between mono-cloud, multi-cloud, and hybrid cloud topologies from an object storage and data gravity perspective. MinIO highlights the critical role of data portability and standardized APIs (S3) in enabling architectural freedom across multi-cloud footprints.</p>
|
||
</details>
|
||
<h2 id="cloud-infrastructure">Cloud Infrastructure<a class="headerlink" href="#cloud-infrastructure" title="Permanent link">¶</a></h2>
|
||
<h3 id="automation">Automation<a class="headerlink" href="#automation" title="Permanent link">¶</a></h3>
|
||
<h4 id="concepts">Concepts<a class="headerlink" href="#concepts" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://thenewstack.io/what-is-cloud-automation-and-how-does-it-benefit-it-teams">thenewstack.io: What Is Cloud Automation and How Does It Benefit IT Teams? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demystifies cloud automation paradigms, describing how automated resource provisioning, scaling, and configuration reduce operational overhead and human error. Key focus is placed on programmatic API orchestration and infrastructure-as-code.</li>
|
||
</ul>
|
||
<h3 id="devops">DevOps<a class="headerlink" href="#devops" title="Permanent link">¶</a></h3>
|
||
<h4 id="infrastructure-abstraction">Infrastructure Abstraction<a class="headerlink" href="#infrastructure-abstraction" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://devops.com/infrastructure-abstraction-will-be-key-to-managing-multi-cloud">devops.com: Infrastructure Abstraction Will Be Key to Managing Multi-Cloud</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores how infrastructure-as-code (IaC) and Kubernetes-driven abstraction layers decouple workloads from underlying cloud provider primitives. This design pattern reduces complexity, minimizes lock-in, and enforces consistent deployment methodologies.</li>
|
||
</ul>
|
||
<h3 id="hybrid-cloud">Hybrid Cloud<a class="headerlink" href="#hybrid-cloud" title="Permanent link">¶</a></h3>
|
||
<h4 id="management-tools">Management Tools<a class="headerlink" href="#management-tools" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.redhat.com/en/blog/hybrid-cloud-management-tools">redhat.com: 5 essential tools for managing hybrid cloud infrastructure</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Identifies key categories and frameworks necessary for coordinating multi-cluster and hybrid environments. Emphasizes unified control planes, configuration management tools like Ansible, orchestration tools, and automated security scanning to maintain posture consistency.</li>
|
||
</ul>
|
||
<h3 id="kubernetes">Kubernetes<a class="headerlink" href="#kubernetes" title="Permanent link">¶</a></h3>
|
||
<h4 id="container-patterns">Container Patterns<a class="headerlink" href="#container-patterns" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://itnext.io/4-container-design-patterns-for-kubernetes-a8593028b4cd">itnext.io: 4 Design Patterns for Containers in Kubernetes | Daniele Polencic 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses key container design patterns within Kubernetes pods, highlighting sidecars, adapters, and ambient patterns. It details how sidecar containers decouple infrastructure utilities (such as logging and service mesh proxies) from main application runtimes.</li>
|
||
</ul>
|
||
<h4 id="openshift">OpenShift<a class="headerlink" href="#openshift" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2018)</strong> <a href="https://techerati.com/the-stack-archive/cloud/2018/10/18/openshift-in-a-world-of-kaas">thestack.com: OpenShift in a world of KaaS 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Evaluates Red Hat OpenShift's standing in an increasingly crowded Kubernetes-as-a-Service (KaaS) market. Details the architectural advantages of OpenShift's integrated developer tooling, security guardrails, and automated enterprise operator systems.</li>
|
||
</ul>
|
||
<h4 id="openshift-comparison">OpenShift Comparison<a class="headerlink" href="#openshift-comparison" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.ibm.com/think/topics/openshift-vs-kubernetes">ibm.com: OpenShift vs. Kubernetes: What’s the Difference?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An authoritative IBM reference contrasting standard Kubernetes and OpenShift. Explains how OpenShift encapsulates the vanilla Kubernetes engine with operational defaults, security governance, and multi-tenant tooling suitable for hybrid cloud environments.</li>
|
||
<li><strong>(2021)</strong> <a href="https://phoenixnap.com/blog/openshift-vs-kubernetes">phoenixnap.com: Kubernetes vs OpenShift: Key Differences Compared 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Breaks down core differences between vanilla Kubernetes and Red Hat OpenShift, evaluating deployment mechanics, security configurations (SCC vs RBAC), built-in routing, out-of-the-box monitoring, and support models.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.simplilearn.com/kubernetes-vs-openshift-article">simplilearn.com: Understanding The Difference Between Kubernetes Vs. Openshift</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An educational comparison detailing the architectural boundaries of Kubernetes and OpenShift. Explores developer workflows, installation processes, built-in CI/CD pipelines, and licensing structures.</li>
|
||
<li><strong>(2019)</strong> <a href="https://www.spec-india.com/blog">spec-india.com: Kubernetes VS Openshift (July 23rd 2019)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares upstream open-source Kubernetes with Red Hat OpenShift. Focuses on user-interface options, CLI differences, security policies, image registry capabilities, and integrated CI/CD toolchain setups in enterprise deployments.</li>
|
||
</ul>
|
||
<h2 id="cloud-native-and-kubernetes-core">Cloud Native and Kubernetes Core<a class="headerlink" href="#cloud-native-and-kubernetes-core" title="Permanent link">¶</a></h2>
|
||
<h3 id="business-value-and-roi">Business Value and ROI<a class="headerlink" href="#business-value-and-roi" title="Permanent link">¶</a></h3>
|
||
<h4 id="operational-automation">Operational Automation<a class="headerlink" href="#operational-automation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.theregister.com/software/2021/12/21/how-kubernetes-lowers-costs-and-automates-it-department-work/1316708">theregister.com: How Kubernetes lowers costs and automates IT department work</a> 🌟🌟🌟 <span class='md-tag md-tag--critical'>[LEGACY]</span> — Evaluates the cost-efficiency and performance benefits of transitioning IT operations from legacy VMs to Kubernetes-orchestrated workloads. Examines auto-scaling, bin-packing, and automated operations as primary factors for decreasing infrastructural and labor expenditures.</li>
|
||
</ul>
|
||
<h3 id="container-orchestration">Container Orchestration<a class="headerlink" href="#container-orchestration" title="Permanent link">¶</a></h3>
|
||
<h4 id="deep-dive">Deep Dive<a class="headerlink" href="#deep-dive" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>alibabacloud.com: Getting Started with Kubernetes | Deep Dive into Kubernetes Core Concepts</summary>
|
||
<p><strong><a href="https://www.alibabacloud.com/blog/getting-started-with-kubernetes-%7C-deep-dive-into-kubernetes-core-concepts_595896">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Deep dive into core Kubernetes architectures, detailing controller-manager reconciliation mechanisms, kube-scheduler filters, and API-driven status updates. Provides a technical reference for engineers wanting to design resource control loops and manage standard system interactions.</p>
|
||
</details>
|
||
<h4 id="fundamentals-1">Fundamentals (1)<a class="headerlink" href="#fundamentals-1" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>cloud.google.com: What is Kubernetes? 🌟</summary>
|
||
<p><strong><a href="https://cloud.google.com/learn/what-is-kubernetes">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>A comprehensive foundation on Kubernetes, detailing its architectural pillars including the control plane, worker nodes, and declarative API engine. It outlines container scheduling, automated self-healing, and service discovery mechanisms essential for running resilient, modern cloud-native systems.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>weave.works: What is a Kubernetes Cluster? 🌟</summary>
|
||
<p><strong><a href="https://www.weave.works/blog/kubernetes-cluster">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Details the core elements forming a Kubernetes cluster, covering worker nodes, control plane systems (etcd, scheduler, API server), and pod networking. Explains how these interconnected components synchronize state to ensure continuous deployment consistency.</p>
|
||
</details>
|
||
<h4 id="future-outlook">Future Outlook<a class="headerlink" href="#future-outlook" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>eficode.com: The future of Kubernetes – and why developers should look beyond Kubernetes in 2022</summary>
|
||
<p><strong><a href="https://www.eficode.com/blog/the-future-of-kubernetes-and-why-developers-should-look-beyond-kubernetes-in-2022">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Investigates the evolutionary curve of Kubernetes, arguing that developers should interface with high-level platform abstractions rather than direct cluster resources. Focuses on tools that simplify the developer workflow, keeping Kubernetes in the background as a dedicated execution runtime.</p>
|
||
</details>
|
||
<h4 id="orchestrator-comparison">Orchestrator Comparison<a class="headerlink" href="#orchestrator-comparison" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>nathanpeck.com: Why should I use an orchestrator like Kubernetes, Amazon ECS, or Hashicorp Nomad?</summary>
|
||
<p><strong><a href="https://nathanpeck.com/why-should-use-container-orchestration">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Compares core orchestrators—Kubernetes, Amazon ECS, and HashiCorp Nomad—to clarify fit based on team expertise and operational scale. Outlines how orchestration solves key deployment needs such as bin-packing, cluster autoscaling, high-availability routing, and health checks.</p>
|
||
</details>
|
||
<h4 id="platform-engineering">Platform Engineering<a class="headerlink" href="#platform-engineering" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Kubernetes and the Next Generation of PaaS</summary>
|
||
<p><strong><a href="https://thenewstack.io/kubernetes-and-the-next-generation-of-paas">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Explores how Kubernetes acts as a core engine for modern Platform-as-a-Service (PaaS) engines, giving developers streamlined deployment controls without underlying cloud complexity. Discusses custom resource definitions (CRDs) and operators as tools for generating customized cloud abstraction layers.</p>
|
||
</details>
|
||
<h3 id="market-trends-2">Market Trends (2)<a class="headerlink" href="#market-trends-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="adoption-analytics">Adoption Analytics<a class="headerlink" href="#adoption-analytics" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoworld.com: Kubernetes adoption up, serverless down, developer survey says</summary>
|
||
<p><strong><a href="https://www.infoworld.com/article/2271482/kubernetes-up-serverless-down-report.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Examines empirical metrics demonstrating increased Kubernetes adoption alongside stagnant serverless framework growth. Highlights developer preference for containerized control, local reproducibility, and standardized deployment patterns over vendor-proprietary, event-driven serverless platforms.</p>
|
||
</details>
|
||
<h4 id="ecosystem-evolution">Ecosystem Evolution<a class="headerlink" href="#ecosystem-evolution" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: 5 Cloud Native Trends to Watch out for in 2022</summary>
|
||
<p><strong><a href="https://thenewstack.io/5-cloud-native-trends-to-watch-out-for-in-2022">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Outlines five major architectural developments in cloud-native technology, highlighting eBPF-powered networking, WebAssembly (Wasm) runtime integration, and GitOps-centric deployment. Serves as a useful compass for aligning next-generation enterprise platforms with emerging standards.</p>
|
||
</details>
|
||
<h3 id="migration-and-modernization-1">Migration and Modernization (1)<a class="headerlink" href="#migration-and-modernization-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="anti-patterns">Anti-Patterns<a class="headerlink" href="#anti-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoq.com: 9 Ways to Fail at Cloud Native</summary>
|
||
<p><strong><a href="https://www.infoq.com/presentations/fail-cloud-native-migration">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Identifies common organizational and architectural pitfalls encountered during cloud-native migrations, such as lifting-and-shifting legacy patterns directly into containers. Stresses the necessity of cultivating a DevOps culture, standardizing platforms, and focusing on cloud-native application patterns.</p>
|
||
</details>
|
||
<h4 id="workload-transition">Workload Transition<a class="headerlink" href="#workload-transition" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: App Modernization: 5 Tips When Migrating to Kubernetes</summary>
|
||
<p><strong><a href="https://thenewstack.io/app-modernization-5-tips-when-migrating-to-kubernetes">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Distills five high-impact operational guidelines for migrating application structures onto Kubernetes. Focuses on the elimination of hardcoded states, configuring robust health probes (liveness/readiness), configuring standard resource limits, and configuring external config parameters.</p>
|
||
</details>
|
||
<h3 id="testing-and-reliability">Testing and Reliability<a class="headerlink" href="#testing-and-reliability" title="Permanent link">¶</a></h3>
|
||
<h4 id="control-plane-validation">Control Plane Validation<a class="headerlink" href="#control-plane-validation" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>micahlerner.com: Automatic Reliability Testing For Cluster Management Controllers</summary>
|
||
<p><strong><a href="https://www.micahlerner.com/2022/07/24/automatic-reliability-testing-for-cluster-management-controllers.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Examines methods for testing Kubernetes-style controllers using fault-injection framework principles (e.g., Sieve). Details how injecting errors, API delays, and container crashes validates the reliability of reconciliation engines, ensuring robust system recovery in production.</p>
|
||
</details>
|
||
<h3 id="virtualization-and-containers">Virtualization and Containers<a class="headerlink" href="#virtualization-and-containers" title="Permanent link">¶</a></h3>
|
||
<h4 id="architecture-comparison">Architecture Comparison<a class="headerlink" href="#architecture-comparison" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>community.hpe.com: Containers vs. VMs: What’s the difference?</summary>
|
||
<p><strong><a href="https://community.hpe.com/hpeb/plugins/custom/hp/hpebresponsive/custom.bounce_endpoint?referer=https%3A%2F%2Fcommunity.hpe.com%2Ft5%2FHPE-Ezmeral-Uncut%2FContainers-vs-VMs-What-s-the-difference%2Fba-p%2F7147090">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Compares hardware-level hypervisor virtualization (VMs) against kernel-level OS virtualization (Containers). The analysis targets engineering constraints around performance, boot speeds, immutable deployment architectures, and compute efficiency, aiding architects in selecting virtualization tiers.</p>
|
||
</details>
|
||
<h4 id="container-anti-patterns">Container Anti-patterns<a class="headerlink" href="#container-anti-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>howtogeek.com: When Not to Use Docker: Cases Where Containers Don’t Help 🌟</summary>
|
||
<p><strong><a href="https://www.howtogeek.com/devops/when-not-to-use-docker-cases-where-containers-dont-help">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Identifies scenarios where containerization introduces unnecessary complexity without providing distinct technical or operational benefits. Analyzes drawbacks for monoliths, GUI-heavy desktop programs, static legacy systems, or performance-critical processes requiring bare-metal host communication.</p>
|
||
</details>
|
||
<h4 id="modernization-strategy">Modernization Strategy<a class="headerlink" href="#modernization-strategy" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>cloud.redhat.com: How to Modernize Virtualized Workloads 🌟</summary>
|
||
<p><strong><a href="https://www.redhat.com/en/blog/how-to-modernize-virtualized-workloads">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Guides enterprise architects through modernizing traditional VM-based applications into containerized architectures using tools like OpenShift Virtualization (KubeVirt). This allows running legacy virtual machines side-by-side with cloud-native containers inside a unified Kubernetes environment.</p>
|
||
</details>
|
||
<h2 id="cloud-native-architecture">Cloud Native Architecture<a class="headerlink" href="#cloud-native-architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="containerization">Containerization<a class="headerlink" href="#containerization" title="Permanent link">¶</a></h3>
|
||
<h4 id="kubernetes-1">Kubernetes (1)<a class="headerlink" href="#kubernetes-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2018)</strong> <a href="https://developers.redhat.com/blog/2018/06/28/why-kubernetes-is-the-new-application-server">developers.redhat.com: Why Kubernetes is The New Application Server</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This guide analyzes the transition from traditional enterprise application servers (like JBoss or WebSphere) to Kubernetes. It positions Kubernetes as the modern application server, handling routing, state management, and lifecycle patterns natively.</li>
|
||
</ul>
|
||
<h3 id="design-patterns-1">Design Patterns (1)<a class="headerlink" href="#design-patterns-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="operators-and-sidecars">Operators and Sidecars<a class="headerlink" href="#operators-and-sidecars" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://thenewstack.io/operators-and-sidecars-are-the-new-model-for-software-delivery">Operators and Sidecars Are the New Model for Software Delivery</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the architectural shift toward using the Sidecar pattern and Kubernetes Operators as standard software delivery mechanisms. This architecture segregates cross-cutting concerns like proxying, logging, and security away from application logic.</li>
|
||
</ul>
|
||
<h3 id="gitops">GitOps<a class="headerlink" href="#gitops" title="Permanent link">¶</a></h3>
|
||
<h4 id="cloud-native-strategy">Cloud Native Strategy<a class="headerlink" href="#cloud-native-strategy" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2019)</strong> <a href="https://www.weave.works/technologies/going-cloud-native-6-essential-things-you-need-to-know">weave.works: Going Cloud Native: 6 essential things you need to know</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Weave Works lays out six core pillars for going cloud native, focusing on containerization, declarative state management, and GitOps workflows to establish efficient deployment setups.</li>
|
||
</ul>
|
||
<h3 id="microservices-3">Microservices (3)<a class="headerlink" href="#microservices-3" title="Permanent link">¶</a></h3>
|
||
<h4 id="enterprise-solutions-1">Enterprise Solutions (1)<a class="headerlink" href="#enterprise-solutions-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.redhat.com/en/topics/microservices/why-choose-red-hat-microservices">redhat.com: Why choose Red Hat for microservices?</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A comprehensive evaluation of Red Hat OpenShift and its ecosystem for microservices. It highlights built-in support for service mesh, security boundaries, and hybrid cloud portability as essential elements for enterprise deployments.</li>
|
||
</ul>
|
||
<h3 id="software-engineering">Software Engineering<a class="headerlink" href="#software-engineering" title="Permanent link">¶</a></h3>
|
||
<h4 id="monoliths-1">Monoliths (1)<a class="headerlink" href="#monoliths-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.allthingsdistributed.com/2023/05/monoliths-are-not-dinosaurs.html">allthingsdistributed.com: Monoliths are not dinosaurs</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Dr. Werner Vogels highlights that monolithic architectures remain highly relevant. The article argues that architectural choices must align with practical business problems rather than dogmatic adherence to microservices patterns.</li>
|
||
<li><strong>(2020)</strong> <a href="https://changelog.com/posts/monoliths-are-the-future">Monoliths are the future | Kelsey Hightower</a> <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Kelsey Hightower advocates for well-structured monolithic applications, challenging the microservices-by-default trend. The case study stresses that organizational discipline and clean boundaries are more important than physical system separation.</li>
|
||
</ul>
|
||
<h2 id="cloud-native-infrastructure_1">Cloud Native Infrastructure<a class="headerlink" href="#cloud-native-infrastructure_1" title="Permanent link">¶</a></h2>
|
||
<h3 id="business-architecture-1">Business Architecture (1)<a class="headerlink" href="#business-architecture-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="infrastructure-management">Infrastructure Management<a class="headerlink" href="#infrastructure-management" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.addwebsolution.com/blog/how-kubernetes-helps-businesses-manage-their-it-infrastructure">addwebsolution.com: How Kubernetes helps businesses manage their IT infrastructure?</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines the business-level value propositions of Kubernetes, including horizontal auto-scaling, resource optimization, and reduced cloud vendor lock-in. It bridges the gap between technical orchestration features and business metrics like accelerated time-to-market and infrastructure cost-efficiency.</li>
|
||
</ul>
|
||
<h4 id="value-proposition">Value Proposition<a class="headerlink" href="#value-proposition" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.weave.works/blog/6-business-benefits-of-kubernetes">weave.works: 6 Business Benefits of Kubernetes</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — From the creators of GitOps, this analysis frames Kubernetes not just as an engineering luxury but as an enterprise driver. Key features highlighted include multi-cloud flexibility, faster software release cycles, robust self-healing infrastructure, and container-driven resource optimization.</li>
|
||
</ul>
|
||
<h3 id="cncf-ecosystem">CNCF Ecosystem<a class="headerlink" href="#cncf-ecosystem" title="Permanent link">¶</a></h3>
|
||
<h4 id="platform-engineering-1">Platform Engineering (1)<a class="headerlink" href="#platform-engineering-1" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: What is the modern cloud native stack? 🌟🌟</summary>
|
||
<p><strong><a href="https://thenewstack.io/what-is-the-modern-cloud-native-stack">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Maps out the components of the modern Cloud Native Computing Foundation (CNCF) stack. From container runtimes (containerd) and orchestration (Kubernetes) to service meshes (Istio/Linkerd) and GitOps deployment paradigms (ArgoCD), this serves as an essential reference architecture.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>thenewstack.io: The Cloud Native Landscape: Platforms Explained</summary>
|
||
<p><strong><a href="https://thenewstack.io/cloud-native/the-cloud-native-landscape-platforms-explained">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Demystifies the CNCF cloud-native interactive landscape by categorizing platform layer elements. Distinguishes Kubernetes distributions, managed Kubernetes offerings, private clouds, and application-level platform abstractions (PaaS) to aid enterprise architects in technology selection.</p>
|
||
</details>
|
||
<h3 id="containerization-1">Containerization (1)<a class="headerlink" href="#containerization-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="fundamentals-2">Fundamentals (2)<a class="headerlink" href="#fundamentals-2" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://opensource.com/article/20/12/containers-101">opensource.com: 6 container concepts you need to understand</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demystifies Linux kernel-level container mechanisms by breaking down the core abstractions. Provides clear explanations of namespaces, cgroups, container images, registries, runtimes, and the relationship between containers and virtual machines.</li>
|
||
<li><strong>(2021)</strong> <a href="https://www.makeuseof.com/kubernetes-or-docker">makeuseof.com: hich Container System Should You Use: Kubernetes or Docker?</a> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Clarifies the common beginner point of confusion comparing Docker with Kubernetes. Explains that Docker is a containerization engine focused on packing and running single application workloads, while Kubernetes is an orchestrator managing fleets of containers across physical resources.</li>
|
||
</ul>
|
||
<h4 id="operations-guide">Operations Guide<a class="headerlink" href="#operations-guide" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>redhat.com: A sysadmin's guide to containerizing applications</summary>
|
||
<p><strong><a href="https://www.redhat.com/en/blog/containerizing-applications">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A highly practical guide detailing how system administrators can containerize legacy workloads. It covers writing clean Containerfiles/Dockerfiles, selecting secure base images, managing non-root execution privileges, and transitioning configuration management to environment variables.</p>
|
||
</details>
|
||
<h3 id="industry-standards">Industry Standards<a class="headerlink" href="#industry-standards" title="Permanent link">¶</a></h3>
|
||
<h4 id="market-trends-3">Market Trends (3)<a class="headerlink" href="#market-trends-3" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: 3 Reasons Why You Can’t Afford to Ignore Cloud Native Computing 🌟</summary>
|
||
<p><strong><a href="https://thenewstack.io/cloud-native/3-reasons-why-you-cant-afford-to-ignore-cloud-native-computing">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Highlights the business-critical benefits of transitioning to a cloud-native compute model. Focuses on cloud-provider independence via portable API standards, massive efficiency gains from auto-scaling resources, and drastically improved fault tolerance compared to traditional legacy VMs.</p>
|
||
</details>
|
||
<h3 id="kubernetes-orchestration">Kubernetes Orchestration<a class="headerlink" href="#kubernetes-orchestration" title="Permanent link">¶</a></h3>
|
||
<h4 id="fundamentals-3">Fundamentals (3)<a class="headerlink" href="#fundamentals-3" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://loves.cloud/kubernetes-an-introduction">loves.cloud: Kubernetes: An Introduction</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Introduces the foundational architecture of Kubernetes, tracing its heritage from Google's internal Borg system to an open-source standard. Explains core concepts such as Pods, Services, Deployments, and the control plane architecture (API Server, etcd, Scheduler, Controller Manager) for bare-metal and cloud migrations.</li>
|
||
</ul>
|
||
<h4 id="future-trends">Future Trends<a class="headerlink" href="#future-trends" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>jaxenter.com: Kubernetes Is Much Bigger Than Containers: Here’s Where It Will Go Next</summary>
|
||
<p><strong><a href="https://devm.io/kubernetes/kubernetes-bigger-173675">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Position paper explaining how Kubernetes has outgrown its primary definition as a container orchestrator to become the universal cloud operating system. Explains the power of the K8s API model, Custom Resource Definitions (CRDs), and how it is orchestrating non-containerized assets, database clusters, and virtual machines.</p>
|
||
</details>
|
||
<h4 id="industry-standards-1">Industry Standards (1)<a class="headerlink" href="#industry-standards-1" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thoughtworks.com: Kubernetes</summary>
|
||
<p><strong><a href="https://www.thoughtworks.com/radar/platforms/kubernetes">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A strategic overview from the Thoughtworks Tech Radar detailing the undisputed supremacy of Kubernetes as the container orchestration engine of choice. The entry evaluates the operational realities of adopting K8s, noting that while it is a de facto standard, organizations must watch out for accidental complexity and invest heavily in platform teams.</p>
|
||
</details>
|
||
<h4 id="industry-trends">Industry Trends<a class="headerlink" href="#industry-trends" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.devprojournal.com/technology-trends/kubernetes/containers-kubernetes-and-software-development-in-2021">devprojournal.com: Containers, Kubernetes and Software Development in 2021</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Evaluates market adoption trends of container ecosystems. Discusses how organizations leverage automated container configurations to speed up local testing cycles, isolate software runtimes, and optimize multi-cloud deployment paradigms.</li>
|
||
</ul>
|
||
<h4 id="kubernetes-tools">Kubernetes Tools<a class="headerlink" href="#kubernetes-tools" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>jaxenter.com: Six Essential Kubernetes Extensions to Add to Your Toolkit 🌟</summary>
|
||
<p><strong><a href="https://devm.io/kubernetes/kubernetes-extensions-172215">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Evaluates a curated selection of Kubernetes command-line and cluster-level utilities designed to simplify debugging, manifest inspection, and deployment automation. Highlighting extensions like K9s, Helm, and Kubectl plugins, the article contrasts native Kubernetes CLI limits with accelerated platform-engineering workflows.</p>
|
||
</details>
|
||
<h4 id="multi-cluster-strategy">Multi-Cluster Strategy<a class="headerlink" href="#multi-cluster-strategy" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>jaxenter.com: Practical Implications for Adopting a Multi-Cluster, Multi-Cloud Kubernetes Strategy</summary>
|
||
<p><strong><a href="https://devm.io/kubernetes/kubernetes-practical-implications-171647">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Analyzes the operational overhead and architectural patterns of deploying Kubernetes across multiple clusters and cloud providers. It contrasts local management with centralized control planes, emphasizing network topology, storage synchronization, and global load balancing. The guide demonstrates that operational complexity must be carefully traded off against high availability and disaster recovery goals.</p>
|
||
</details>
|
||
<h4 id="platform-engineering-2">Platform Engineering (2)<a class="headerlink" href="#platform-engineering-2" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Defining a Different Kubernetes User Interface for the Next Decade</summary>
|
||
<p><strong><a href="https://thenewstack.io/defining-a-different-kubernetes-user-interface-for-the-next-decade">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Discusses the evolution of the Kubernetes API and the growing necessity for user interfaces that abstract the complex YAML declarations. Explores trends like custom controllers, platform wrappers, and programmatic DSLs to simplify operations for non-expert system developers.</p>
|
||
</details>
|
||
<h3 id="professional-development-1">Professional Development (1)<a class="headerlink" href="#professional-development-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="career-engineering-1">Career Engineering (1)<a class="headerlink" href="#career-engineering-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://javarevisited.blogspot.com/2020/11/why-devops-engineer-learn-docker-kubernetes.html">javarevisited.blogspot.com: Why Every Programmer, DevOps Engineer Should learn Docker and Kubernetes in 2020</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines why containerization and container orchestration skills have transitioned from advanced operational specialties to core software development competencies. Highlights the industry-wide ubiquity of Docker and Kubernetes for consistent, reproducible builds across local and cloud environments.</li>
|
||
</ul>
|
||
<h3 id="technology-assessment">Technology Assessment<a class="headerlink" href="#technology-assessment" title="Permanent link">¶</a></h3>
|
||
<h4 id="compute-paradigms">Compute Paradigms<a class="headerlink" href="#compute-paradigms" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>softwareengineeringdaily.com: Kubernetes vs. Serverless with Matt Ward (podcast) 🌟</summary>
|
||
<p><strong><a href="https://softwareengineeringdaily.com/2020/12/29/kubernetes-vs-serverless-with-matt-ward-repeat">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A deep-dive podcast discussion analyzing the philosophical and technical tradeoffs between Kubernetes-orchestrated long-running containers and serverless functions. Explores developer velocity, cold starts, operational complexity, and total cost of ownership (TCO) at scale.</p>
|
||
</details>
|
||
<h2 id="cloud-native-orchestration">Cloud Native Orchestration<a class="headerlink" href="#cloud-native-orchestration" title="Permanent link">¶</a></h2>
|
||
<h3 id="platform-comparison">Platform Comparison<a class="headerlink" href="#platform-comparison" title="Permanent link">¶</a></h3>
|
||
<h4 id="openshift-vs-kubernetes">OpenShift vs Kubernetes<a class="headerlink" href="#openshift-vs-kubernetes" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.imaginarycloud.com/blog/openshift-vs-kubernetes-differences">imaginarycloud.com: OPENSHIFT VS KUBERNETES: WHAT ARE THE DIFFERENCES</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A strategic comparison detailing the core structural and operational differences between upstream Kubernetes and Red Hat OpenShift. This piece evaluates security postures, default configurations, integration constraints, and deployment flexibility, offering architects clear decision criteria.</li>
|
||
<li><strong>(2021)</strong> <a href="https://thenewstack.io/kubernetes/whats-the-difference-between-kubernetes-and-openshift">thenewstack.io: What’s the Difference Between Kubernetes and OpenShift?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This architectural comparison highlights Red Hat's opinionated enterprise extensions built atop vanilla Kubernetes. It details how OpenShift integrates security defaults, built-in container registries, router mechanisms, and lifecycle management controls (OLM) out of the box.</li>
|
||
</ul>
|
||
<h2 id="data-engineering">Data Engineering<a class="headerlink" href="#data-engineering" title="Permanent link">¶</a></h2>
|
||
<h3 id="education">Education<a class="headerlink" href="#education" title="Permanent link">¶</a></h3>
|
||
<h4 id="cookbook">Cookbook<a class="headerlink" href="#cookbook" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://cookbook.learndataengineering.com/docs/05-CaseStudies">cookbook.learndataengineering.com: The Data Engineering Cookbook</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — A comprehensive community cookbook gathering foundational data engineering designs, pipelines, and frameworks. Includes real-world infrastructure and data science architecture case studies, such as processing extreme datasets at CERN.</li>
|
||
</ul>
|
||
<h2 id="devops-and-cicd">DevOps and CICD<a class="headerlink" href="#devops-and-cicd" title="Permanent link">¶</a></h2>
|
||
<h3 id="continuous-integration">Continuous Integration<a class="headerlink" href="#continuous-integration" title="Permanent link">¶</a></h3>
|
||
<h4 id="developer-experience">Developer Experience<a class="headerlink" href="#developer-experience" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>shopify.engineering: Keeping Developers Happy with a Fast CI</summary>
|
||
<p><strong><a href="https://shopify.engineering/faster-shopify-ci">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A case study from Shopify detailing the infrastructure and engineering effort required to maintain sub-minute continuous integration pipelines for large codebases. Explores parallelization techniques, test selection algorithms, and cache-optimization strategies that scale.</p>
|
||
</details>
|
||
<h3 id="microservices-4">Microservices (4)<a class="headerlink" href="#microservices-4" title="Permanent link">¶</a></h3>
|
||
<h4 id="tooling-ecosystem">Tooling Ecosystem<a class="headerlink" href="#tooling-ecosystem" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>hcltech.com: DevOps Tools and Technologies to Manage Microservices 🌟</summary>
|
||
<p><strong><a href="https://www.hcltech.com/blogs/devops-tools-and-technologies-manage-microservices">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Maps out the comprehensive tooling stack required to manage complex microservice lifecycles. Details the intersection of build systems, container registries, service meshes, centralized logging (EFK/ELK), and distributed tracing tools (Jaeger) essential for observability.</p>
|
||
</details>
|
||
<h2 id="devops-automation-and-modern-systems-engineering">DevOps Automation and Modern Systems Engineering<a class="headerlink" href="#devops-automation-and-modern-systems-engineering" title="Permanent link">¶</a></h2>
|
||
<h3 id="automation-and-orchestration">Automation and Orchestration<a class="headerlink" href="#automation-and-orchestration" title="Permanent link">¶</a></h3>
|
||
<h4 id="operational-efficiency">Operational Efficiency<a class="headerlink" href="#operational-efficiency" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/automation-combat-increased-workload">redhat.com: Use automation to combat your increased workload</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Focuses on the role of system-wide automation frameworks (e.g., Ansible, Chef) in managing scale complexity within modern engineering groups. Illustrates how automating toil and routine operations reduces human error rate and frees cognitive resources for high-value architecture planning.</li>
|
||
</ul>
|
||
<h3 id="culture-and-roles">Culture and Roles<a class="headerlink" href="#culture-and-roles" title="Permanent link">¶</a></h3>
|
||
<h4 id="systems-administration-evolution">Systems Administration Evolution<a class="headerlink" href="#systems-administration-evolution" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://opensource.com/article/21/7/system-administrators">opensource.com: What do we call post-modern system administrators?</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Reflects on the transformation of the system administrator role into Site Reliability Engineering (SRE), Platform Engineering, and DevOps roles. It highlights how infrastructure-as-code, GitOps, and high automation levels have reshaped the operational skills required to maintain state-of-the-art enterprise platforms.</li>
|
||
</ul>
|
||
<h3 id="infrastructure-as-code">Infrastructure-as-Code<a class="headerlink" href="#infrastructure-as-code" title="Permanent link">¶</a></h3>
|
||
<h4 id="self-healing-systems">Self-Healing Systems<a class="headerlink" href="#self-healing-systems" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Intention-as Code: Making Self-Healing Infrastructure Work</summary>
|
||
<p><strong><a href="https://thenewstack.io/intention-as-code-making-self-healing-infrastructure-work">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Describes the shift from declarative Infrastructure-as-Code to 'Intention-as-Code,' where engineers declare higher-level business expectations and allow self-healing loops to continuously resolve deviations. Explains reconciliation loops within container orchestrators as the foundational model for autonomous infrastructure engines.</p>
|
||
</details>
|
||
<h3 id="security-and-governance">Security and Governance<a class="headerlink" href="#security-and-governance" title="Permanent link">¶</a></h3>
|
||
<h4 id="policy-as-code">Policy-as-Code<a class="headerlink" href="#policy-as-code" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Cloud Engineers Try Policy-as-Code to Cure Misconfiguration Woes</summary>
|
||
<p><strong><a href="https://thenewstack.io/cloud-engineers-try-policy-as-code-to-cure-misconfiguration-woes">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Details the growth of Policy-as-Code (PaC) tooling like Open Policy Agent (OPA) and Kyverno in preventing critical cloud misconfigurations before runtime. By integrating deterministic rule engines directly into continuous integration loops, platform engineers enforce compliance and security invariants shift-left.</p>
|
||
</details>
|
||
<h3 id="software-engineering-principles">Software Engineering Principles<a class="headerlink" href="#software-engineering-principles" title="Permanent link">¶</a></h3>
|
||
<h4 id="programming-languages">Programming Languages<a class="headerlink" href="#programming-languages" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.enter.co/especiales/dev/herramientas-dev/estos-son-los-10-lenguajes-de-programacion-mas-populares-en-2021">enter.co: Estos son los 10 lenguajes de programación más populares en 2021</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Revisa los lenguajes de programación más influyentes y demandados del año 2021, evaluando su adopción en microservicios, frontend y desarrollo móvil. Ayuda a los equipos de desarrollo a evaluar qué tecnologías garantizan mayor facilidad para contratar talento y compatibilidad de librerías a largo plazo.</li>
|
||
</ul>
|
||
<h4 id="technical-debt-1">Technical Debt (1)<a class="headerlink" href="#technical-debt-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.xataka.com/pro/deuda-tecnica-lastre-para-tecnologicas-estudio-senala-que-informaticos-pierden-casi-dia-trabajo-a-semana-para-solventarlas">xataka.com: La deuda técnica, un lastre para las tecnológicas: un estudio señala que los informáticos pierden casi un día de trabajo a la semana para solventarlas</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analiza las repercusiones financieras y operativas de la deuda técnica dentro de los equipos de desarrollo modernos, destacando que los ingenieros pierden aproximadamente un día por semana mitigándola. El informe subraya la necesidad de implementar prácticas de refactorización continuas y arquitecturas robustas para mitigar este impacto.</li>
|
||
</ul>
|
||
<h2 id="distributed-systems">Distributed Systems<a class="headerlink" href="#distributed-systems" title="Permanent link">¶</a></h2>
|
||
<h3 id="consensus">Consensus<a class="headerlink" href="#consensus" title="Permanent link">¶</a></h3>
|
||
<h4 id="algorithms">Algorithms<a class="headerlink" href="#algorithms" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://raft.github.io">The Raft Consensus Algorithm 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — An interactive educational visualizer for the Raft Consensus Algorithm, designed to be more understandable than Paxos. Covers leader election, log replication, safety mechanisms, and cluster membership changes in highly consistent databases.</li>
|
||
</ul>
|
||
<h2 id="edge-and-iot-orchestration">Edge and IoT Orchestration<a class="headerlink" href="#edge-and-iot-orchestration" title="Permanent link">¶</a></h2>
|
||
<h3 id="embedded-software">Embedded Software<a class="headerlink" href="#embedded-software" title="Permanent link">¶</a></h3>
|
||
<h4 id="automotive-systems">Automotive Systems<a class="headerlink" href="#automotive-systems" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://spectrum.ieee.org/software-eating-car">spectrum.ieee.org: How Software Is Eating the Car</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An industry analysis of software-defined vehicle (SDV) architectures. Investigates how safety-critical embedded frameworks are migrating toward virtualized hardware, container workloads, and modular microservices structures in advanced automotive systems.</li>
|
||
</ul>
|
||
<h2 id="emerging-technology">Emerging Technology<a class="headerlink" href="#emerging-technology" title="Permanent link">¶</a></h2>
|
||
<h3 id="quantum-computing">Quantum Computing<a class="headerlink" href="#quantum-computing" title="Permanent link">¶</a></h3>
|
||
<h4 id="fundamentals-4">Fundamentals (4)<a class="headerlink" href="#fundamentals-4" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://www.cope.es/programas/la-linterna/noticias/ejemplo-moneda-con-que-entender-como-funciona-ordenador-cuantico-una-revolucion-20240407_3232557">cope.es: El ejemplo de 'la moneda' con el que entender cómo funciona un ordenador cuántico: "Será una revolución"</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Introduce los principios de la computación cuántica de manera accesible mediante la analogía de una moneda girando para ilustrar la superposición. Destaca el impacto potencial de los cúbits frente a la computación clásica.</li>
|
||
</ul>
|
||
<h2 id="frontend-architecture">Frontend Architecture<a class="headerlink" href="#frontend-architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="design-patterns-2">Design Patterns (2)<a class="headerlink" href="#design-patterns-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="bff">BFF<a class="headerlink" href="#bff" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://developers.soundcloud.com/blog/service-architecture-1">developers.soundcloud.com: Service Architecture at SoundCloud — Part 1: Backends for Frontends</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--secondary'>[CASE STUDY]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The pioneering engineering case study detailing SoundCloud's development of the Backends-for-Frontends (BFF) pattern. Explains how dedicated, platform-specific API gateways optimize network roundtrips and tailor response payloads for mobile and web clients.</li>
|
||
</ul>
|
||
<h3 id="microfrontends">Microfrontends<a class="headerlink" href="#microfrontends" title="Permanent link">¶</a></h3>
|
||
<h4 id="aws-serverless">AWS Serverless<a class="headerlink" href="#aws-serverless" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://aws.amazon.com/blogs/compute/server-side-rendering-micro-frontends-ui-composer-and-service-discovery">aws.amazon.com: Server-side rendering micro-frontends – UI composer and service discovery</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Proposes a reference architecture for deploying server-side rendered (SSR) micro-frontends on AWS. It uses serverless services like AWS Lambda, Amazon CloudFront, and dynamic composition layers to optimize SEO and page load speeds.</li>
|
||
</ul>
|
||
<h4 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://semaphore.io/blog/microfrontends">semaphoreci.com: Microfrontends: Microservices for the Frontend</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores extending microservice patterns to client-side presentation layers. Evaluates how microfrontends divide a single web application into independent, decoupled frontend modules maintained by autonomous cross-functional teams.</li>
|
||
</ul>
|
||
<h2 id="infrastructure">Infrastructure<a class="headerlink" href="#infrastructure" title="Permanent link">¶</a></h2>
|
||
<h3 id="cloud-architecture-1">Cloud Architecture (1)<a class="headerlink" href="#cloud-architecture-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="paradigms">Paradigms<a class="headerlink" href="#paradigms" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://cloudscaling.com/blog/cloud-computing/the-history-of-pets-vs-cattle">cloudscaling.com: The History of Pets vs Cattle and How to Use the Analogy Properly</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Unpacks the historical context of the 'Pets vs Cattle' cloud infrastructure analogy. Contrasts bespoke, manually maintained systems (pets) with standardized, automatically rebuilt, and ephemeral containerized node pools (cattle).</li>
|
||
</ul>
|
||
<h3 id="cloud-financials">Cloud Financials<a class="headerlink" href="#cloud-financials" title="Permanent link">¶</a></h3>
|
||
<h4 id="finops">FinOps<a class="headerlink" href="#finops" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.theregister.com/off-prem/2023/01/16/basecamp-details-32-million-bill-that-saw-it-quit-cloud/270397">theregister.com: Basecamp details 'obscene' $3.2 million bill that caused it to quit the cloud</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Investigates 37signals' highly publicized exit from AWS public cloud infrastructure. Highlights the architectural transition back to owned bare-metal hardware, showcasing substantial cost reductions and FinOps optimization.</li>
|
||
</ul>
|
||
<h3 id="legacy">Legacy<a class="headerlink" href="#legacy" title="Permanent link">¶</a></h3>
|
||
<h4 id="mainframe">Mainframe<a class="headerlink" href="#mainframe" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.elespanol.com/invertia/disruptores/grandes-actores/tecnologicas/20230416/mainframe-repaso-pasado-futuro-tecnologia-resiste-morir/756174490_0.html">elespanol.com: Mainframe: repaso de pasado y futuro a una tecnología de 1944 que se resiste a morir</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analiza la longevidad del hardware mainframe y su continua relevancia en el sector financiero y asegurador. Explora cómo las arquitecturas heredadas se integran con nubes híbridas modernas mediante APIs y capas de compatibilidad.</li>
|
||
</ul>
|
||
<h3 id="virtualization">Virtualization<a class="headerlink" href="#virtualization" title="Permanent link">¶</a></h3>
|
||
<h4 id="broadcom-era">Broadcom Era<a class="headerlink" href="#broadcom-era" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://www.thestack.technology/vmware-is-killing-off-56-products-including-vsphere-hypervisor-and-nsx">thestack.technology: VMware is killing off 56 products amid "tectonic" infrastructure shift</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details Broadcom's aggressive consolidation of VMware's product portfolio. Analyzes the impact on enterprise infrastructure strategies, driving many organizations to accelerate their migrations to bare metal, KVM, or public cloud.</li>
|
||
</ul>
|
||
<h2 id="infrastructure-and-hardware">Infrastructure and Hardware<a class="headerlink" href="#infrastructure-and-hardware" title="Permanent link">¶</a></h2>
|
||
<h3 id="data-center-investments">Data Center Investments<a class="headerlink" href="#data-center-investments" title="Permanent link">¶</a></h3>
|
||
<h4 id="europe">Europe<a class="headerlink" href="#europe" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://cincodias.elpais.com/cincodias/2022/03/31/companias/1648738965_952353.html">cincodias.elpais.com: El sector del 'data center' eleva a 6.837 millones su inversión directa en nuevos centros en España hasta 2026</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Industrial report tracking data center investments in Spain up to 2026. Highlights structural upgrades and major hardware infrastructure investments needed to support highly dense, low-latency regional cloud-native workloads.</li>
|
||
</ul>
|
||
<h2 id="kubernetes-tools-1">Kubernetes Tools (1)<a class="headerlink" href="#kubernetes-tools-1" title="Permanent link">¶</a></h2>
|
||
<h3 id="general-reference">General Reference<a class="headerlink" href="#general-reference" title="Permanent link">¶</a></h3>
|
||
<ul>
|
||
<li><a href="https://www.ringcentral.com/gb/en/blog/definitions/software-as-a-service-saas">ringcentral.co.uk: Software as a Service (SaaS)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering www.ringcentral.com in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.ringcentral.com/gb/en/blog/definitions/cloud-management">ringcentral.co.uk: Cloud Management 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering www.ringcentral.com in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.hashicorp.com/resources/kelsey-hightower-fireside-chat-an-unconventional-path-to-it-and-some-life-advice">Kelsey Hightower Fireside Chat: An Unconventional Path to IT and Some Life Advice</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering www.hashicorp.com in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/microservices-communication-using-grpc-protocol-dc3a2f8b648d">medium.com/javarevisited: Microservices communication using gRPC Protocol</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/javarevisited: Microservices communication using gRPC Protocol</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/how-to-design-a-system-to-scale-to-your-first-100-million-users-4450a2f9703d">levelup.gitconnected.com: How to design a system to scale to your first' 100 million users</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: How to design a system to scale to your first' 100 million users in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.enterprisetimes.co.uk/2020/07/23/monolithic-versus-microservice-architecture">Monolithic versus Microservice architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering Monolithic versus Microservice architecture in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.cncf.io/blog/2020/09/15/top-7-challenges-to-becoming-cloud-native">cncf.io: Top 7 challenges to becoming cloud native</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering cncf.io: Top 7 challenges to becoming cloud native in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.techrepublic.com/article/kubernetes-will-deliver-the-app-store-experience-for-enterprise-software-says-weaveworks-ceo">techrepublic.com: Kubernetes will deliver the app store experience for enterprise' software, says Weaveworks CEO</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering techrepublic.com: Kubernetes will deliver the app store experience for enterprise' software, says Weaveworks CEO in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://shahirdaya.medium.com/what-does-it-mean-to-be-cloud-native-12360a324571">shahirdaya.medium.com: What does it mean to be Cloud Native? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering shahirdaya.medium.com: What does it mean to be Cloud Native? 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://skamille.medium.com/make-boring-plans-9438ce5cb053">skamille.medium.com: Make Boring Plans</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering skamille.medium.com: Make Boring Plans in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://cloud-melon.com/2019/12/26/under-the-hood-of-kubernetes-and-microservices">cloud-melon.com: Under the hood of Kubernetes and microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering cloud-melon.com: Under the hood of Kubernetes and microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/swlh/a-design-analysis-of-cloud-based-microservices-architecture-at-netflix-98836b2da45f">medium: A Design Analysis of Cloud-based Microservices Architecture at Netflix</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: A Design Analysis of Cloud-based Microservices Architecture at Netflix in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.hashicorp.com/resources/why-microservices">hashicorp.com: Why Microservices? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering hashicorp.com: Why Microservices? 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/swlh/microservices-architecture-from-a-to-z-7287da1c5d28">medium: Microservices Architecture From A to Z 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Microservices Architecture From A to Z 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://skycrafters.io/blog/2021/06/08/do-containers-really-contain">skycrafters.io: Do Containers Really Contain? Virtual Machines vs. Containers' 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering skycrafters.io: Do Containers Really Contain? Virtual Machines vs. Containers' 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/techbeatly/container-fundamentals-part-i-445881a81b7">medium: Container Fundamentals — Part 1</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Container Fundamentals — Part 1 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/microservices-for-net-developers/what-is-microservices-and-why-is-it-different-fac017cb8cf4">medium: What is microservices and why is it different? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: What is microservices and why is it different? 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/how-your-application-architecture-evolved">How Your Application Architecture Has Evolved 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering How Your Application Architecture Has Evolved 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.fylamynt.com/post/mastering-cloud-automation-in-the-cloud-native-era">fylamynt.com: Mastering Cloud Automation in the Cloud-Native Era 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering fylamynt.com: Mastering Cloud Automation in the Cloud-Native Era 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/getdefault-in/monoliths-vs-microservices-59cff20bb106">medium: Monoliths vs Microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Monoliths vs Microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/top-time-wastes-as-a-software-engineer">dzone: Top 6 Time Wastes as a Software Engineer</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Top 6 Time Wastes as a Software Engineer in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://hiralee.medium.com/software-design-vs-architecture-1da0a94322a4">hiralee.medium.com: Software Architecture vs Design</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering hiralee.medium.com: Software Architecture vs Design in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.deref.io/containers-dont-solve-everything">blog.deref.io: Containers Don't Solve Everything 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering blog.deref.io: Containers Don't Solve Everything 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/transitioning-from-monolith-to-microservices">dzone: Transitioning from Monolith to Microservices (with python django' example)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Transitioning from Monolith to Microservices (with python django' example) in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.cncf.io/blog/2021/10/29/how-to-justify-infrastructure-replacement-to-your-manager">cncf.io: How to justify infrastructure replacement to your manager</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering cncf.io: How to justify infrastructure replacement to your manager in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.techrepublic.com/article/enterprises-get-closer-to-the-app-store-experience-with-kubernetes-and-gitops">techrepublic.com: Enterprises get closer to the app store experience with' Kubernetes and GitOps</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>techrepublic.com: Enterprises get closer to the app store experience with' Kubernetes and GitOps</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://venturebeat.com/2021/12/22/5-ways-the-world-of-it-operations-will-shift-in-2022-and-beyond">venturebeat.com: 5 ways the world of IT operations will shift in 2022 (and' beyond)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering venturebeat.com: 5 ways the world of IT operations will shift in 2022 (and' beyond) in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.devgenius.io/distributed-monolith-1d2d9f86a68f">blog.devgenius.io: Distributed Monolith</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>blog.devgenius.io: Distributed Monolith</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/geekculture/a-beginners-guide-to-understanding-microservices-d2a8bae871b7">medium.com/geekculture: A Beginners Guide to Understanding Microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/geekculture: A Beginners Guide to Understanding Microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/interviewnoodle/shift-from-monolith-to-cqrs-a34bab75617e">medium.com/interviewnoodle: Shift from Monolith to CQRS 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/interviewnoodle: Shift from Monolith to CQRS</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@ajin.sunny/system-design-architecture-stateful-vs-stateless-62ed0ddb9f2b">medium.com/@ajin.sunny: System Design Architecture: Stateful vs. Stateless' 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/@ajin.sunny: System Design Architecture: Stateful vs. Stateless</mark>' 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@ajin.sunny/system-design-concept-rate-limiting-f4da72371533">medium.com/@ajin.sunny: System Design Concept: Rate limiting 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@ajin.sunny: System Design Concept: Rate limiting 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@ajin.sunny/rate-limiting-in-distributed-systems-bbeca0c47b96">medium.com/@ajin.sunny: Rate limiting in Distributed Systems 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@ajin.sunny: Rate limiting in Distributed Systems 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.devgenius.io/top-10-architecture-characteristics-non-functional-requirements-with-cheatsheat-7ad14bbb0a9b">blog.devgenius.io: Top 10 Architecture Characteristics / Non-Functional' Requirements with Cheatsheet 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering blog.devgenius.io: Top 10 Architecture Characteristics / Non-Functional' Requirements with Cheatsheet 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/dotnet-hub/introduction-to-cloud-native-application-architecture-what-is-cloud-native-architecture-overview-benefits-e9be9aca0dd3">medium.com/dotnet-hub: Software Architecture — Introduction to Cloud Native' Application Architecture 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/dotnet-hub: Software Architecture — Introduction to Cloud Native' Application Architecture</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://bootcamp.uxdesign.cc/popular-tech-stack-for-startups-in-2022-f3b53f50c18">bootcamp.uxdesign.cc: Popular Tech Stack for Startups in 2022</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering bootcamp.uxdesign.cc: Popular Tech Stack for Startups in 2022 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@interviewready/data-replication-in-distributed-system-87f7d265ff28">medium.com/@interviewready: Data Replication in Distributed System</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@interviewready: Data Replication in Distributed System in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://semaphoreci.medium.com/12-ways-to-improve-your-monolith-before-transitioning-to-microservices-d1061e96ca1a">semaphoreci.medium.com: 12 Ways to Improve Your Monolith Before Transitioning' to Microservices 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>semaphoreci.medium.com: 12 Ways to Improve Your Monolith Before Transitioning' to Microservices</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://hardiks.medium.com/top-6-best-practices-for-container-orchestration-b4b0d3398ebc">hardiks.medium.com: Top 6 Best practices for Container Orchestration' 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>hardiks.medium.com: Top 6 Best practices for Container Orchestration</mark>' 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@nadinCodeHat/http-based-microservices-is-a-bad-idea-670d3db29ca6">medium.com/@nadinCodeHat: HTTP based Microservices is a bad idea 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@nadinCodeHat: HTTP based Microservices is a bad idea 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/qe-unit/the-microservices-adoption-roadmap-e37f3f32877">medium.com/qe-unit: Microservices — Do You Need Them? Are You Ready? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/qe-unit: Microservices — Do You Need Them? Are You Ready? 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://cloudnativeislamabad.hashnode.dev/virtualization-vs-containerization">cloudnativeislamabad.hashnode.dev: Virtualization vs Containerization</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering cloudnativeislamabad.hashnode.dev: Virtualization vs Containerization in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/distributed-transaction-management-in-microservices-part-1-bb7dc1fbee9f">medium.com/javarevisited: Distributed Transaction Management in Microservices' — Part 1 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/javarevisited: Distributed Transaction Management in Microservices' — Part 1 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://betterprogramming.pub/how-to-transform-a-monolith-application-into-a-microservices-architecture-1e00363a03ba">betterprogramming.pub: How to Transform a Monolith Application Into a' Microservices Architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>betterprogramming.pub: How to Transform a Monolith Application Into a' Microservices Architecture</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/codex/solving-distributed-transaction-management-problem-in-microservices-architecture-586ab3087efe">medium.com/codex: MicroServices Architecture to Solve Distributed Transaction' Management Problem</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/codex: MicroServices Architecture to Solve Distributed Transaction' Management Problem in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://betterprogramming.pub/how-i-split-a-monolith-into-microservices-without-refactoring-5d76924c34c2">betterprogramming.pub: How I Split a Monolith Into Microservices Without' Refactoring 🌟🌟🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>betterprogramming.pub: How I Split a Monolith Into Microservices Without' Refactoring</mark> 🌟🌟🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.ust.com/en/insights/do-we-really-need-kubernetes-and-containers">ust.com: Do we really need Kubernetes and containers?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering ust.com: Do we really need Kubernetes and containers? in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/do-you-know-distributed-job-scheduling-in-microservices-architecture-44082adad8ac">levelup.gitconnected.com: Do you know Distributed Job Scheduling in Microservices' Architecture? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: Do you know Distributed Job Scheduling in Microservices' Architecture? 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/microservices-communication-part-1-every-programmer-must-know-7c6607d2d563">medium.com/javarevisited: Microservices Communication part 1-every programmer' must know 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/javarevisited: Microservices Communication part 1-every programmer' must know</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/microservices-communication-part-2-sync-vs-async-vs-hybrid-23d057e137d8">medium.com/javarevisited: Microservices Communication — part 2— Sync vs' Async vs Hybrid?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/javarevisited: Microservices Communication — part 2— Sync vs' Async vs Hybrid? in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/why-microservices-are-not-silver-bullet-10-reasons-for-not-using-microservices-74f7c0fa98c">medium.com/javarevisited: Why Microservices are not silver bullet? 10 Reasons' for NOT using Microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/javarevisited: Why Microservices are not silver bullet? 10 Reasons' for NOT using Microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://rahulh123.medium.com/choosing-the-right-architecture-monolithic-vs-microservices-analyzing-requirements-for-success-70d681f6a1d0">rahulh123.medium.com: Choosing the Right Architecture: Monolithic vs. Microservices' — Analyzing Requirements for Success</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering rahulh123.medium.com: Choosing the Right Architecture: Monolithic vs. Microservices' — Analyzing Requirements for Success in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://waswani.medium.com/microservices-data-sharing-using-database-an-antipattern-35e0196ee2ad">waswani.medium.com: Microservices Communication: Data Sharing using Database,' an AntiPattern !!!</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering waswani.medium.com: Microservices Communication: Data Sharing using Database,' an AntiPattern !!! in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@bill.salvaggio/the-aws-cloud-resume-challenge-project-c5c0c6fe9593">medium.com/@bill.salvaggio: The AWS Cloud Resume Challenge Project</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/@bill.salvaggio: The AWS Cloud Resume Challenge Project</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.lealdasilva.com/vmware2proxmox">blog.lealdasilva.com: Why You Should Switch from VMware to Proxmox in 2024</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering blog.lealdasilva.com: Why You Should Switch from VMware to Proxmox in 2024 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://towardsdev.com/solution-architecture-101-are-you-ready-for-the-solution-architect-path-5a2d01aebbb">towardsdev.com: Solution architecture 101 — Are you ready for the Solution' Architect Path 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>towardsdev.com: Solution architecture 101 — Are you ready for the Solution' Architect Path</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://mkaschke.medium.com/cloud-native-part-1-what-is-cloud-native-40640f128834">mkaschke.medium.com: ud Native Part 1: What Is Cloud Native? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>mkaschke.medium.com: ud Native Part 1: What Is Cloud Native?</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/promyze/avoid-accidental-complexity-and-technical-debt-2dc2cdf4dd4b">medium.com/promyze: Avoid accidental complexity and technical debt</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/promyze: Avoid accidental complexity and technical debt in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://maheshwari-bittu.medium.com/why-event-driven-architecture-eda-is-needed-fac2f00f25a8">maheshwari-bittu.medium.com: Why Event-Driven Architecture (EDA) is needed?' 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering maheshwari-bittu.medium.com: Why Event-Driven Architecture (EDA) is needed?' 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/rocco-scaramuzzi-tech/event-driven-microservice-architecture-dont-use-only-events-but-use-commands-too-b8694d370436">medium.com/rocco-scaramuzzi-tech: Event-Driven Microservice Architecture,' don’t use only events but use commands too!</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/rocco-scaramuzzi-tech: Event-Driven Microservice Architecture,' don’t use only events but use commands too! in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://deeptimittalblogger.medium.com/event-driven-architecture-111f504a8cbc">deeptimittalblogger.medium.com: Event driven architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering deeptimittalblogger.medium.com: Event driven architecture in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/mcdonalds-technical-blog/behind-the-scenes-mcdonalds-event-driven-architecture-51a6542c0d86">medium.com/mcdonalds-technical-blog: Behind the scenes: McDonald’s event-driven' architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/mcdonalds-technical-blog: Behind the scenes: McDonald’s event-driven' architecture in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/mcdonalds-technical-blog/mcdonalds-event-driven-architecture-the-data-journey-and-how-it-works-4591d108821f">medium.com/mcdonalds-technical-blog: McDonald’s event-driven architecture:' The data journey and how it works</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/mcdonalds-technical-blog: McDonald’s event-driven architecture:' The data journey and how it works in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/error-handling-in-event-driven-systems-1f0a7ef2cfb7">levelup.gitconnected.com: Error Handling in Event-Driven Systems</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: Error Handling in Event-Driven Systems in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://faun.pub/what-is-difference-of-event-driven-architecture-message-driven-architecture-and-microservices-f5623e51f868">faun.pub: Understanding the Differences Between Event-Driven, Message-Driven,' and Microservices Architectures with AWS Services</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering faun.pub: Understanding the Differences Between Event-Driven, Message-Driven,' and Microservices Architectures with AWS Services in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/5-tips-to-design-for-multi-tenancy-architecture-5f7d55657d77">levelup.gitconnected.com: 5 Tips To Design For Multi-Tenancy Architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: 5 Tips To Design For Multi-Tenancy Architecture in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/multi-tenant-application-a29153d31c5a">levelup.gitconnected.com: Multi-Tenant Application</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: Multi-Tenant Application in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/shift-left-a-developers-pipeline-dream">dzone.com: Shift-Left: A Developer's Pipe(line) Dream?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>dzone.com: Shift-Left: A Developer's Pipe(line) Dream?</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/solutions-architecture-patterns/multi-cloud-enterprise-deployment-pattern-19571604e64b">medium: Multi Cloud Enterprise Deployment Pattern</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Multi Cloud Enterprise Deployment Pattern in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.cncf.io/blog/2021/09/29/automation-is-the-future-of-cloud-cost-optimization">Automation is the future of cloud cost optimization</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering Automation is the future of cloud cost optimization in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/7-microservices-best-practices-for-developers">dzone: 7 Microservices Best Practices for Developers 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: 7 Microservices Best Practices for Developers 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.couchbase.com/microservices-architecture-in-couchbase">blog.couchbase.com: 4 Patterns for Microservices Architecture in Couchbase</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering blog.couchbase.com: 4 Patterns for Microservices Architecture in Couchbase in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/microservices-in-practice/microservices-in-practice-7a3e85b6624c">medium: Pragmatic Microservices 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium: Pragmatic Microservices 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@sandeepsharmaster/modernize-your-cloud-microservices-apps-hexagonal-architecture-769696494c0">medium.com/@sandeepsharmaster: Design your Cloud Microservices Apps the' DDD way (Hexagonal Architecture)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@sandeepsharmaster: Design your Cloud Microservices Apps the' DDD way (Hexagonal Architecture) in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@denhox/sharing-data-between-microservices-fe7fb9471208">medium.com/@denhox: Sharing Data Between Microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@denhox: Sharing Data Between Microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@maneesha649nirman/design-patterns-for-microservices-30bed0d215f5">medium.com/@maneesha649nirman: Design Patterns For Microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@maneesha649nirman: Design Patterns For Microservices in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@vinciabhinav7/microservices-communication-architecture-patterns-a8e77e614c2c">medium.com/@vinciabhinav7: Microservices Communication Architecture Patterns' 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/@vinciabhinav7: Microservices Communication Architecture Patterns</mark>' 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/javarevisited/10-microservices-design-principles-every-developer-should-know-44f2f69e960f">medium.com/javarevisited: Top 10 Microservices Design Principles and Best' Practices for Experienced Developers 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/javarevisited: Top 10 Microservices Design Principles and Best' Practices for Experienced Developers</mark> 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@mbarkin.narin/problem-solving-strategies-for-microservice-architecture-part-iii-c15830151890">medium.com/@mbarkin.narin: Problem Solving Strategies for Microservice Architecture' Part III</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/@mbarkin.narin: Problem Solving Strategies for Microservice Architecture' Part III in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.developer.com/design/solving-microservices-anti-patterns">developer.com: Overcoming the Common Microservices Anti-Patterns</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering developer.com: Overcoming the Common Microservices Anti-Patterns in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/micro-frontends-by-example-8">dzone: Micro Frontends With Example 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Micro Frontends With Example 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/micro-frontend-architecture-794442e9b325">levelup.gitconnected.com: Micro Frontend Architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: Micro Frontend Architecture in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/micro-frontend-architecture">dzone: Micro-Frontend Architecture</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>dzone: Micro-Frontend Architecture</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/whispering-data/the-state-of-data-engineering-2022-d6ef0f7cf607">medium.com/whispering-data: The State of Data Engineering 2022</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>medium.com/whispering-data: The State of Data Engineering 2022</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://joereis.substack.com/p/data-engineering-in-2024-what-im">joereis.substack.com: Data Engineering in 2024. What I'm Seeing</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering joereis.substack.com: Data Engineering in 2024. What I'm Seeing in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://betterprogramming.pub/a-cloud-migration-questionnaire-for-solution-architects-dec7ffcf063e">betterprogramming.pub: A Cloud Migration Questionnaire for Solution Architects' 🌟🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering betterprogramming.pub: A Cloud Migration Questionnaire for Solution Architects' 🌟🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://www.trustradius.com/platform-as-a-service-paas">What is Platform as a Service Software?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering What is Platform as a Service Software? in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://ramansharma.substack.com/p/containers-are-not-just-for-kubernetes-fa330653cbbd">ramansharma.substack.com: Containers are not just for Kubernetes</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>ramansharma.substack.com: Containers are not just for Kubernetes</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition">wikipedia: Java Enterprise Edition (Java EE)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering wikipedia: Java Enterprise Edition (Java EE) in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/monolith-to-microservices-using-the-strangler-patt">dzone: Monolith to Microservices Using the Strangler Pattern 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: Monolith to Microservices Using the Strangler Pattern 🌟 in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/4-cluster-management-tools-to-compare">Dzone.com: 4 Cluster Management Tools to Compare</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering Dzone.com: 4 Cluster Management Tools to Compare in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/kubernetes-distributions-how-do-i-choose-one">Dzone.com: A Comparison of Kubernetes Distributions</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering Dzone.com: A Comparison of Kubernetes Distributions in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/levvel-consulting/the-differences-between-kubernetes-and-openshift-ae778059a90e">medium.com: The Differences Between Kubernetes and Openshift</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com: The Differences Between Kubernetes and Openshift in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://blog.netsil.com/kubernetes-vs-openshift-vs-tectonic-comparing-enterprise-options-e3a34dc60519">blog.netsil.com: Kubernetes vs Openshift vs Tectonic: Comparing Enterprise' Options</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering blog.netsil.com: Kubernetes vs Openshift vs Tectonic: Comparing Enterprise' Options in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://kubedex.com/redhat-openshift-vs-pivotal-pks-vs-rancher">kubedex.com: Kubernetes On-Prem, OpenShift vs PKS vs Rancher</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering kubedex.com: Kubernetes On-Prem, OpenShift vs PKS vs Rancher in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/@srikanth.k/kubernetes-what-is-it-what-problems-does-it-solve-how-does-it-compare-with-its-alternatives-937fe80b754f">medium.com: Kubernetes — What Is It, What Problems Does It Solve and How' Does It Compare With Alternatives?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com: Kubernetes — What Is It, What Problems Does It Solve and How' Does It Compare With Alternatives? in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://levelup.gitconnected.com/openshift-the-next-level-of-kubernetes-6d58ad722b26">levelup.gitconnected.com: OpenShift — The Next Level of Kubernetes</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering levelup.gitconnected.com: OpenShift — The Next Level of Kubernetes in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/7-software-development-models-you-should-know">dzone: 7 Software Development Models You Should Know</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering dzone: 7 Software Development Models You Should Know in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://dzone.com/articles/the-concept-of-domain-driven-design-explained">dzone: The Concept of Domain-Driven Design Explained</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering <mark>dzone: The Concept of Domain-Driven Design Explained</mark> in the Kubernetes Tools ecosystem.</li>
|
||
<li><a href="https://medium.com/codex/ddd-events-are-complex-db4b1fb57817">medium.com/codex: DDD — Events Are Complex</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated technical resource and architectural guide covering medium.com/codex: DDD — Events Are Complex in the Kubernetes Tools ecosystem.</li>
|
||
</ul>
|
||
<h2 id="methodology-1">Methodology (1)<a class="headerlink" href="#methodology-1" title="Permanent link">¶</a></h2>
|
||
<h3 id="careers">Careers<a class="headerlink" href="#careers" title="Permanent link">¶</a></h3>
|
||
<h4 id="enterprise-strategy">Enterprise Strategy<a class="headerlink" href="#enterprise-strategy" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://www.virtualizationhowto.com/2024/02/vmware-by-broadcom-lesson-dont-base-your-career-on-a-product">virtualizationhowto.com: VMware by Broadcom Lesson: Don’t base your career on a product</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Reflects on the rapid changes post-Broadcom acquisition of VMware, serving as a cautionary tale for technical practitioners. Advises diversifying skills beyond proprietary ecosystems into open-source tooling like Kubernetes and Proxmox.</li>
|
||
</ul>
|
||
<h3 id="development">Development<a class="headerlink" href="#development" title="Permanent link">¶</a></h3>
|
||
<h4 id="best-practices-1">Best Practices (1)<a class="headerlink" href="#best-practices-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.freecodecamp.org/news/how-to-write-clean-code">freecodecamp.org: How to Write Clean Code – Tips and Best Practices (Full Handbook)</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A definitive guide on readability, testing, refactoring patterns, and SOLID principles. Helps engineers reduce mental overhead, secure maintainability, and keep technical debt low across codebases.</li>
|
||
</ul>
|
||
<h4 id="learning-resources">Learning Resources<a class="headerlink" href="#learning-resources" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.genbeta.com/desarrollo/cinco-repositorios-github-buenos-que-imprescindibles-estas-aprendiendo-te-dedicas-a-programar-1">genbeta.com/a-fondo: Cinco repositorios de GitHub tan buenos que son imprescindibles si estás aprendiendo o te dedicas a programar</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Recopila cinco repositorios de GitHub esenciales para el aprendizaje continuo de programación. Incluye recursos interactivos sobre algoritmos, patrones de diseño, hojas de ruta de desarrollo y arquitecturas de sistemas.</li>
|
||
</ul>
|
||
<h3 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h3>
|
||
<h4 id="governance">Governance<a class="headerlink" href="#governance" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/architecture-decision-records">redhat.com: Why you should be using architecture decision records to document your project</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines the foundational value of Architecture Decision Records (ADRs). Demonstrates how recording the context, options, and rationale behind architectural changes prevents information decay and guides onboarding processes.</li>
|
||
</ul>
|
||
<h3 id="engineering-leadership">Engineering Leadership<a class="headerlink" href="#engineering-leadership" title="Permanent link">¶</a></h3>
|
||
<h4 id="governance-1">Governance (1)<a class="headerlink" href="#governance-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://thenewstack.io/stop-technical-debt-before-it-damages-your-company">thenewstack.io: Stop Technical Debt Before It Damages Your Company</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines proactive governance models to identify and mitigate tech debt before it stunts organizational velocity. Advocates for clear code quality baselines, integrated CI/CD linter pipelines, and dedicated refactoring sprints.</li>
|
||
</ul>
|
||
<h4 id="technical-debt-2">Technical Debt (2)<a class="headerlink" href="#technical-debt-2" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://leaddev.com/technical-direction/how-break-cycle-tech-debt">leaddev.com: How to break the cycle of tech debt</a> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Provides engineering leadership strategies to break the endless loop of compounding legacy software issues. Outlines methods to negotiate refactoring cycles directly with product stakeholders using objective metrics.</li>
|
||
</ul>
|
||
<h3 id="metrics">Metrics<a class="headerlink" href="#metrics" title="Permanent link">¶</a></h3>
|
||
<h4 id="technical-debt-3">Technical Debt (3)<a class="headerlink" href="#technical-debt-3" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://devops.com/measuring-technical-debt">devops.com: Measuring Technical Debt</a> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Explores analytical frameworks to measure technical debt objectively. Employs metrics like SQALE methodology, code coverage, cycle time impact, and escape defect rates to calculate the true cost of legacy architectures.</li>
|
||
</ul>
|
||
<h3 id="quality">Quality<a class="headerlink" href="#quality" title="Permanent link">¶</a></h3>
|
||
<h4 id="embedded-systems">Embedded Systems<a class="headerlink" href="#embedded-systems" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.enriquedans.com/2023/12/el-desastre-del-software-y-la-automocion.html">enriquedans.com: El desastre del software y la automoción</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Reflexiona sobre la crisis de desarrollo de software en la industria automotriz global. Analiza la transición crítica de la ingeniería puramente mecánica hacia ecosistemas de software complejos basados en actualizaciones OTA.</li>
|
||
</ul>
|
||
<h3 id="roles">Roles<a class="headerlink" href="#roles" title="Permanent link">¶</a></h3>
|
||
<h4 id="cloud-governance">Cloud Governance<a class="headerlink" href="#cloud-governance" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.infoworld.com/article/2335001/why-we-need-both-cloud-architects-and-cloud-engineers.html">infoworld.com: Why we need both cloud architects and cloud engineers</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details the division of labor between cloud architects, who define strategic blueprints and governance, and cloud engineers, who handle implementation, IaC deployment, and operational maintenance.</li>
|
||
</ul>
|
||
<h3 id="software-engineering-1">Software Engineering (1)<a class="headerlink" href="#software-engineering-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="technical-debt-4">Technical Debt (4)<a class="headerlink" href="#technical-debt-4" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.n-ix.com/reduce-technical-debt">n-ix.com: How to reduce your technical debt: An ultimate guide</a> <span class='md-tag md-tag--secondary'>[GUIDE]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — A holistic architectural playbook for diagnosing, budgeting, and paying down complex software debt. Proposes systematic approaches like code reviews, architectural documentation, and legacy modernization patterns.</li>
|
||
<li><strong>(2023)</strong> <a href="https://www.infoworld.com/article/2338860/you-cant-run-away-from-technical-debt.html">infoworld.com: You can’t run away from technical debt</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the inevitability of technical debt as cloud environments and architectures naturally age. Argues that cloud adoption does not eliminate debt but merely shifts it to configuration, infrastructure, and IaC domains.</li>
|
||
</ul>
|
||
<h2 id="microservices-5">Microservices (5)<a class="headerlink" href="#microservices-5" title="Permanent link">¶</a></h2>
|
||
<h3 id="anti-patterns-1">Anti-Patterns (1)<a class="headerlink" href="#anti-patterns-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="failure-modes">Failure Modes<a class="headerlink" href="#failure-modes" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2019)</strong> <a href="https://www.infoq.com/articles/microservices-seven-fail">infoq.com: 7 Ways to Fail at Microservices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details common organizational and architectural traps when shifting to microservices. Critiques lack of boundary clarity, shared database anti-patterns, manual deployment strategies, and neglecting distributed observability networks.</li>
|
||
</ul>
|
||
<h4 id="lessons-learned">Lessons Learned<a class="headerlink" href="#lessons-learned" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://world.hey.com/joaoqalves/disasters-i-ve-seen-in-a-microservices-world-a9137a51">world.hey.com: Disasters I've seen in a microservices world 🌟🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A candid engineering post-mortem of catastrophic distributed systems architectures. It warns against over-engineered microservice boundaries, distributed transactions, massive latency chains, and premature optimization that results in 'distributed monoliths'.</li>
|
||
</ul>
|
||
<h3 id="data-management-2">Data Management (2)<a class="headerlink" href="#data-management-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="event-driven-architecture">Event-Driven Architecture<a class="headerlink" href="#event-driven-architecture" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2016)</strong> <a href="https://www.infoq.com/articles/microservices-inside-out">infoq.com: Turning Microservices Inside-Out</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — This piece outlines Martin Kleppmann's paradigm of 'turning the database inside-out'. It advocates for treating state logs as a first-class citizen, enabling downstream services to process and construct specialized read-optimized views.</li>
|
||
</ul>
|
||
<h3 id="design-patterns-3">Design Patterns (3)<a class="headerlink" href="#design-patterns-3" title="Permanent link">¶</a></h3>
|
||
<h4 id="best-practices-2">Best Practices (2)<a class="headerlink" href="#best-practices-2" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.simform.com/blog/microservice-best-practices">simform.com: 10 Microservice Best Practices: The 80/20 Way</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Synthesizes critical strategies for implementing resilient microservice deployments, highlighting domain-driven design, decentralized data management, API gateways, fault-isolation patterns, and automated telemetry ingestion to optimize the 80/20 impact curve.</li>
|
||
</ul>
|
||
<h4 id="catalog">Catalog<a class="headerlink" href="#catalog" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://javarevisited.blogspot.com/2021/09/microservices-design-patterns-principles.html">javarevisited.blogspot.com: Top 10 Microservices Design Patterns and Principles - Examples</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores 10 industry-standard microservices design patterns, providing concrete conceptual diagrams and usage examples for Database-per-Microservice, Event Sourcing, CQRS, Saga Orchestration, and the Backends-for-Frontends (BFF) topology.</li>
|
||
</ul>
|
||
<h4 id="dotnet">DotNet<a class="headerlink" href="#dotnet" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.dotnetcurry.com/microsoft-azure/microservices-architecture">dotnetcurry.com: Microservices Architecture Pattern 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details implementing microservices architectures specifically utilizing modern .NET and Azure frameworks. It explores domain partitioning, local persistent storage designs, and event-driven communications mediated by Azure Service Bus.</li>
|
||
</ul>
|
||
<h4 id="event-driven">Event-Driven<a class="headerlink" href="#event-driven" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.zdnet.com/article/when-microservices-need-event-driven-architecture">zdnet.com: Why microservices need event-driven architecture</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores the symbiotic relationship between microservices and event-driven patterns. Outlines how asynchronous event publication decoupled via brokers like Kafka or RabbitMQ mitigates tight runtime coupling, enhancing overall system fault tolerance and temporal scalability.</li>
|
||
</ul>
|
||
<h4 id="reference-architecture">Reference Architecture<a class="headerlink" href="#reference-architecture" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://geeksarray.com/blog/microservice-architecture-pattern-for-architects">geeksarray.com: Microservice Architecture Pattern for Architects 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Serves as a fundamental reference blueprint for systems architects designing microservices. Explains transaction boundaries, operational logging, API gateway proxies, database isolation, and service discovery mechanics.</li>
|
||
</ul>
|
||
<h3 id="design-principles">Design Principles<a class="headerlink" href="#design-principles" title="Permanent link">¶</a></h3>
|
||
<h4 id="core-principles">Core Principles<a class="headerlink" href="#core-principles" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://developers.redhat.com/articles/2022/01/11/5-design-principles-microservices">developers.redhat.com: 5 design principles for microservices</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines five core engineering principles foundational to sustainable microservices: single responsibility boundaries, loose coupling, data isolation, failure-resilient architecture, and robust observability.</li>
|
||
</ul>
|
||
<h4 id="evaluation">Evaluation<a class="headerlink" href="#evaluation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.simform.com/blog/microservices-design-principles">simform.com: Microservices Design Principles: Do We Really Know It Well Enough? 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Critically evaluates common microservices design patterns, warning against over-engineering. It details the nuances of domain model partition boundaries and the runtime overhead of maintaining absolute microservices autonomy.</li>
|
||
</ul>
|
||
<h3 id="frameworks">Frameworks<a class="headerlink" href="#frameworks" title="Permanent link">¶</a></h3>
|
||
<h4 id="ecosystem">Ecosystem<a class="headerlink" href="#ecosystem" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.simform.com/blog/microservices-framework">simform.com: The Top Go-To Microservices Frameworks for a Scalable Application</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares modern software frameworks specifically built to streamline microservices development (e.g., Spring Boot, Go Kit, NestJS, and Quarkus). Evaluates runtime performance, cloud-native readiness, and tooling ecosystem support.</li>
|
||
</ul>
|
||
<h3 id="implementation">Implementation<a class="headerlink" href="#implementation" title="Permanent link">¶</a></h3>
|
||
<h4 id="cqrs">CQRS<a class="headerlink" href="#cqrs" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://blog.bitsrc.io/implementing-microservices-with-cqrs-2cecb0b09c66">blog.bitsrc.io: Implementing a Microservices Application with CQRS (Command Query Responsibiltiy Segregation)</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Provides a practical, code-driven guide to setting up CQRS in a multi-service Node.js or TypeScript application, explaining how read-replicas are kept synchronized using event messaging systems.</li>
|
||
</ul>
|
||
<h3 id="modernization-1">Modernization (1)<a class="headerlink" href="#modernization-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="automated-migration">Automated Migration<a class="headerlink" href="#automated-migration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://devops.com/vfunction-automates-conversion-of-java-apps-to-microservices">devops.com: Function Automates Conversion of Java Apps to Microservices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Details how automated profiling instruments compile-time and runtime dynamics of legacy enterprise codebases, identifying domain boundaries to programmatically extract microservice packages.</li>
|
||
</ul>
|
||
<h4 id="cdc-patterns">CDC Patterns<a class="headerlink" href="#cdc-patterns" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://developers.redhat.com/articles/2021/06/14/application-modernization-patterns-apache-kafka-debezium-and-kubernetes">developers.redhat.com: Application modernization patterns with Apache Kafka, Debezium, and Kubernetes</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A deep technical dive into change data capture (CDC) as an application modernization accelerator. Demonstrates how combining Debezium, Apache Kafka, and Kubernetes enables seamless database-to-database replication and asynchronous microservice integration.</li>
|
||
</ul>
|
||
<h4 id="monolith-migration">Monolith Migration<a class="headerlink" href="#monolith-migration" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://thenewstack.io/monoliths-to-microservices-4-modernization-best-practices-2">thenewstack.io: Monoliths to Microservices: 4 Modernization Best Practices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Outlines strategic methodologies for decomposing legacy monolithic architectures. Promotes the Strangler Fig pattern, domain-driven boundary definition, database decomposition techniques, and the evolutionary transition of data schemas to prevent transactional failure.</li>
|
||
</ul>
|
||
<h3 id="observability">Observability<a class="headerlink" href="#observability" title="Permanent link">¶</a></h3>
|
||
<h4 id="namespaces">Namespaces<a class="headerlink" href="#namespaces" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://blog.appsignal.com/2021/01/06/microservices-monitoring-using-namespaces-for-data-structuring.html">blog.appsignal.com: Microservices Monitoring: Using Namespaces for Data Structuring 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses structured logging and telemetry tagging practices across distributed microservices. Explains how namespace isolation and unified tagging strategies allow DevOps teams to easily filter performance metrics, traces, and application logs.</li>
|
||
</ul>
|
||
<h3 id="orchestration-1">Orchestration (1)<a class="headerlink" href="#orchestration-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="best-practices-3">Best Practices (3)<a class="headerlink" href="#best-practices-3" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://blog.getambassador.io/microservice-orchestration-best-practices-f32314dd6a12">blog.getambassador.io: Microservice Orchestration Best Practices</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Contrasts orchestration and choreography in distributed microservice topologies. Analyzes the trade-offs of centralized workflow engines versus decentralized event routing, providing architectural criteria to guide deployment choices under scale.</li>
|
||
</ul>
|
||
<h2 id="microservices-and-distributed-systems">Microservices and Distributed Systems<a class="headerlink" href="#microservices-and-distributed-systems" title="Permanent link">¶</a></h2>
|
||
<h3 id="architecture-evolution">Architecture Evolution<a class="headerlink" href="#architecture-evolution" title="Permanent link">¶</a></h3>
|
||
<h4 id="abstractions-and-frameworks">Abstractions and Frameworks<a class="headerlink" href="#abstractions-and-frameworks" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: The Future of Microservices? More Abstractions</summary>
|
||
<p><strong><a href="https://thenewstack.io/microservices/the-future-of-microservices-more-abstractions">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Explores the evolutionary shift of microservices toward higher-level abstraction patterns, such as Dapr and WebAssembly, designed to isolate developers from network complexities. It details how externalizing cross-cutting concerns (state management, pub/sub, service discovery) into sidecars reduces cognitive overhead and boilerplate.</p>
|
||
</details>
|
||
<h4 id="curated-reference">Curated Reference<a class="headerlink" href="#curated-reference" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.redhat.com/en/blog/best-microservices-2021">redhat.com: Top 8 resources for microservices architecture of 2021</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A curated compilation of top-tier resources discussing microservices, distributed logging, service mesh implementations, and event-driven patterns. Provides platform architects with a quick roadmap to explore advanced container patterns and decentralized database design approaches.</li>
|
||
</ul>
|
||
<h3 id="architecture-patterns-1">Architecture Patterns (1)<a class="headerlink" href="#architecture-patterns-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="anti-patterns-2">Anti-Patterns (2)<a class="headerlink" href="#anti-patterns-2" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>itnext.io: You Don’t Need Microservices 🌟</summary>
|
||
<p><strong><a href="https://itnext.io/you-dont-need-microservices-2ad8508b9e27">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Critically evaluates the industry's widespread push for microservices, highlighting cases of 'distributed monoliths' and unnecessary network overhead. Advocates for modular monolith designs as a better option for teams lacking the infrastructure capacity to manage distributed systems.</p>
|
||
</details>
|
||
<h4 id="best-practices-4">Best Practices (4)<a class="headerlink" href="#best-practices-4" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>geeksforgeeks.org: Microservice Architecture – Introduction, Challeneges & Best Practices</summary>
|
||
<p><strong><a href="https://www.geeksforgeeks.org/blogs/microservice-architecture-introduction-challenges-best-practices">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Introduces microservices architecture foundations, delineating major design trade-offs around decentralized data management, inter-service networking, and distributed tracing. Outlines tactical approaches for handling network failures via sagas, API Gateways, and transactional outbox patterns.</p>
|
||
</details>
|
||
<h4 id="component-design">Component Design<a class="headerlink" href="#component-design" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>optisolbusiness.com: 8 Core Components are Microservices Architecture</summary>
|
||
<p><strong><a href="https://www.optisolbusiness.com/insight/8-core-components-of-microservice-architecture">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Details eight critical components of a microservice architecture, including Service Discovery, API Gateways, Service Registries, and Circuit Breakers. Explains how these interconnected components work together to provide reliable communication, load balancing, and fault isolation in production systems.</p>
|
||
</details>
|
||
<h4 id="decision-matrix">Decision Matrix<a class="headerlink" href="#decision-matrix" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>dev.to: When it Pays to Choose Microservices 🌟</summary>
|
||
<p><strong><a href="https://dev.to/typeable/when-it-pays-to-choose-microservices-12h5">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Establishes a rigorous decision framework for migrating from monolithic systems to microservices, balancing organization size, domain boundaries, and cognitive load. The synthesis emphasizes that microservices should only be selected when parallel development velocity and independent horizontal scaling justify the added network complexity.</p>
|
||
</details>
|
||
<h4 id="fundamentals-5">Fundamentals (5)<a class="headerlink" href="#fundamentals-5" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: What Is Microservices Architecture?</summary>
|
||
<p><strong><a href="https://thenewstack.io/microservices/what-is-microservices-architecture">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Beginner</p>
|
||
<p>Introduces microservice-based application design, emphasizing modularity, domain boundaries, and decentralized technical footprints. Compares traditional monolithic patterns against distributed designs, highlighting structural trade-offs, testing models, and continuous integration needs.</p>
|
||
</details>
|
||
<h3 id="deployment-models-1">Deployment Models (1)<a class="headerlink" href="#deployment-models-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="orchestration-options">Orchestration Options<a class="headerlink" href="#orchestration-options" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>semaphoreci.com: 5 Options for Deploying Microservices 🌟</summary>
|
||
<p><strong><a href="https://semaphore.io/blog/deploy-microservices">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Compares five distinct patterns for microservices deployment: single machine/multiple processes, multi-VM hosting, containerization, specialized orchestrators, and serverless runtimes. Outlines the operational costs, performance attributes, and deployment complexities of each option.</p>
|
||
</details>
|
||
<h3 id="software-engineering-principles-1">Software Engineering Principles (1)<a class="headerlink" href="#software-engineering-principles-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="developer-workflow">Developer Workflow<a class="headerlink" href="#developer-workflow" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>hackernoon.com: 9 Basic (and Crucial) Tips for Microservices Developers 🌟</summary>
|
||
<p><strong><a href="https://hackernoon.com/9-basic-and-crucial-tips-for-microservices-developers">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Synthesizes nine core guidelines for microservices engineering, focusing on isolated databases, API versioning, robust service contracts, and distributed tracing integration. Highlights the architectural imperative of treating microservices as loosely coupled, independently deployable domains.</p>
|
||
</details>
|
||
<h3 id="testing-and-reliability-1">Testing and Reliability (1)<a class="headerlink" href="#testing-and-reliability-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="fault-tolerance">Fault Tolerance<a class="headerlink" href="#fault-tolerance" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>christophermeiklejohn.com: Understanding why Resilience Faults in Microservice Applications Occur</summary>
|
||
<p><strong><a href="https://christophermeiklejohn.com/filibuster/2022/03/19/understanding-faults.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Evaluates systemic failure modes in microservice environments, emphasizing issues like cascading failures, misconfigured circuit breakers, and network partition timeouts. Shows how programmatic resilience-testing strategies can identify failure-handling errors during early design.</p>
|
||
</details>
|
||
<h2 id="operations">Operations<a class="headerlink" href="#operations" title="Permanent link">¶</a></h2>
|
||
<h3 id="disaster-recovery">Disaster Recovery<a class="headerlink" href="#disaster-recovery" title="Permanent link">¶</a></h3>
|
||
<h4 id="cloud-native-1">Cloud-Native (1)<a class="headerlink" href="#cloud-native-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://thenewstack.io/disaster-recovery-is-different-for-the-cloud">thenewstack.io: Disaster Recovery Is Different for the Cloud</a> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Highlights the key differences between legacy cold-standby disaster recovery models and modern, cloud-native active-active paradigms. Highlights regional replication, automatic failover orchestration, and chaotic failure injection.</li>
|
||
</ul>
|
||
<h4 id="devops-1">DevOps (1)<a class="headerlink" href="#devops-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.bunnyshell.com/blog/disaster-recovery-devops">bunnyshell.com: DR in DevOps: How to Guarantee an Effective Disaster Recovery Plan with DevOps</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores integrating DR validation directly within DevOps lifecycles. Details setting up automated environment cloning, infrastructure-as-code state synchronization, and defining recovery point objectives (RPO) and recovery time objectives (RTO).</li>
|
||
</ul>
|
||
<h2 id="orchestration-2">Orchestration (2)<a class="headerlink" href="#orchestration-2" title="Permanent link">¶</a></h2>
|
||
<h3 id="kubernetes-2">Kubernetes (2)<a class="headerlink" href="#kubernetes-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="anti-patterns-3">Anti-Patterns (3)<a class="headerlink" href="#anti-patterns-3" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://paulbutler.org/2024/the-haters-guide-to-kubernetes">paulbutler.org: The hater’s guide to Kubernetes</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Offers a pragmatic, critical look at Kubernetes' administrative complexity. Outlines strategic advice for startups, warning against premature orchestration setup while detailing how to run lean, low-overhead Kubernetes deployments.</li>
|
||
</ul>
|
||
<h4 id="dependency-isolation">Dependency Isolation<a class="headerlink" href="#dependency-isolation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://itnext.io/isolating-and-managing-dependencies-in-12-factor-microservice-applications-with-kubernetes-988638f8bc6d">itnext.io: Isolating and Managing Dependencies in 12-factor Microservice Applications — with Kubernetes</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Focuses specifically on Factor II (Dependencies). Demonstrates isolating system dependencies using container images, multi-stage Dockerfiles, and initContainers to orchestrate external DB readiness checks before app startup.</li>
|
||
</ul>
|
||
<h4 id="microservices-6">Microservices (6)<a class="headerlink" href="#microservices-6" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://itnext.io/12-factor-microservice-applications-on-kubernetes-db913008b018">itnext.io: 12 factor Microservice applications — on Kubernetes</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A deep dive into implementing the complete 12-Factor framework within Kubernetes. Highlights strict environmental isolation, declarative deployment processes, and scaling microservices with pod replicas.</li>
|
||
</ul>
|
||
<h4 id="paradigms-1">Paradigms (1)<a class="headerlink" href="#paradigms-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://traefik.io/blog/pets-vs-cattle-the-future-of-kubernetes-in-2022">traefik.io: Pets vs. Cattle: The Future of Kubernetes in 2022</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores how modern Kubernetes clusters treat clusters, nodes, and ingress configurations as stateless, disposable entities (cattle). Examines automation engines and dynamic routing protocols like Traefik to abstract network edges.</li>
|
||
</ul>
|
||
<h4 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://thenewstack.io/learn-12-factor-apps-before-kubernetes">thenewstack.io: Learn 12 Factor Apps Before Kubernetes</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Argues that mastering cloud-native architectural patterns (such as 12-Factor principles) is essential before deploying workloads on complex container orchestration fabrics like Kubernetes to prevent broken anti-patterns.</li>
|
||
</ul>
|
||
<h4 id="processes">Processes<a class="headerlink" href="#processes" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://itnext.io/processes-for-12-factor-microservice-applications-70551a9021b">itnext.io: Processes — for 12-factor Microservice Applications</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Unpacks Factor VI (Processes), requiring apps to run as stateless, shared-nothing executions. Details how to handle sticky sessions externally via Redis and run dynamic workloads cleanly across Kubernetes pods.</li>
|
||
</ul>
|
||
<h4 id="twelve-factor-app-1">Twelve-Factor App (1)<a class="headerlink" href="#twelve-factor-app-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.pluralsight.com/resources/blog/cloud/twelve-factor-apps-in-kubernetes">acloudguru.com: Twelve-Factor Apps in Kubernetes</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Demonstrates mapping the 12-Factor framework directly onto Kubernetes primitives. Maps ConfigMaps and Secrets to Factor III (Config), and Deployments/ReplicaSets to Factor IX (Disposability).</li>
|
||
</ul>
|
||
<h4 id="workloads">Workloads<a class="headerlink" href="#workloads" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://thenewstack.io/kubernetes-evolution-from-microservices-to-batch-processing-powerhouse">thenewstack.io: Kubernetes Evolution: From Microservices to Batch Processing Powerhouse 🌟🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explores Kubernetes' evolution from a simple microservices hosting platform to an advanced orchestrator for heavy batch processing, AI/ML training runs, and high-performance computing (HPC) jobs.</li>
|
||
</ul>
|
||
<h2 id="platform-engineering-3">Platform Engineering (3)<a class="headerlink" href="#platform-engineering-3" title="Permanent link">¶</a></h2>
|
||
<h3 id="paas-solutions">PaaS Solutions<a class="headerlink" href="#paas-solutions" title="Permanent link">¶</a></h3>
|
||
<h4 id="market-shifts">Market Shifts<a class="headerlink" href="#market-shifts" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoworld.com: The decline of Heroku PaaS</summary>
|
||
<p><strong><a href="https://www.infoworld.com/article/2264177/the-decline-of-heroku.html">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A diagnostic retrospective detailing the structural decline of Heroku in the developer ecosystem. It traces how a lack of feature innovation, persistent pricing structure limitations, and the massive rise of container-based orchestration engines and modern edge platforms drove teams away from classic PaaS models.</p>
|
||
</details>
|
||
<h3 id="reference-architectures">Reference Architectures<a class="headerlink" href="#reference-architectures" title="Permanent link">¶</a></h3>
|
||
<h4 id="aws">AWS<a class="headerlink" href="#aws" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://humanitec.com/reference-architectures/aws">humanitec.com: Platform reference architecture on AWS</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Illustrates modern Platform Engineering frameworks on AWS. Details integrating EKS, RDS, and AWS Secrets Manager with Score and Humanitec to build scalable, low-friction self-service infrastructure portals.</li>
|
||
</ul>
|
||
<h4 id="azure">Azure<a class="headerlink" href="#azure" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://humanitec.com/reference-architectures/azure">humanitec.com: Platform reference architecture on Azure</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — A production-ready blueprint mapping internal developer platforms (IDP) to native Azure resources. Details how to utilize AKS, Azure Key Vault, and Terraform to implement automated, secure self-service infrastructure pipelines.</li>
|
||
</ul>
|
||
<h4 id="gcp">GCP<a class="headerlink" href="#gcp" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://humanitec.com/reference-architectures">humanitec.com: Platform reference architecture on GCP</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — Outlines enterprise platform blueprints tailored for Google Cloud Platform. Combines GKE, Cloud Run, and Secret Manager under a unified platform orchestrator layer to drive developer velocity while keeping governance secure.</li>
|
||
</ul>
|
||
<h3 id="self-service">Self-Service<a class="headerlink" href="#self-service" title="Permanent link">¶</a></h3>
|
||
<h4 id="case-studies-1">Case Studies (1)<a class="headerlink" href="#case-studies-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://thenewstack.io/what-we-learned-from-enabling-developer-self-service">thenewstack.io: What We Learned from Enabling Developer Self-Service</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Analyzes the lessons learned from deploying internal developer platforms. Emphasizes that successful self-service portals require careful user-research, avoiding over-automation, and continuous developer feedback loops.</li>
|
||
</ul>
|
||
<h4 id="concepts-1">Concepts (1)<a class="headerlink" href="#concepts-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.weave.works/blog/what-is-a-self-service-developer-platform">weave.works: What is a self-service developer platform and why does it matter?</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details the philosophy of Platform Engineering through self-service developer portals. Explains how curating 'golden paths' reduces cognitive load on developers, allowing them to spin up database and infrastructure templates securely.</li>
|
||
</ul>
|
||
<h3 id="service-catalogs">Service Catalogs<a class="headerlink" href="#service-catalogs" title="Permanent link">¶</a></h3>
|
||
<h4 id="microservices-governance">Microservices Governance<a class="headerlink" href="#microservices-governance" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.cortex.io/post/why-you-need-a-microservices-catalog-tool">getcortexapp.com: Why You Need a Microservices Catalog Tool</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Details the operational sprawl that occurs as organizations scale their microservices topologies. Proposes centralized service catalogs (similar to Backstage or Cortex) to map dependencies, track security compliance, enforce reliability standards, and assign service ownership across teams.</li>
|
||
</ul>
|
||
<h2 id="professional-development-2">Professional Development (2)<a class="headerlink" href="#professional-development-2" title="Permanent link">¶</a></h2>
|
||
<h3 id="career-guidance">Career Guidance<a class="headerlink" href="#career-guidance" title="Permanent link">¶</a></h3>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.forbes.com/sites/adunolaadeshola/2021/04/28/13-signs-youre-selling-yourself-short-in-your-career">forbes.com: 13 Signs You’re Selling Yourself Short In Your Career</a> <span class='md-tag md-tag--warning'>[MARKDOWN CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An executive career-strategy publication focusing on professional growth, self-worth, and leadership traits. Though non-technical, 2026 engineering team development paradigms heavily emphasize these foundational soft skills alongside cloud proficiency to foster highly autonomous Platform Engineering structures.</li>
|
||
</ul>
|
||
<h2 id="reliability-engineering">Reliability Engineering<a class="headerlink" href="#reliability-engineering" title="Permanent link">¶</a></h2>
|
||
<h3 id="resilience-patterns-1">Resilience Patterns (1)<a class="headerlink" href="#resilience-patterns-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="infrastructure-stability">Infrastructure Stability<a class="headerlink" href="#infrastructure-stability" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: 7 Best Practices to Build and Maintain Resilient Applications and Infrastructure</summary>
|
||
<p><strong><a href="https://thenewstack.io/7-best-practices-to-build-and-maintain-resilient-applications-and-infrastructure">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Synthesizes core software engineering and site reliability practices to maintain resilient systems under load. Key patterns explored include chaos engineering, circuit breaking, automated canary deployments, proactive monitoring, and robust failure domain isolation.</p>
|
||
</details>
|
||
<h2 id="security">Security<a class="headerlink" href="#security" title="Permanent link">¶</a></h2>
|
||
<h3 id="software-protection">Software Protection<a class="headerlink" href="#software-protection" title="Permanent link">¶</a></h3>
|
||
<h4 id="obfuscation">Obfuscation<a class="headerlink" href="#obfuscation" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.welivesecurity.com/es/recursos-herramientas/ofuscacion-de-codigo-arte-ciberseguridad">welivesecurity.com: La ofuscación de código: un arte que reina en la ciberseguridad</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explica cómo la ofuscación de código protege la propiedad intelectual y dificulta la ingeniería inversa por parte de actores maliciosos. Describe métodos comunes como el cambio de flujos de control y cifrado de cadenas.</li>
|
||
</ul>
|
||
<h2 id="software-architecture">Software Architecture<a class="headerlink" href="#software-architecture" title="Permanent link">¶</a></h2>
|
||
<h3 id="application-modernization-1">Application Modernization (1)<a class="headerlink" href="#application-modernization-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="legacy-migration">Legacy Migration<a class="headerlink" href="#legacy-migration" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>Modernize legacy applications with containers, microservices</summary>
|
||
<p><strong><a href="https://www.techtarget.com/searchcloudcomputing/feature/Modernize-legacy-applications-with-containers-microservices">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Examines methodologies for containerizing and decomposing legacy applications into microservices. It highlights refactoring patterns, the strangler fig pattern, and the steps required to isolate state and transition monolithic database architectures to distributed cloud-native databases.</p>
|
||
</details>
|
||
<h3 id="event-driven-systems">Event-Driven Systems<a class="headerlink" href="#event-driven-systems" title="Permanent link">¶</a></h3>
|
||
<h4 id="asynchronous-messaging">Asynchronous Messaging<a class="headerlink" href="#asynchronous-messaging" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: React in Real-Time with Event-Driven APIs</summary>
|
||
<p><strong><a href="https://thenewstack.io/react-in-real-time-with-event-driven-apis">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Evaluates the shifting architectural landscape towards event-driven API patterns. Discusses protocols and specifications like WebSockets, Server-Sent Events, and AsyncAPI, analyzing how they enable real-time asynchronous streaming and responsive microservice architectures.</p>
|
||
</details>
|
||
<h3 id="microservices-7">Microservices (7)<a class="headerlink" href="#microservices-7" title="Permanent link">¶</a></h3>
|
||
<h4 id="decomposition-patterns">Decomposition Patterns<a class="headerlink" href="#decomposition-patterns" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoq.com: Migrating Monoliths to Microservices with Decomposition and Incremental Changes</summary>
|
||
<p><strong><a href="https://www.infoq.com/articles/migrating-monoliths-to-microservices-with-decomposition">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A highly structured technical article focused on database-first and domain-driven monolith decomposition strategies. Examines step-by-step decoupling techniques, including interface abstractions, event-driven data synchronization, and managing temporary shared states without degrading uptime.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>codeopinion.com: Splitting up a Monolith into Microservices 🌟</summary>
|
||
<p><strong><a href="https://codeopinion.com/splitting-up-a-monolith-into-microservices">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A tactical architectural guide detailing strategies to transition from a single monolithic code base to a decoupled microservice topology. Outlines bounded contexts, logical code isolation within the monolith, and utilizing transactional outbox patterns to prevent distributed split-brain scenarios.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>blog.heroku.com: Deconstructing Monolithic Applications into Services</summary>
|
||
<p><strong><a href="https://www.heroku.com/blog/monolithic-applications-into-services">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A detailed playbook on dividing monolithic backends into cohesive, independent services. It discusses domain-driven design (DDD) boundaries, API gateway design, database decomposition, and how to manage the incremental migration phases to minimize downtime.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>vmware.com: How to Deconstruct a Monolith using Microservices – Getting Ready for Cloud-Native</summary>
|
||
<p><strong><a href="https://blogs.vmware.com/vov/2018/08/06/how-to-deconstruct-a-monolith-using-microservices-getting-ready-for-cloud-native">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Provides an enterprise architectural path for decomposing traditional monoliths into distributed services. It focuses on identifying bounded contexts, managing cross-service communication via asynchronous events, and restructuring development teams around microservices boundaries.</p>
|
||
</details>
|
||
<h4 id="design-patterns-4">Design Patterns (4)<a class="headerlink" href="#design-patterns-4" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoq.com: Principles for Microservice Design: Think IDEALS, Rather than SOLID</summary>
|
||
<p><strong><a href="https://www.infoq.com/articles/microservices-design-ideals">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Introduces the IDEALS framework (Interface segregation, Deployability, Event-driven, Availability, Latency, State management) as the modern replacement for SOLID design principles in distributed systems. Evaluates how microservices necessitate a focus on network and execution boundaries rather than object relations.</p>
|
||
</details>
|
||
<details class="note">
|
||
<summary>thenewstack.io: Microservices vs. Monoliths: An Operational Comparison</summary>
|
||
<p><strong><a href="https://thenewstack.io/microservices/microservices-vs-monoliths-an-operational-comparison">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>A comprehensive operational comparison of monolithic and microservices architectural patterns. It details how the distribution of systems shifts problems from single-process memory management to complex network-level routing, distributed tracing, eventual consistency, and CI/CD pipelines.</p>
|
||
</details>
|
||
<h4 id="distributed-transactions">Distributed Transactions<a class="headerlink" href="#distributed-transactions" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>infoq.com: Saga Orchestration for Microservices Using the Outbox Pattern</summary>
|
||
<p><strong><a href="https://www.infoq.com/articles/saga-orchestration-outbox">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>A detailed exploration of Saga Orchestration coupled with the Transactional Outbox Pattern to maintain eventual consistency in distributed databases. Examines architectural tradeoffs of orchestration versus choreography and how to implement CDC (Change Data Capture) via Debezium.</p>
|
||
</details>
|
||
<h4 id="maturity-models">Maturity Models<a class="headerlink" href="#maturity-models" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>blog.container-solutions.com: How Mature Is Your Microservices Architecture? 🌟</summary>
|
||
<p><strong><a href="https://blog.container-solutions.com/how-mature-is-your-microservices-architecture">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Establishes a systematic maturity assessment framework for microservice architectures. Evaluates technical implementation levels across continuous deployment pipelines, automated system testing, distributed observability, configuration injection, and organizational alignment.</p>
|
||
</details>
|
||
<h4 id="monolith-transition">Monolith Transition<a class="headerlink" href="#monolith-transition" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2023)</strong> <a href="https://www.aboutamazon.com/what-we-do/entertainment">primevideotech.com: Scaling up the Prime Video audio/video monitoring service and reducing costs by 90%</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--secondary'>[CASE STUDY]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The famous Prime Video case study describing the refactoring of a highly distributed, serverless orchestration pipeline back to a consolidated monolithic service. Demonstrates how eliminating network serialization and step functions reduced operating costs by 90%.</li>
|
||
</ul>
|
||
<h4 id="technology-selection">Technology Selection<a class="headerlink" href="#technology-selection" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>devops.com: Why Boring Tech is Best to Avoid a Microservices Mess</summary>
|
||
<p><strong><a href="https://devops.com/why-boring-tech-is-best-to-avoid-a-microservices-mess">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Arguments for architectural conservatism when adopting a highly distributed microservices paradigm. By utilizing mature, 'boring' technology (e.g., PostgreSQL, REST/gRPC, stable programming runtimes), engineering teams can isolate and absorb the inherent complexity of distributed systems coordination.</p>
|
||
</details>
|
||
<h4 id="value-proposition-1">Value Proposition (1)<a class="headerlink" href="#value-proposition-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://devops.com/6-advantages-of-microservices">devops.com: 6 Advantages of Microservices</a> 🌟🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Outlines the foundational architectural advantages of adopting a microservices pattern, including technological flexibility, autonomous deployability, localized scaling, fault isolation, and improved team ownership over distinct domain services.</li>
|
||
</ul>
|
||
<h3 id="modernization-2">Modernization (2)<a class="headerlink" href="#modernization-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="strangler-pattern">Strangler Pattern<a class="headerlink" href="#strangler-pattern" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.harness.io/products/service-reliability-management">overops.com: Strangler Pattern: How to Deal With Legacy Code During the Container Revolution</a> <span class='md-tag md-tag--critical'>[LEGACY]</span> — Details the mechanics of the Strangler Fig pattern for migrating legacy codebases into containerized microservices. Analyzes API routing strategies, incremental migration boundaries, and monitoring paradigms for managing dual runtimes.</li>
|
||
</ul>
|
||
<h3 id="monoliths-2">Monoliths (2)<a class="headerlink" href="#monoliths-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="modular-monolith">Modular Monolith<a class="headerlink" href="#modular-monolith" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://www.kamilgrzybek.com/blog/posts/modular-monolith-primer">kamilgrzybek.com: Modular Monolith: A Primer 🌟</a> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — An architectural deep dive arguing that modular monoliths are a robust alternative to premature microservices. Outlines domain boundaries, strict module encapsulation, asynchronous internal communication, and database schema segregation rules.</li>
|
||
</ul>
|
||
<h2 id="software-delivery">Software Delivery<a class="headerlink" href="#software-delivery" title="Permanent link">¶</a></h2>
|
||
<h3 id="devops-2">DevOps (2)<a class="headerlink" href="#devops-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="industry-trends-1">Industry Trends (1)<a class="headerlink" href="#industry-trends-1" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://www.zdnet.com/article/the-year-ahead-in-devops-and-agile-more-automation-more-business-involvement-needed">zdnet.com: The year ahead in DevOps and agile: bring on the automation, bring on the business involvement</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines evolutionary trends in agile delivery and DevOps, emphasizing the integration of business operations with engineering pipelines. It underscores automation, value-stream mapping, and the integration of artificial intelligence into CI/CD pipelines.</li>
|
||
</ul>
|
||
<h2 id="software-engineering-2">Software Engineering (2)<a class="headerlink" href="#software-engineering-2" title="Permanent link">¶</a></h2>
|
||
<h3 id="architecture-patterns-2">Architecture Patterns (2)<a class="headerlink" href="#architecture-patterns-2" title="Permanent link">¶</a></h3>
|
||
<h4 id="microservices-8">Microservices (8)<a class="headerlink" href="#microservices-8" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2024)</strong> <a href="https://www.dynatrace.com/knowledge-base/microservices">dynatrace.com: What are microservices? All you need to know</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A high-level architectural overview exploring the decoupling of corporate monoliths into agile microservices. Discusses structural changes, challenges in service discovery, and the crucial role of tracing telemetry for maintaining state consistency.</li>
|
||
</ul>
|
||
<h3 id="education-1">Education (1)<a class="headerlink" href="#education-1" title="Permanent link">¶</a></h3>
|
||
<h4 id="systems-programming">Systems Programming<a class="headerlink" href="#systems-programming" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>Build Your Own X</summary>
|
||
<p><strong><a href="https://github.com/codecrafters-io/build-your-own-x">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>An immensely popular community-driven compilation of step-by-step guides for building complex software systems (compilers, databases, operating systems, Docker) from scratch. Perfect for deep pedagogical exploration of core engineering systems.</p>
|
||
</details>
|
||
<h3 id="full-stack-fundamentals">Full-Stack Fundamentals<a class="headerlink" href="#full-stack-fundamentals" title="Permanent link">¶</a></h3>
|
||
<h4 id="architectural-roles">Architectural Roles<a class="headerlink" href="#architectural-roles" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2020)</strong> <a href="https://www.viewnext.com/front-end-vs-back-end">viewnext.com: Front End vs Back End (spanish)</a> <span class='md-tag md-tag--warning'>[SPANISH CONTENT]</span> 🌟🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Explica la división fundamental del desarrollo de software entre el Front End y el Back End. Describe las tecnologías clave de la capa de presentación (HTML, CSS, JavaScript frameworks) y las arquitecturas de servidor de la capa lógica, bases de datos y APIs que las sostienen.</li>
|
||
</ul>
|
||
<h3 id="performance-optimization">Performance Optimization<a class="headerlink" href="#performance-optimization" title="Permanent link">¶</a></h3>
|
||
<h4 id="system-architecture">System Architecture<a class="headerlink" href="#system-architecture" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>thenewstack.io: The Scalability Myth</summary>
|
||
<p><strong><a href="https://thenewstack.io/the-scalability-myth">Access Resource</a></strong> 🌟🌟🌟🌟 | Level: Intermediate</p>
|
||
<p>Deconstructs the architectural fixation on infinite scaling patterns, exposing the operational costs and technical debt of prematurely optimizing for hyper-scale. Explores real-world performance tuning, database indexing, and efficient code paths as more cost-effective alternatives.</p>
|
||
</details>
|
||
<h3 id="web-development">Web Development<a class="headerlink" href="#web-development" title="Permanent link">¶</a></h3>
|
||
<h4 id="nodejs">NodeJS<a class="headerlink" href="#nodejs" title="Permanent link">¶</a></h4>
|
||
<details class="note">
|
||
<summary>NodeJS Best Practices (Spanish Translation)</summary>
|
||
<p><strong><a href="https://github.com/goldbergyoni/nodebestpractices/blob/spanish-translation/README.spanish.md">Access Resource</a></strong> 🌟🌟🌟🌟🌟 | Level: Advanced</p>
|
||
<p>Spanish localization of the leading Node.js architecture and security handbook. It offers comprehensive design blueprints covering error handling, clean architecture, security, production readiness, and testing guidelines for scalable enterprise systems.</p>
|
||
</details>
|
||
<h2 id="software-engineering-practices">Software Engineering Practices<a class="headerlink" href="#software-engineering-practices" title="Permanent link">¶</a></h2>
|
||
<h3 id="developer-productivity">Developer Productivity<a class="headerlink" href="#developer-productivity" title="Permanent link">¶</a></h3>
|
||
<h4 id="roadmaps">Roadmaps<a class="headerlink" href="#roadmaps" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2021)</strong> <a href="https://dev.to/ender_minyard/full-stack-developer-s-roadmap-2k12">Full Stack Developer's Roadmap 🌟</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A holistic guide detailing modern career trajectories and essential technical skills for full-stack developers. While covering classic frontend and backend tools, it places significant emphasis on containerization (Docker) and modern microservices orchestration patterns.</li>
|
||
</ul>
|
||
<h4 id="toolkits">Toolkits<a class="headerlink" href="#toolkits" title="Permanent link">¶</a></h4>
|
||
<ul>
|
||
<li><strong>(2022)</strong> <a href="https://ubiqum.com/blog/20-software-development-tools-that-will-make-you-more-productive">ubiqum.com: 20 Software Development Tools that will make you more productive</a> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Curated technical list analyzing software development tools engineered to enhance engineering velocity. Explores IDE extensions, local container utilities, source control clients, and task automators critical for scaling developer operations.</li>
|
||
</ul>
|
||
<hr />
|
||
<p>💡 <strong>Explore Related:</strong> <a href="../demos/">Demos</a> | <a href="../kubernetes/">Kubernetes</a> | <a href="../cloud-arch-diagrams/">Cloud Arch Diagrams</a></p>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
</article>
|
||
</div>
|
||
|
||
|
||
<script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>
|
||
</div>
|
||
|
||
<button type="button" class="md-top md-icon" data-md-component="top" hidden>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8z"/></svg>
|
||
Back to top
|
||
</button>
|
||
|
||
</main>
|
||
|
||
<footer class="md-footer">
|
||
|
||
<div class="md-footer-meta md-typeset">
|
||
<div class="md-footer-meta__inner md-grid">
|
||
<div class="md-copyright">
|
||
|
||
<div class="md-copyright__highlight">
|
||
Copyright © 2026 Nubenetes Agentic Intelligence
|
||
</div>
|
||
|
||
|
||
Made with
|
||
<a href="https://squidfunk.github.io/mkdocs-material/" target="_blank" rel="noopener">
|
||
Material for MkDocs
|
||
</a>
|
||
|
||
</div>
|
||
|
||
|
||
<div class="md-social">
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://github.com/nubenetes/awesome-kubernetes" target="_blank" rel="noopener" title="github.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M173.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6m-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3m44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9M252.8 8C114.1 8 8 113.3 8 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C436.2 457.8 504 362.9 504 252 504 113.3 391.5 8 252.8 8M105.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1m-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7m32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1m-11.4-14.7c-1.6 1-1.6 3.6 0 5.9s4.3 3.3 5.6 2.3c1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://twitter.com/nubenetes" target="_blank" rel="noopener" title="twitter.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M459.4 151.7c.3 4.5.3 9.1.3 13.6 0 138.7-105.6 298.6-298.6 298.6-59.5 0-114.7-17.2-161.1-47.1 8.4 1 16.6 1.3 25.3 1.3 49.1 0 94.2-16.6 130.3-44.8-46.1-1-84.8-31.2-98.1-72.8 6.5 1 13 1.6 19.8 1.6 9.4 0 18.8-1.3 27.6-3.6-48.1-9.7-84.1-52-84.1-103v-1.3c14 7.8 30.2 12.7 47.4 13.3-28.3-18.8-46.8-51-46.8-87.4 0-19.5 5.2-37.4 14.3-53C87.4 130.8 165 172.4 252.1 176.9c-1.6-7.8-2.6-15.9-2.6-24C249.5 95.1 296.3 48 354.4 48c30.2 0 57.5 12.7 76.7 33.1 23.7-4.5 46.5-13.3 66.6-25.3-7.8 24.4-24.4 44.8-46.1 57.8 21.1-2.3 41.6-8.1 60.4-16.2-14.3 20.8-32.2 39.3-52.6 54.3"/></svg>
|
||
</a>
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
<a href="https://www.linkedin.com/groups/1937212/" target="_blank" rel="noopener" title="www.linkedin.com" class="md-social__link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><!--! Font Awesome Free 7.1.0 by @fontawesome - https://fontawesome.com License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License) Copyright 2025 Fonticons, Inc.--><path d="M416 32H31.9C14.3 32 0 46.5 0 64.3v383.4C0 465.5 14.3 480 31.9 480H416c17.6 0 32-14.5 32-32.3V64.3c0-17.8-14.4-32.3-32-32.3M135.4 416H69V202.2h66.5V416zM102.2 96a38.5 38.5 0 1 1 0 77 38.5 38.5 0 1 1 0-77m282.1 320h-66.4V312c0-24.8-.5-56.7-34.5-56.7-34.6 0-39.9 27-39.9 54.9V416h-66.4V202.2h63.7v29.2h.9c8.9-16.8 30.6-34.5 62.9-34.5 67.2 0 79.7 44.3 79.7 101.9z"/></svg>
|
||
</a>
|
||
|
||
</div>
|
||
|
||
</div>
|
||
</div>
|
||
</footer>
|
||
|
||
</div>
|
||
<div class="md-dialog" data-md-component="dialog">
|
||
<div class="md-dialog__inner md-typeset"></div>
|
||
</div>
|
||
|
||
|
||
|
||
|
||
|
||
<script id="__config" type="application/json">{"annotate": null, "base": "..", "features": ["navigation.tabs", "navigation.tabs.sticky", "navigation.top", "navigation.tracking", "navigation.sections", "navigation.expand", "navigation.indexes", "search.suggest", "search.highlight", "search.share", "content.code.copy", "content.action.view", "content.action.edit", "content.tooltips", "navigation.prune", "toc.integrate"], "search": "../assets/javascripts/workers/search.2c215733.min.js", "tags": null, "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"provider": "mike"}}</script>
|
||
|
||
|
||
<script src="../assets/javascripts/bundle.79ae519e.min.js"></script>
|
||
|
||
<script src="../static/v2_filter.js"></script>
|
||
|
||
|
||
</body>
|
||
</html> |