,
9 tweets,
2 min read
Read on Twitter
X : Only those who don't get it think Kubernetes won the "container wars".
Me : Does K8s focus and operate below the level of code? If the answer is "yes", then I don't care. I view every need to dive below the level of code as a bug not a feature. It needs to move up the stack.
Me : Does K8s focus and operate below the level of code? If the answer is "yes", then I don't care. I view every need to dive below the level of code as a bug not a feature. It needs to move up the stack.
The areas that interest me are Google Cloud Functions & Firebase etc or AWS Lambda and its range of events and services or Azure Functions and MSFT's suite of services. Every time I need to think about packaging formats and orchestration, I think "this system is broken".
It's like in the past where I used to build large databases ... I had to have think about the disk set-up, i/o reads and writes, the number of disk heads, optimisation of the query plan, the amount of memory caching, the structure of the index ... just to run a query at scale.
i.e. trying to ensure the data was structured so the query maximised use of sequential reads or calculating whether round robin or random or queuing requests based on worker load was the more effective? Self healing systems to scaling worker volume, this is so 2005 for me ...
... but this is not 2005, it's 2019. Anything which goes below the level of code is a bug to me, a failure of the underlying system and I care as much today about this as I care about L2/L3 cache.
X : Surely, one size doesn't fit all?
Me : There will always be niches. But this is about the dominant model. Our ability to move up the stack, to progress depends upon industrialisation of lower order ...
Me : There will always be niches. But this is about the dominant model. Our ability to move up the stack, to progress depends upon industrialisation of lower order ...
... do you think our world would be as advanced in places if we were all messing around with nut and bolt threading sizes, or standards for electricity provision or protocols for network transfer or custom building our own operating system or fiddling with RAID configuration.
X : Why are you always pro Amazon and anti Google?
Me : I'm not. I'm very pro Google which is why I keep beating it up about moving up the stack. Ditto Cloud Foundry in the past. If I didn't care, I would ignore. Friends tell you what you need to hear not what you want to hear.
Me : I'm not. I'm very pro Google which is why I keep beating it up about moving up the stack. Ditto Cloud Foundry in the past. If I didn't care, I would ignore. Friends tell you what you need to hear not what you want to hear.
... the same was true with OpenStack. I tried to warn them so many times about APIs, danger of creating a collective prisoner dilemma, need to create a competitive market.
X : You also called them a dead duck.
Me : By then they were. Others needed to find a different path.
X : You also called them a dead duck.
Me : By then they were. Others needed to find a different path.
