and you know what? Elastic's cloud offering is shit. It's really expensive, it falls over every other week and their support is terrible. AWS ElasticSearch is not great, but it's way better than Elastic.
> No acquisition is also a possibility. Oh my yes, the quiet release of CRI-O by RedHat and Google recently was a pivotal moment. You can run a container orchestration environment in production without anything from…
I'm not sure how you put GitHub in the mix to acquire Docker, they are not a very big company in terms of revenue (currently they talk about a $200m run rate, which is pitiful even compared to RedHat). But I agree…
There's no one silver bullet, as always, you just have to get really good at using Cost Explorer. Project 1: We reduced our EC2 bill by about $10k a month by moving to spot instances for our Continuous Integration…
No what I was saying was its ready for today in certain use cases. But only if you look at it as a long term transition and not a short term project
My googling failed on this account on the correct grammatical term.
Hi There, I created an account here so I could let you know I've clarified some points in my post to address your concerns.
and you know what? Elastic's cloud offering is shit. It's really expensive, it falls over every other week and their support is terrible. AWS ElasticSearch is not great, but it's way better than Elastic.
> No acquisition is also a possibility. Oh my yes, the quiet release of CRI-O by RedHat and Google recently was a pivotal moment. You can run a container orchestration environment in production without anything from…
I'm not sure how you put GitHub in the mix to acquire Docker, they are not a very big company in terms of revenue (currently they talk about a $200m run rate, which is pitiful even compared to RedHat). But I agree…
There's no one silver bullet, as always, you just have to get really good at using Cost Explorer. Project 1: We reduced our EC2 bill by about $10k a month by moving to spot instances for our Continuous Integration…
No what I was saying was its ready for today in certain use cases. But only if you look at it as a long term transition and not a short term project
My googling failed on this account on the correct grammatical term.
Hi There, I created an account here so I could let you know I've clarified some points in my post to address your concerns.