20 ms·
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 yo
by anigbrowl 4y ago
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 don't know what I don't know.
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.
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.
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.)
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.
- VyseofArcadia 4y ago> 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 don't know what I don't know. >Right now your marketing speaks to people who have already implemented something across multiple different platforms This seems to be a pretty big gap in marketing across the industry. Everything is either utterly meaningless market-speak[0] or targeted at experts. [0] The sheer number of products marketing themselves as one-size-fits-all "solutions" without ever bothering to define the problem...
- ovaistariq 4y agoWe have prepared this use-case video to depict how Tigris can be used: https://youtu.be/G489hasvgio https://youtu.be/G489hasvgio
- Volundr 4y ago> I don't know what I don't know. This probably describes me. Reading over the linked documentation it's not clear to me how this is different from couchdb or any number of other document databases that work over http.
- ovaistariq 4y agoDoes this explain it in a better way: https://docs.tigrisdata.com/overview/features https://docs.tigrisdata.com/overview/features
- ovaistariq 4y agoGreat 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 agoThis 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.