shyneeup

the hype around k8s is unreal..... But should everyone even learn k8s? A lot of the core features of k8s and container orchestration is getting abstracted away at a rapid pace with more things being built on top of k8s. I see this at my current company where we have a ton of ops people who have only ever used vmware....with cloud migration and container focused workflows being the standard now they are fearing like they are left behind. So I see a lot of them learning to code, trying to learn k8s, trying to become more devops with automation. Its quite a steep learning curve.

But by the time they catch up to this technology I have a feeling it will become less important to administer k8s directly.

this was a great read thanks!

What is the role of an architect nowadays?

are you advocating for the same solution here with search engines...? Because that would just give the same result.

well just behind is very generous considering Azure's market share is around 12% and AWS is like 50%

https://www.forbes.com/sites/jeanbaptiste/2019/08/02/amazon-...

Now I am curious, who runs production customer facing apps on Azure? I'm assuming many people do given that Azure is second after AWS in market share or is that really just mostly corporate IT servers?

I think one of the reasons why it's such a conundrum is because software development as a practice is just now getting to the level of complexity where large groups of people have collaborated over a large codebase over a long time.

One of the problems that the microservice architecture is trying to solve is by making a a large software entity a collection of smaller easier to manage entities. It's like single cell organisms evolving to multicell organisms...each cell becomes smaller and simpler and more specialized and replacement of cells becomes easier and allows the overall lifeform to "scale" and become more complex.

Mature software companies have gone through this transformation multiple times already in the form of, n-tier, SOA, microservices, and now serverless architectures. This is all part of a natural progression of making individual components simpler, the overall structure more granular, and as a result more resilient. This resiliency opens up new capabilities to scale a complex system.

My long winded point being that legacy software will always exist yes, but each piece of legacy software is already getting smaller and more granular where rewriting it will eventually be a more continuous operation of refactoring small things--kind of like skin cells falling off your body or hair falling out.

I'm still trying to understand....whats the point of using blockchain here at all if you're going to just make it centralized by validating only through an admitted pool of validators?

Don't know enough about crypto, but whats the benefit of a payment system for messenger apps to run on crypto at all? If you're transacting through a centralized messaging platform doesnt that defeat the purpose of a decentralized currency or ledger?

I'm curious do you only hire people with US citizenship?