News for hackers. Stuff that matters.
Re:Docker's Second Death by indymike on Sunday December 06, 2020 @02:25PM (#25325927)
It depends on what that infrastructure is. Docker owes its existence to the OS not providing an adequate interface to create lighter containers than 00's style virtual machines. They chose to be imported and used as part of the stack by kubernetes instead of offering a better solution, which was clearly where kubernetes was headed. This one is less of a model question, than a market position question.

Elastic, on the other hand, is a very specialized application and the main issue they've had is having to compete with cloud providers (MongoDB also shares this problem). It's a very different problem, and both companies (Elastic and Mongo) seem to be finding ways to compete and cooperate. Elastic on Amazon is a great gateway drug to Elasticco's offerings.

Re:Docker's Second Death by pydry on Sunday December 06, 2020 @02:33PM (#25325987)
>Elastic on Amazon is a great gateway drug to Elasticco's offerings.

Why is that? Is amazon not able to run it properly?

Re:Docker's Second Death by vr46 on Sunday December 06, 2020 @07:55PM (#25328269)
Can’t speak for the poster who wrote the parent post, but we’ve just evicted the AWS Elasticsearch stack from our platform. For something simple, it was a resource hog, configured badly out of the box, complex in all the wrong places, and limited in its offering and linkages to other AWS resources. Just my 2 cents of course.
Re:Docker's Second Death by indymike on Sunday December 06, 2020 @06:42PM (#25327773)
AWS is several versions behind, and only supports a limited number of plug-ins and does not allow custom plug-ins.