AppWrite Reviews

1. dndiel

   over 2 years ago
   Appwrite is awesome, free and open-source!

   I've use it instead of Firebase on a 15$ DigitalOcean droplet and saved around ~$150 a month. Managing my own infra does take some extra time, but definitely worth it. The APIs and SDK are also surprisingly much easier to consume than Firebase. Waiting for the cloud version.

   🏁 Competitors: Firebase

   👍 Pros:    Easy to use|Cost effective|Open-source|Great user experience|Super simple|Self hosted

   👎 Cons:    Self hosted

goa Reviews

AppWrite mentions (169)

• Basics of web3 development, JS new releases this week, cool npm modules and open-source packages

  Serverless apps or apps without a backend or app that controls your backend, all are the same and for frontend and backend devs Firebase and Supabase are quite useful and trending along with other serverless databases such as Appwrite and  PocketBase. - Source: dev.to / 9 days ago

• Building An E-Commerce Store With NextJS

  Appwrite - for authenticating users, as well as saving and retrieving product details. - Source: dev.to / 27 days ago

• How I use Appwrite Databases with Pinia to build my own habit tracker

  If you haven't tried Appwrite, make sure you give it a spin. It's a open source backend that packs authentication, databases, storage, serverless functions, and all kinds of utilities in a neat API. Appwrite can be self-hosted, or you can use Appwrite Cloud starting with a generous free plan. - Source: dev.to / 3 months ago

• Exploring Appwrite: A Comprehensive Guide

  What is Appwrite? Appwrite is an open-source backend server that abstracts the complexity of backend development, allowing developers to focus on building their applications. It provides a wide range of services including databases, storage, functions, and authentication, all designed to work seamlessly together. This integration simplifies the development process, reducing the need for extensive configuration... - Source: dev.to / 3 months ago

• 11 Planetscale alternatives with free tiers

  Appwrite is an open source BaaS platform that provides services like serverless functions, serverless databases, user authentication, and messaging. Since its release, it has quickly become a popular choice for building websites and applications. - Source: dev.to / 3 months ago

goa mentions (27)

• IBM to Acquire HashiCorp, Inc

  My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 2 months ago

• Microservices communication

  See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 7 months ago

• Which is the best framework to create web apps with go?

  If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 1 year ago

• OpenAPI v4 Proposal

  Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 1 year ago

• Beginner-friendly API made with Go following hexagonal architecture.

  One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: about 1 year ago