BC SOFTWARE
Saved by @Alex1Powell

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 ...
... platform (Vercel e.g.) to the repository and then it does its magic. It handles deployment, it handles scaling, it offers metrics, it offers a lot. Sounds like a great offering, doesn't it?

Or take Amplify for example. It offers an integrated full-stack experience.
Simply use the CLI to add an API, or drop your functions into a special folder and let Amplify handle setting up Lambda for you. No need to do everything manually anymore, and also nearly a NoOps experience. Devs can focus on what they want to focus on.

⏬
3️⃣ Understanding the author's perspective

Before we're going into a comparison, I want you to understand my perspective. As objective as I try to be, I have my own experience which may differ vastly from yours.

So always keep this in mind when reading on!
I've designed and deployed many production-grade systems on Kubernetes, and I've designed and deployed fewer serverless apps.

The workloads I dealt with were more often suited to a Kubernetes deployment, with traditional micro services, handling infrastructure ...
... components like databases, message brokers, and such on our own.

I used serverless especially when we were building the surrounding systems of mobile or web apps, integrating with existing systems which did the heavy lifting.

⏬
4️⃣ Some Pros and Cons of serverless

There is of course more to serverless than only Vercel, Netlify, AWS Amplify/Lambda/CDK, Azure Functions or whatever the offer is.

You can have serverless databases, serverless message brokers, and much more.
Simply look at the catalogue, pick what you need, and with most offerings: Only pay for what you use!

The developer experience is great, because using those offerings is relatively simple. Sometimes there's a good UI or a CLI which helps a lot.
Devs can focus on the code while the provider handles everything else for you. The simpler your project, the easier the usage gets.

A Next.js / Nuxt.js app without any backend functionality besides SSR can be deployed in 5 minutes and scales and scales and scales.
But there are also downsides.

You can either decide to pick wildly through the whole catalogue and have your database hosted here, while your app is hosted there, and your messaging service is somewhere completely different.
Or you go the vendor lock-in route.

Already on AWS?
Need a database? DynamoDB!
Need a message queue? SQS!
Need backend functionality? Lambda!
Need storage? S3!

And now you have branded code. You won't be able to move from AWS to let's say Azure easily.
As long as you don't plan to or need to move, that's no problem at all. But what if the need ever arises?

Well, that's a whole migration project then which may, depending on the size of your system, take quite some time.
Another problem arises when you have backend-heavy applications.

If you ever considered the management of 50 micro services to be difficult, what about 360 lambda functions? You'll need good documentation to be able to recall all of them and what each and every one does.

⏬
5️⃣ Some Pros and Cons of Kubernetes

Kubernetes itself is a container orchestrator, as we already learned. It works with all sorts of containers. Every application that can be containerized can be run on K8s.
You won't need to set it up manually nowadays. There is EKS, a fully managed K8s service on AWS, AKS (K8s on Azure), or GKE (K8s on Google Cloud). So at least distributing the infrastructure comes close to a serverless offering.
Where Kubernetes shines is especially standardization. As long as you don't use any vendor-specifics, you can take your EKS cluster and simply move it to AKS or GKE. All your yaml specs will still work and you'll have the same system running in the end.
Another advantage is flexibility.

View Kubernetes as a blank sheet of papers. You can write nearly everything on it, or remove it again if you don't want it anymore. And this offers a lot more flexibility.
Need a database? You can use one offered by your cloud provider or deploy your own MySQL (e.g.) instances.

Need messaging? Deploy your own RabbitMQ or Kafka or, again, use something offered by your cloud provider.

Need...? I think you see where this is going.
In the end, you can deploy your favorite (open source) software (as long as its license permits it).

And if traditional micro services aren't for you, you can even deploy your own serverless function infrastructure (https://t.co/ynaXXliREv)!
But of course, all of this comes at a cost. You don't get all of that for free. You'll need to work for it. There is mostly no one-click solution to deploy all of those awesome components you want within your cluster.
You'll need to take care of storing your logs somewhere yourself, you'll need to deploy your databases yourself, you'll ... I once again think you see where this is going.

Simply put: You need people doing this for you and it's complex.
It's nothing an application developer should do next to writing business logic.

So you'll need DevOps / Site Reliability Engineers that handle at least CI/CD and all those infrastructure components for you. And optimally, they'll take care of everything related to the cluster.
Which means:
- Monitoring
- Automating
- Deployments
- Disaster recovery
- Alerting
- Upgrading components
- And a lot more

⏬
6️⃣ And...which one is...better now?

You hate those answers, I know, but it is how it is.
Neither does Kubernetes win, nor does serverless.

They each fill a specific niche in which they are good at.
Serverless offerings are pretty great when you need that development speed and ease of use. If you plan to make that system really big later, and can plan in some time to do a rewrite at some time, start with serverless.
Sometimes you can even stay there forever and the need to migrate never arises. In this case you've saved a lot of time and probably money and made a good decision.

And it's especially a good choice to use serverless when you're developing a mobile or web app.
Kubernetes on the other hand will shine when you have very large systems with many teams involved. It will offer you the flexibility to chose your components to your likings. No need to wait for a provider to offer something as a service that you'd like to have.
Through its flexibility, you'll get many things like A/B testing for very little cost (it's a mere gateway config setting).

