diff --git a/michael bingel b/michael bingel
new file mode 100644
index 0000000..7c85d08
--- /dev/null
+++ b/michael bingel	
@@ -0,0 +1,29 @@
+Recommended content:
+From a single server MVP to scale – easy with Portainer
+We assume you already have you web-app running within a container
+Select your orchestration (what is best practice, what are reasons, what are limits ???)
+
+- Kubernetes
+- Docker Swarm
+
+10-100 server : Docker Swarm
+50-200 server: microk8s (easy as docker swarm, but prepare for further growth ???)
+100-100.000: kubernetes
+Setup infrastructure (swarm or microk8s)
+Launch servers (virtual or bare metal)
+Create master
+Join further nodes
+Launch Portainer
+…
+Launch reverse proxy via Portainer
+The reverse proxy will automatically load balance all incoming requests to the web-app containers
+The proxy will hot reload when containers change, not interrupt ongoing and long-running requests (?)
+The proxy can automatically forward to services based on sub-domains and/or paths via labels (?)
+Launch services (web-app and others)
+Launch you services with Portainer, set labels for sub-domain and/or path
+Example: www (wordpress), api (nodejs) (?)
+Database: only one instance per server on dedicated servers
+Scale up
+Check metrics
+Easily scale services up and down, add more servers
+7. b. Manage credentials, pass them to the web-app so it can connect to the database.