HackerTrans
TopNewTrendsCommentsPastAskShowJobs

vincentge

no profile record

Submissions

[untitled]

1 points·by vincentge·4 tahun yang lalu·0 comments

comments

vincentge
·4 tahun yang lalu·discuss
Timelines we can share? I don't know... but soon ;)
vincentge
·4 tahun yang lalu·discuss
The API is pretty simple! Not close to Firebase but simple to pick up.

Here's some Kotlin: https://appwrite.io/docs/getting-started-for-android#fullExa... https://appwrite.io/docs/databases#create-documents
vincentge
·4 tahun yang lalu·discuss
This actually looks suuuupppppeeeerrrr cool!!!
vincentge
·4 tahun yang lalu·discuss
I do. If I were to attend a hackathon (which I haven't since 2020), I would use Firebase. It's simple and they sponsor every hackathon I've been to, so I get free credits.

That said, if I attend today and ignore sponsorships, I'd actually get DigitalOcean market place deployment of Appwrite. I honestly think it's quicker to get started with, and I like owning my data ;)
vincentge
·4 tahun yang lalu·discuss
No, we're trying to provide similar functionality, but we're not just cloning it down to the API. We have some of our own philosophy, for better or for worse, about what a good BaaS should look like.

Think of it as an alternative, not a clone :)
vincentge
·4 tahun yang lalu·discuss
We're looking into it. We optimistically want to do it. We haven't committed to doing it, because we're prioritizing some other stuff right now :P
vincentge
·4 tahun yang lalu·discuss
I answered above, so look there for a detail response.

If you like your experience to be decided for you, use Supabase, especially if you love interacting with a Postgres instance and Deno for your cloud functions.

We try to keep our stack agnostic, hence the 11 function executor, and ever growing list of SDKs. We also allow you to choose your storage adaptor for stuff like Linode, S3, DigitalOcean spaces, Wasabi, and more. We'll eventually give you the option to choose between many DB options, too.

We don't wanna replace your stack, we wanna play nicely with it. You can straight up disable all our services but one, and we're happy to let you enjoy your experience all the same :)
vincentge
·4 tahun yang lalu·discuss
Both are great products, here's my biased (obviously) way of choosing between them:

- Appwrite is really focused on a simplistic experience. If you check out our SDK documentation, we try to keep everything dead simple.

- Supabase allows more verbose control over their PostgreSQL instance, i.e. you're actually writing SQL and interacting through a SQL console. This might be your cup of tea. They also use Deno for their cloud function equivalent, which is cool if you love Deno.

I would say Supabase is more opinionated, we try to give more options. Neither is necessarily better, there are pros and cons that you can decide on.

Other than that, Appwrite does some things that I find special.

Appwrite is simple to self-host. Like really simple. Like a single line of Docker command simple:

docker run -it --rm \ --volume /var/run/docker.sock:/var/run/docker.sock \ --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \ --entrypoint="install" \ appwrite/appwrite:latest

This gives you the full Appwrite experience for local/dev environments and you only need a few more environment variables to be production-ready.

We try to make Appwrite agnostic to your tech stack. You can use or disable any of the services when self-hosting, saving resources on your precious servers. You can integrate with frontend, backend, or both, or just use a single service, like our function runtimes.

We support a ton of SDKs, and we're always adding more. Our vibrant community makes this possible.

We have a lot of languages supported for Appwrite Functions, not just Deno ;) We have lots of storage adaptors you can choose from, or local storage if you want to keep all your data. We will support MANY databases (you can contribute your own, too).

I hope that helps, it really is down to personal preference, developing on the platforms feels very different. Try both!
vincentge
·4 tahun yang lalu·discuss
We don't have instructors for this, per-se. There is an older article about using docker swarm -> https://dev.to/appwrite/30daysofappwrite-docker-swarm-integr...

We're trying to update these old posts as we speak... hopefully we'll get to this soon :') Keep an eye out!
vincentge
·4 tahun yang lalu·discuss
Appwrite is really meant to live happily beside your stack. Honestly, disable and rip out the containers you don't need, they're all stateless, and loosely coupled. You can disabled them in console.

Use what you find useful. I often use Appwrite just for Auth + Avatar/profile management. Something I do for every app... something that I find painful to do for every app :P
vincentge
·4 tahun yang lalu·discuss
Firebase is great for Hackathons =D
vincentge
·4 tahun yang lalu·discuss
My honest two cents, which is biased, so take liberal amounts of salt.

I think Supabase is verbose. You get to dig around the PostgreSQL instance, write SQL, etc. I know people that live and die by SQL, so if that sounds like you, Supabase is great.

Appwrite is more about simplicity. Our SDKs are simple, our UI is simple, our Documentation is simple, heck we even have a 1 line deploy: docker run -it --rm \ --volume /var/run/docker.sock:/var/run/docker.sock \ --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \ --entrypoint="install" \ appwrite/appwrite:latest

Use a part of Appwrite, or all of it. Heck, go dig in our code or checkout our open sourced Functions runtime. We don't care, we just want you to do more while writing less code.

Both have their audience, both are great, see which one suits your needs better :)
vincentge
·4 tahun yang lalu·discuss
There's two ways to address this if you don't wanna maintain/host.

There will be a hosted Appwrite Cloud option => https://appwrite.io/cloud

There is a way to do 1 click deployment on Digital Ocean Marketplace: https://marketplace.digitalocean.com/apps/appwrite

With these options, you can put off the whole mess with devops, infra, and hosting to someone else :')
vincentge
·4 tahun yang lalu·discuss
Thank you!