Authors Oliver Jumpertz
7 days
30 days
All time
Recent
Popular
"Blockchain technology is energy-intensive..." => No, it doesn't have to be.
Let's look at Proof-Of-Stake, an alternative to the energy-intensive Proof-Of-Work algorithm.
🧵🔽
1️⃣ A Quick Recap On Proof-Of-Work
A Proof-Of-Work algorithm requires miners to do a certain amount of work that is compute-intensive to gain access to a service or the right to do something. This algorithm, by design, also requires that the work done shall not ...
... be reusable for anything else than what it was performed for. This lies at the core of the security concept of a blockchain. To gain the right to append a new block to a chain and to get some currency as a reward, there is work to be done, and this work must be verifyable.
That work is a race between different miners. Many miners try to compete and to be the first to find the answer to a problem presented to them. This implies that a lot of energy is wasted as only the first correct solution is accepted.
You can find a more detailed thread on Proof-Of-Work
Let's look at Proof-Of-Stake, an alternative to the energy-intensive Proof-Of-Work algorithm.
🧵🔽
1️⃣ A Quick Recap On Proof-Of-Work
A Proof-Of-Work algorithm requires miners to do a certain amount of work that is compute-intensive to gain access to a service or the right to do something. This algorithm, by design, also requires that the work done shall not ...
... be reusable for anything else than what it was performed for. This lies at the core of the security concept of a blockchain. To gain the right to append a new block to a chain and to get some currency as a reward, there is work to be done, and this work must be verifyable.
That work is a race between different miners. Many miners try to compete and to be the first to find the answer to a problem presented to them. This implies that a lot of energy is wasted as only the first correct solution is accepted.
You can find a more detailed thread on Proof-Of-Work
Proof-Of-Work is the name of a cryptographic algorithm that is used for some blockchains when new blocks are to be appended to the chain.
— Oliver Jumpertz (@oliverjumpertz) April 3, 2021
Let's take a higher-level look at how this one works, shall we?
\U0001f9f5\U0001f53d
Kubernetes vs Serverless offerings
Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?
Well, let's try to look at both approaches and draw our own conclusions!
🧵⏬
1️⃣ A quick look at Kubernetes
Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.
There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you: https://t.co/nuH4dmpUmf), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.
After all that, you need to write specs which instruct Kubernetes what the desired state of your application is, and finally let Kubernetes do its work. It's certainly not a NoOps platform, as you'll still need people knowing what they do and how to handle Kubernetes.
⏬
2️⃣ A quick look at (some!) serverless offerings
The offer is pretty simple: You write the code, the platform handles everything else for you. It's basically leaning far to the NoOps side. There is not much to manage anymore.
Take your Next.js / Nuxt.js app, point the ...
Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?
Well, let's try to look at both approaches and draw our own conclusions!
🧵⏬
1️⃣ A quick look at Kubernetes
Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.
There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you: https://t.co/nuH4dmpUmf), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.
After all that, you need to write specs which instruct Kubernetes what the desired state of your application is, and finally let Kubernetes do its work. It's certainly not a NoOps platform, as you'll still need people knowing what they do and how to handle Kubernetes.
⏬
2️⃣ A quick look at (some!) serverless offerings
The offer is pretty simple: You write the code, the platform handles everything else for you. It's basically leaning far to the NoOps side. There is not much to manage anymore.
Take your Next.js / Nuxt.js app, point the ...
