Coralogix VS AWS Database Migration Service

In defense of Grafana Loki, it's awesome... If you have a lot of information about your telemetry data up front - i.e volumes, use cases, how you wish to query it etc. A broader solution like Coralogix (https://coralogix.com/) is more appropriate if you're venturing into the unknown and you need more of a data discovery capability. The problem with most of THESE "all in one" platforms is they tried flexibility and... - Source: Hacker News / about 1 year ago

We, coralogix.com, are looking for a Rust engineer with some experience of database engineering. Source: about 2 years ago

The second big drawback is speed. There will be more latency in this scenario. How much latency depends upon the environment. If there is RDBMS in the source, AWS Data Migration Service will at worst take around 60 seconds to replicate. That cost needs to be accounted for. Secondarily, many triggering events are leveraged which happen fairly quickly but they do add up. - Source: dev.to / 28 days ago

Amazon Database Migration Service might initially seem like a perfect tool for a smooth and straightforward migration to RDS. However, our overall experience using it turned out to be closer to an open beta product rather than a production-ready tool for dealing with a critical asset of any company, which is its data. Nevertheless, with the extra adjustments, we made it work for almost all our needs. - Source: dev.to / about 2 months ago

Does AWS DMS make sense here? Doesn't the aforementioned "snapshot+restore to provisioned and upgrade" method suffice? I wanted to get some opinions before deep diving into the docs for yet another AWS service. Source: 9 months ago

One easy solution is AWS DMS. I use it for on-going CDC replication with custom transforms, but you can use it for simple replication too. Source: about 1 year ago

Https://aws.amazon.com/dms/ Azure Database Migration Service. - Source: Hacker News / about 1 year ago