It's also great for backend-heavy systems, with a lot of APIs that do not only exist to fulfill the needs of mobile and a web app.
And many serverless offerings you see could be running on Kubernetes under the hood. So you would be right to assume that Kubernetes is, of course, more low-level.

⏬
7️⃣ Final conclusion

This was only a very high-level overview and comparison. Going very in-depth is nearly impossible, as the Kubernetes and serverless ecosystems are both pretty large nowadays.

It would simply be nearly impossible to compare everything highly detailed.
The statement set, however, is still true in my humble opinion.

Both have their right to exist, and both cover their own niche, so choose what suits your use case and your team's skills best when you have to decide!

More from Software

John Fetterman
John Fetterman
@JohnFetterman
buffalo uses dominion scoreboard software so not really


DEAD PEOPLE SCORED FOR BUFFALO!

A truck delivered off a suitcase full of points at halftime from Canada for Buffalo.

#StopTheSteel !!!!

I’ll be submitting sworn affidavits from Steelers fans than they saw the Buffalo rigging the game but I want to emphasize that I’m not under oath.
SOFTWARE
Abhiram Reddy
Abhiram Reddy
@nrabhiram
It’s been a minute since I’ve written code. So, I figured that now might be a good time to start learning how to use the Blueprint system in #UnrealEngine. I felt that it’d be interesting to share my progress and mistakes. So here goes!
🧵

1.
Firstly, I made use of the auto-rigging feature in Mixamo to give my character a skeleton. This allows you to use the Mixamo animations for the character in Unreal Engine.


2.
In the Animation Blueprint, I tried to add a punching state to the character. The problem I faced initially was that the character glides while punching. This occurs because multiple states of the animation are active (as their transition conditions are satisfied).


3.
There are a couple of solutions for this:

👉Blending the punch and idle states (character can punch while running) by using the Layered Blend Per Bone node.

👉Disabling input while the punch occurs.


4.
I didn’t like the outcome when I blended the animations. as the hip rotates more than we’d like it to. This leads to the character punching upwards and to the left. This isn’t favorable as the enemy is usually straight ahead. Disabling the input worked way better!
SOFTWARE
Advertisement
Charity Majors
Charity Majors
@mipsytipsy
Developer productivity, y'all. It is a three TRILLION dollar opportunity, per the stripe report.

Eng managers and directors, we have got to stop asking for "more headcount" and start treating this like the systems problem that it is. https://t.co/XJ0CkFdgiO


If you are getting barely more than 50% productivity out of your very expensive engineers, I can pretty much guarantee you cannot hire your way out of this resourcing issue. 😐

