If you're serious about scaling up, definitely consider Vespa (https://vespa.ai). At serious scale, Vespa will likely knock all the other options out of the park. - Source: Hacker News / about 2 months ago

Yahoo released their geographic data catalogue under open license and it still lives on as https://whosonfirst.org/ Afaik https://en.wikipedia.org/wiki/Apache_ZooKeeper started at Yahoo https://vespa.ai/ was Yahoo's search engine for news and other content product, now spinned off (https://techcrunch.com/2023/10/04/yahoo-spins-out-vespa-its-search-tech-into-an-independent-company/). - Source: Hacker News / 4 months ago

I think https://vespa.ai/ has the right approach in this space by focusing on being hybrid - vectors alone aren't great for production use cases, it's the combining of vectors+text that lets you use ranking to get meaningful result. (I'm an investor so I'm biased; but it's also the reason why I invested). - Source: Hacker News / 4 months ago

So what’s the catch? Why is this not everywhere? Because IR is not quite NLP — it hasn’t gone fully mainstream, and a lot of the IR frameworks are, quite frankly, a bit of a pain to work with in-production. Some solid efforts to bridge the gap like Vespa [1] are gathering steam, but it’s not quite there. [1] https://vespa.ai. - Source: Hacker News / 5 months ago

When it comes to search I cannot disagree more. https://vespa.ai is a purpose built search engine. If you start bolting search onto your database, your relevance will be terrible, you'll be rewriting a lot of table stakes tools/features from scratch, and your technical debt will skyrocket. - Source: Hacker News / 11 months 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 / about 2 months 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 / 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: 10 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