The 5th volume of our newsletter deals with a very serious question: GKE, EKS, or AKS? People get religious about it...
People get religious about it: GKE, EKS, or AKS?
We’ve had our fair share of experience integrating with each one and have a clear winner from a technical perspective: GKE still rules them all. We will do a more thorough meta-analysis soon but a first glance at the numbers reveals a close race.
Positive sentiment towards each of these services are:
Negative sentiment comes in at:
If you look at content and tutorials all providers are creating per month (over 12 months): GKE is leading the pack with 33, EKS with 11, and our friends at Microsoft decided to chill for a while with 0 videos this month, 1 on average.
AWS is still the most influential voice with an estimated social reach of 816.000, followed by GKE with 370k and AKS with 270k.
That was a quick taster of stats. If you’d like to go deeper down the rabbit hole and enjoy a full meal, here’s a great Reddit thread on the clash of religions - bon appetit!
Another amusing topic to reflect upon: Did open sourcing Kubernetes backfire for Google? It certainly introduced an uncomfortably simple way to migrate from A to B. Then again, this might allow Google to win in the long run because of the quality of their tech rather than a first-mover advantage. What we hear from AWS engineering is that they are really busy identifying features to increase lock-in. Serverless is a prime example :) Long live Kubernetes we say.
Interesting how the team at SAP is thinking to use Kubernetes at scale to allow devs to extend their products. This is very much focussed on the SAP ecosystem but does contain valuable lessons for everyone. On DevEx my key takeaway is: they are getting it wrong. Less is more in my opinion, but read for yourself and let me know what you think. Products designed to lower cognitive load should do just that, not introduce additional distractions.
Developer Experience - yes! I'm pretty sure we will hear a lot more about this. We are already seeing the first companies actually hiring devex people to exclusively focus on the productivity and well-being of the app dev teams. Chris Ward gives a great overview on the topic - check it out.
In case you missed it, here’s the recording from last week’s webinar. Our VP Engineering talks through our experience building an Internal Developer Platform, how elite teams leverage such platforms to outperform the rest of the pack, and how it can benefit your dev teams too.
It’s a technical one this time: how do you test hotfixes to your Production without rolling back staging? We have been asking ourselves how leveraging ephemeral environments can help in this scenario. We decided to present our findings and discuss them with you.
Look forward to the conversation!
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.