Re:OpenSearch: AWS fork of Elasticsearch and Kibana
by ukd1 on Monday April 12, 2021 @01:00PM
(#26781895)
I buy the main reason being the all-in-one solution; the comprehensiveness is attractive. However, I think you're underplaying the lock-in: migrating clouds is non-trivial - mostly due to stuff that's not running in k8s/docker/etc; stateful apps (Postgres, etc), and or just static data like s3. This takes time, and careful planning and sometimes downtime - and is mostly avoided due to it being hard.
[ Parent
| on HN ]
Re:OpenSearch: AWS fork of Elasticsearch and Kibana
by fastball on Monday April 12, 2021 @02:57PM
(#26783564)
I specifically talked about state and storage.
You're conflating the difficulty of migrating a complex system to anywhere with "vendor lock-in". It would be harder to migrate an Aurora RDS Postgresql instance to an Aurora RDS MySQL instance than it would be to migrate from Aurora RDS (postgres) to a hosted postgres anywhere else.
That to me screams "not vendor lock-in".