Tigris is the first truly open source developer data platform with a simple yet powerful, unified API that spans search, event streaming, and transactional document store. It enables you to focus on building your applications and stop worrying about the data infrastructure.
Build out the overview with some case studies. If I am a first time cloud builder at the 'what should I use...' stage - which seems to be a target market for you - then <i>I don't know what I don't know</i>.<p>Right now your marketing speaks to people who have already implemented something across multiple different platforms - but having learned all that they're probably more willing to accept the marginal cost of maintenance than to abandon the time and effort already invested in setting it all up.<p>Building from scratch is a much easier and more pleasant decision than migrating. So you'll gain more users from people who want an accessible infrastructure experience that can grow with their (presently unknown) needs than with grizzled veterans - who might prefer just demanding a larger budget or more hires for infrastructure on a future project than learning a new technology that will render their previous knowledge obsolete.<p>Your short intro video kind of addresses this, but shows your example developer deploying her app and then 5 different infrastructure platforms with zero effort - she doesn't care about the problem until it comes to the boring maintenance stage. A lot of people would take away that the market leading technologies are super-easy to deploy and that they can just hire someone to do the maintenance while they focus on product or the business side. (Also, the music doesn't match the visual story at all and feels cringey - again, not the emotional impression you want to create.)<p>In general, people will go with whatever the default tool is because it's socially proven and there will be a big community of prior users who can help them through the teething problems. And there's a sense that the right tool for the right job is usually better than a do-everything tool. So you need to show where the pain points are early in the process of cloud deployment - when your target user is figuring out what infrastructure they need, and why.
So where does the data actually live? I read through the page and I'm still not clear.<p>Is Tigris itself a database? Specifically it seems, a multi-paradigm database? And if it is, what is it that makes it a platform and not simply a database?<p>Not criticizing, these are just questions I have initially trying to grok it at a quick glance.
Is it just a server process sitting in front of the db?<p>All this “docker this” and “docker that” I can’t tell what things do anymore. I assume the docker image does a whole lot of magic to get things to work that one would have to reproduce to run this on a bare VM they have sitting around.<p>I’m not trying to be negative here, this looks like something I’ve had rattling around in my head for a while but haven’t had the time to figure out how to make. Well, my imaginary version is based on graphQL (and not written in JavaScript like every other graphQL thing) simply because I want to try out graphQL and no other reason.<p>Oh, and a python client library would be nice but I can knock something out on my own to play around with this when I get some free time.
Great job shipping!<p>When it comes to open-source infrastructure projects like this, the first thing I generally look for is an architecture diagram on how to operate something like this.<p>Having a great developer-friendly API is important, but operating the system(s) is just as important and often a differentiation point of using the system (e.g. scale up some nodes, and you're good vs a mish-mash of an OLTP database, distributed WAL, a denormalized search cluster, etc).<p>I don't get a good sense of how this works right now with the docs.
it's a REST+json payload frontend for foundationDB.<p>...by people who doesn't feel that the underlying tech is important to mention. So, not for this crowd.
after reading the front page i honestly have no clue what this is, but i'm reasonably certain that part of it is a document db. the quickstart seem to imply that i throw JSON at it via APIs and that that ends up in the implied db. The quickstart is also all about "hey DB stuff"<p>so, now i think it's... a MongoDB competitor? maybe?
This looks like a great project but it's not a valid Show HN if people can't try it out. Please see <a href="https://news.ycombinator.com/showhn.html" rel="nofollow">https://news.ycombinator.com/showhn.html</a>. Note the bit about signup pages.<p>(I've taken Show HN out of the title now.)