Some input from previously working on a superset of this problem. And being in a similar position.

Mature projects have too much bureacracy, and even spending time talking to you = opportunity cost. So making a case for why you're going to solve a problem for them is tough.

New projects (whether at big companies or small companies) have 20 other things to worry about, so the problem isn't big enough.

I wrote about this in our blog if you're curious: https://ambar.cloud/blog/a-new-path-for-ambar

Thanks. Interesting read, and an interesting product / service. Have been thinking about the same approach myself…

The website seems very vapid. Extraordinary claims require extraordinary evidence. Personally I see a lack of evidence here (that this vendor-locked product is better than existing freeware) and I'm going to move on.

Thanks for the honest assessment!

> HaystackDB is accessed through a RESTful HTTPS API. No client library necessary.

That's cool, but but I would prefer to not reinvent the wheel. If you have a simple library, that would already be useful.

Some simple code or request examples would be convenient as well. I really don't know how easy or difficult your interface design is. It would be cool to see the API docs.

Yeah, it’s a bit of a chicken and egg problem. Since I don’t have a way to find potential customers I feel it’s too risky investing in stuff like client libraries and good API docs. But I can definitely understand you’d like to see more.

what can you do that redis can't?

I'm also skeptical of the graph on your front page that claims S3 cost as much as DynamoDB.

that alone makes it look like total nonsense.

as someone else said, extraordinary claims require extraordinary evidence.

> what can you do that redis can't?

Keep the data in S3 for 0.023 USD per GB-month. If you have a billion keys that can be useful.

> I'm also skeptical of the graph on your front page that claims S3 cost as much as DynamoDB.

Good point. Could have put a bit more work into that.

> Good point. Could have put a bit more work into that.

On second thought, and after looking at my cost estimates, the reason DynamoDB ends up costing about the same as S3 for this kind of use case is storage costs. DynamoDB is a lot cheaper than S3 to write to, but 5-10x more expensive to keep data stored in. So after about 16-32 months you reach break even.