4 ms·

Great feedback. We do want to speak to folks building new applications as Tigris takes away the infrastructure burden completely from the start. We want to bri

Great feedback. We do want to speak to folks building new applications as Tigris takes away the infrastructure burden completely from the start. We want to bring the same API experience to "data" as you get when using Stripe API for financial transactions. Migration is often times necessary. In my experience I have seen countless examples of migrations once an application becomes popular and the backend technology choices at that point either become brittle (hard to keep adding new app features), or do not scale. So I wouldn't categorize it as marginal maintenance cost. The video, I agree could be improved. Because the pain is not just seen at the maintenance stage, it is felt at every step that you add a new technology to you stack. Regarding your other comment about "people will go with whatever the default tool". It is actually the opposite, if you give people the choice they will stick to far fewer technologies :) This is why when you see someone building a top Postgres, as an example, initially they use it for the OLTP workloads, then they use it for the full-text search use cases (knowing fully well there is a better alternative because PG is not a search engine), or use it for analytics (even though there are other special-purpose analytical products), or use it for modeling event stream (even though again there is a special-purpose product available for event streaming). This is how application architectures organically grow, and the reason this happens is exactly because it is much easier (development time-wise and maintenance-wise) for me to continue to use X until it is unsustainable. And this is where we are coming from. We want to be that general purpose solution that you can continue to use to build up your application and it will grow/evolve with you. We did prepare this use-case video, I am curious to hear your thoughts: https://youtu.be/G489hasvgio https://youtu.be/G489hasvgio

anigbrowl 4y ago
This video was essentially the same argument, but in a much more accessible way (sorry Jane). Regarding your features overview, it's very good, but I think you can get a lot of lifelong signups by adding a longer tutorial aimed at first times (not throwing away your existing material, which is mostly great). That is, put yourself in the position of the developer who has something working and wats to share it with the world, but hasn't gone past the MVP/dem stage yet. If Tigris can be the tool that teaches people what infrastructure does (maybe via a book or similar) you get that sort of generational loyalty. Best of luck - I'm definitely motivated to use it.
- ovaistariq 4y ago
  Again, I really appreciate the feedback. So regarding the video, if I understand correctly your suggestion is that use-case driven videos would be better? You make a great point regarding the tutorial. Where would you want to see it? In tutorials, or would that be the first page you would want to land on as a developer?
  - anigbrowl 4y ago
    I would want to land on it. But I might not be the best yardstick for that because I mostly develop solo and don't have a lot of technical peers/colleagues that might say 'oh, use MongoDB for [task] because [reasons].' So I look at pretty much everything in terms of either 'does it solve/help with problem X I already know' or 'what is this for and why does it matter'. Sometimes it's interesting and maybe I'll use it someday, other times it's not necessarily interesting but I pay attention because I'll definitely need something like that sooner or later.
    - ovaistariq 4y ago
      I think that's how most people interested in solving problems would look at it the way you have described - 'does it solve/help with problem X I already know' or 'what is this for and why does it matter'. And we do want to be able to answer that. We will definitely be adding tutorials showing how Tigris eliminates complexity and provides a simple API experience.

anigbrowl 4y ago

This video was essentially the same argument, but in a much more accessible way (sorry Jane). Regarding your features overview, it's very good, but I think you can get a lot of lifelong signups by adding a longer tutorial aimed at first times (not throwing away your existing material, which is mostly great). That is, put yourself in the position of the developer who has something working and wats to share it with the world, but hasn't gone past the MVP/dem stage yet. If Tigris can be the tool that teaches people what infrastructure does (maybe via a book or similar) you get that sort of generational loyalty. Best of luck - I'm definitely motivated to use it.

ovaistariq 4y ago
Again, I really appreciate the feedback. So regarding the video, if I understand correctly your suggestion is that use-case driven videos would be better? You make a great point regarding the tutorial. Where would you want to see it? In tutorials, or would that be the first page you would want to land on as a developer?
- anigbrowl 4y ago
  I would want to land on it. But I might not be the best yardstick for that because I mostly develop solo and don't have a lot of technical peers/colleagues that might say 'oh, use MongoDB for [task] because [reasons].' So I look at pretty much everything in terms of either 'does it solve/help with problem X I already know' or 'what is this for and why does it matter'. Sometimes it's interesting and maybe I'll use it someday, other times it's not necessarily interesting but I pay attention because I'll definitely need something like that sooner or later.
  - ovaistariq 4y ago
    I think that's how most people interested in solving problems would look at it the way you have described - 'does it solve/help with problem X I already know' or 'what is this for and why does it matter'. And we do want to be able to answer that. We will definitely be adding tutorials showing how Tigris eliminates complexity and provides a simple API experience.