Google Cloud SQL

We use Go for the first-off due to our knowledge of it. Second off, it's highly performant and optimized for scalability. We run it using dockerized containers for our backend REST APIs.

For Frontend, we use React with Next.js at vercel. We use NextJS here mostly due to our need for Server Side Rendering and easier route management.

For Database, we use MySQL as it is first-off free and always has been in use with us. We use Google Cloud SQL from GCP that manages its storage and versions along with HA.

All stacks are free to use and get the best juice out of the system. We also use Redis for caching for enterprise-grade apps where data retrieval latency matters the most.

I want to develop a mobile app with Cloud Firestore as backend. It's good until I realize need to implement FullTextSearch, and Firestore doesn't support it natively. Although they advise to use Algolia but at this time I'm not willing to pay for it.

Therefore, I'm thinking about using the built-in tool from Google Cloud. Since this app is online-only, the offline & sync are not a top priority, so how about use Google Cloud SQL? Or, do you recommend any stack for me? Thanks for your advice.

As far as the backend goes, we first had to decide which database will power most of Daily services. Considering relational databases vs document datbases, we decided that the relational model is a better fit for Daily as we have a lot of connections between the different entities. At the time MySQL was the only service available on Google Cloud SQL so this was out choice. In terms of #backend development Node.js powers most of our services, thanks to its amazing ecosystem there are a lot of modules publicly available to shorten the development time. Go is for the light services which are all about performance and delivering quickly the response, such as our redirector service.