(the stripe report is here:

Say you've got a strategic initiative that 3 engineers to build and support it. Well, they're going to be swimming in the same muddy pipeline as everyone else at ~50%, so you're actually gotta source, hire and train 6, er make that 7 (gonna need another manager too now)...

...which actually understates the problem, because each person you add also adds friction and overhead to the system. Communication, coordination all get harder and processes get more complex and elaborate, etc.

So we could hire 7 people, or we could patch up our sociotechnical system to lose say only 25% productivity to tech debt, instead of 42%? 🤔

By my calculations, that would reclaim 3 engineers worth of capacity given a team of just 17-18 people.
SOFTWARE
C\U000100cfrtex Futura
C𐃏rtex Futura
@cortexfutura
[[Knowledge Management]], [[Reproducible [[Social [[Science]]]]]], and [[Academic Workflow]]s – 100 Tweets for @threadapalooza 2020, let's go
#roamcult #𐃏
1/100

Pandoc is a magical piece of software, and if you're not using it for your academic writing you're missing out. Compile (basically) any document format to (basically) any other document format.
2/100

While Pandoc is fantastic, it's a bit like ffmpeg: extremely powerful, but without GUI apps too few people will use it. ffmpeg has a ton of GUI apps that basically just wrap the CLI, Pandoc doesn't have enough of them.
3/100

Citekeys + CSL files + Pandoc can easily cut ~10+ hours from your writing workflow. Citekeys come from LaTeX-Land, you can use them through Pandoc with anything. And CSL files make it super easy to switch citation styles.
4/100

Since many journals have their own version of popular formats, every journal should be required to publish a CSL file, LaTeX and Word Pandoc template ready for submission. I don't want to think about the collective hours wasted formatting stuff for submission.
5/100
SOFTWARE
Glenn Greenwald
Glenn Greenwald
@ggreenwald
How Silicon Valley, in a Show of Monopolistic Force, Destroyed

In the last three months, tech giants have censored political speech and journalism to manipulate U.S. politics -- banning reporting on the Bidens, removing the President, destroying a new competitor -- while US liberals, with virtual unanimity, have cheered.

The ACLU said the unity of Silicon Valley monopoly power to destroy Parler was deeply troubling. Leaders from Germany, France and Mexico protested. Only US liberals support it, because the dominant strain of US liberalism is not economic socialism but political authoritarianism.

https://t.co/qD9OdwlPbV


Just three months ago, a Dem-led House Committee issued a major report warning of the dangers of the anti-trust power of Apple, Amazon, Google and Facebook. Left-wing scholars have been sounding the alarm for years. Now it's here, and liberals
SOFTWARE

You May Also Like

TXgrlWatching\U0001f4bb\u2694\U0001f6e1
TXgrlWatching💻⚔🛡...
@VeritasTXgem
Thread A History lesson for the MOAB:
1. The United States of America is not and has never been a Democracy, we're a Federal Republic tied together by the capital Laws of the Constitution.

Everyone in the country is about to get a harsh lesson on what this really means...

2. In 1871, February 21: Congress Passes an Act to Provide a Government for the District of Columbia, also known as the Act of 1871.

With no constitutional authority to do so, Congress creates a separate form of
government for the District of Columbia.

3. A ten mile square parcel of land (see,
Acts of the Forty-first Congress,” Section 34, Session III, chapters 61 and

4. The act — passed when the country was weakened and financially depleted in
the aftermath of the Civil War — was a strategic move by foreign interests
(international bankers) who were intent upon gaining a stranglehold on the coffers and neck of America.

5. Congress cut a deal w/ the international bankers(Rothschilds of London) to incur a DEBT to said bankers. Because the bankers were not about to lend money to a floundering nation w/out serious stipulations, they devised a way to get their foot in the door of the United States.
HISTORYLESSON
Nyck de Vries
Nyck de Vries
@nyckdevries
Lately there have been various rumours in the media about myself and Jumbo in relation to Williams. To clarify things, Jumbo is not and will not invest any money in my career. 1/2

Of course we’re collectively looking at career opportunities, however this is certainly not our philosophy and strategy. I hope to announce my future plans soon, be patient 😉 2/2
SPORT
Advertisement
Sam Dylan Finch \U0001f937\U0001f3fb\u200d\u2642\ufe0f
Sam Dylan Finch 🤷🏻‍♂️...
@samdylanfinch
I had the most bizarre experience outside of a bar yesterday, which my partner very aptly described as "toxic mask-unlinity." (A Thread.)

I was standing outside, waiting for a lyft to get home, when two cis men came out of the bar to smoke cigarettes. They're discussing the masks that folks are wearing in California at the moment because of the very dangerous air pollution from the fires happening.

I happen to be wearing one of those masks, because I think lungs are important and I like breathing. I dunno. One of the men notices me standing there, and says, "Like this f*cker right here. What is this shit?"

He goes on a homophobic rant about me, the pansy with a mask, and what a Very Manly Man he is because he's not afraid to smoke a pack of cigarettes while California is on fire. He doesn't need a mask, because something-something-heterosexual-something.

And part of me is just... impressed by the fact that this dude thinks he's Owning The Gay Libs by not wearing a mask to protect his lungs from smoke and particles in the air that are literally DANGEROUS... while chain-smoking. Outside of a bar.
SOCIETY
Lumina\u2728
Lumina✨
@Anaphora_Lumina
I present to you all, my (possibly) superthread On how and why the Unknown God from Genshin Impact, and The Herrscher of Void/God Kiana/Sirin from Honkai Impact!

First off! We’ll start with the obvious things that constitute a possible connection.

They share the same Japanese Voice actress! Rie Kugimiya.
Usually this is a stretch reason, but considering everything else, it’s not unlikely that it’s the same character.

Secondly, their Appearances.
The both have very long white hair with identical bang style, and a very noticeable small piece of hair on top that curls upwards. That’s a defining part Of all of Kiana’s hairstyles, and for it to be shared with this god says something.


Another notable thing is their eyes. They both have Glowing golden eyes with very similar appearances. They contain a ring, and a 4-point star pupil. Resemblant of a scope if you will. That’s The Herrscher of Void’s defining characteristic


If you’d even like to take a look at their outfits, there’s resemblances including the black fur collar, the designs on the torso and chest, and the use of something similar to coat tails/skirt. The Herrscher can change their outfit and they aren’t stuck with one. Sirin does this
CULTURE
Anu Satheesh \U0001f1ee\U0001f1f3
Anu Satheesh 🇮🇳...
@AnuSatheesh5
Panniyur Sri Varahamurthy Temple Palakkad, Kerala
#KeralaTemples 🚩

Panniyur Sri Varahamurthy Temple is located in Pattambi Taluk of Palakkad District. This is believed to be the first temple in Kerala, where Prathishta was done by Parasurama

Story says that, Parashurama after


Creating Kerala was doing Tapasya here. But he was disturbed as the land faced turbulence. Parashurama sought Narada’s help, who advised him to pray to Vishnu. Parashurama started praying Maha Vishnu. Finally Maha Vishnu appeared and told to do Prathishta of his Varaha Avatar.


As Earth is saved in Varaha Avatar, this temple is famous to solve land related issues.

Many people conduct Bhoomi puja here, which is very special here. They bring sand from around the temple which is used for pooja and then has to be returned to the same spot 👇


from where it was taken.
It is also believed that Perumthachan, the legedary craftsman has abandoned his tools here.
Om Shri Varaha Murthaye Namah
🙏🕉🙏
ALL