Check out the repo with all concepts from this post: https://github.com/alonronin/rn2021
In Eric Reis’ “The Lean Startup” he talks about the Build — Measure — Learn feedback loop. And why is that important? because in my opinion our users makes our product great, and the fastest we reach them out, the faster we can get the new data and perfected our product.
When we talk about the infrastructure we’re immediately switch our context towards the DevOps worlds. However, the DevOps is merely 25% of our infrastructure, and I believe that the infrastructure is 80% of our product.
So I talk about also our Code Infrastructure, the way and tools we use to communicate with our product’s stakeholders, and it can be the product, designers, users, internal users etc., and also establishing trust between us and share our expectations as describe in Rozensky & Woods’ “Architecture Description — Viewpoints and Perspectives”.
We can write as many user stories as we need, and define a fine grained specs but it is never translate well to final product until we are seeing it visually.
Visual spec can gives us the ability to really understand our product and user experience before we start to convert it to code, this gives us a lot of span to change our requirement and products’ flow before we are using our most expensive resource — the development.
And it is not ends with visual spec, because we want also our stakeholders to see our progress, even if it is not fully implemented and passed thru our dev flow pipeline (PR, Code Review, Testing, QA etc.)
So we need the ability to also ship our artifacts internally, and fast.
Kubernetes is a container orchestration software that enables us to ship our code as docker container and have a reverse proxy, known as Ingress, out of the box that connects our different services.
This enables us to break our software to smaller parts and ship it as one unit.
The following selections are very opinionated by myself, however I believe you can choose whatever speeds up your productivity, development wise.
I chose Pulumi for our DevOps operation of creating our EKS cluster and create the relevant Policies and Service Accounts we need.
Check out my post on how to Setup EKS Cluster with Pulumi and Helm.