adv-firestore-functions VS extensions

I retired my package, adv-firestore-functions, because I could not keep up with it anymore. However, most of the code is still good. I made it easy to use Counters with a colCounter function. There are several problems with this method:

The number one problem with Firestore is hands down the lack of counters. I literally wrote a package to do everything in Firebase Functions, and I learned after 6 months, I hate Firebase Functions. All the code missing from Firestore that takes up your time is relational and counter related. Now I know on the Frontend it is just as bad. However, I wrote some reusable Functions which I have talked about in other posts to make your life a little easier. However, some things are just impossible in Firestore. I seriously hate noSQL in general, but not having counters is terrible. I also wrote some reusable Firestore Rules for counters. Everything is usually dealing with counters.

Based on my relevant search index, I created a simple frontend version you can use in your app.

If each followers_index holds 10,000 users, then we only grab 100 documents for 1 million followers. If you're lucky enough to have 100 million followers, then yes, you would need to create 10,000 documents. That is actually doable in a Firestore function with my Bulk Update Function in theory. The most amount of followers ever recorded on any platform is under 200 million.

Method 1: - use my adv-firestore-functions package... one line of code in your firebase function... done.

The beauty of this, is it automatically scales. It creates a new index document after 10,000 items (you can set this with max, see the docs). It will automatically remove a product from the index if the product doc is delete from the collection. It automatically adds. I have id sorting and value sorting options that I spoke about in Part 3.

Basically you create your own index using __ between every combination of items in the array. This would give you search options. You could do this on the front end, or on the backend in Firebase Functions. Here I am only covering the frontend, although I may one day add this ability to my adv-firestore-functions package.

As the author of adv-firestore-functions, I feel like I have figured out how to hack every problem the Firestore Team refuses to solve internally, except how to connect the relational data of a follower feed.

In this tutorial, learn how to install and utilize a combination of Pangea provided Firebase Extensions. Firebase Extensions are an easy way to add Pangea services to your Firebase app without the need to write or debug code on your own. Extensions are pre-packaged solutions designed to save development time and quickly deploy Pangea functionality into your applications hosted on Firebase. You provide the configuration parameters, such as authentication tokens, for each extension at install time. All Pangea-provided extensions are open-sourced and built on Firebase and Google Cloud products you already know. Deployment and configuration of each extension are performed in the Firebase console or the Firebase CLI, and once deployed, they require no maintenance.

If you want to try the Extension, check out this tutorial. Accepting user uploads is the use case we developed the Extension. Depending on your use case, and if you want to share your app's processing capabilities with other Firebase developers, you might want to consider building it into a Firebasse Extensions

Firebase Extensions: Pre-packaged development solutions 🔗Link

According to this discussion the Node version is set by the Firebase team, which is quite sad. Please let me know if I'm wrong, but it seems like it's not under our control.

Also see the delete user extension for an example: https://github.com/firebase/extensions/tree/master/delete-user-data

So this provides an obvious question, how do I import previously existing data? We have an import script for that!

Hi all, I need to add some data into BQ, the data was in my Firebase before I installed the "Stream Collections to BigQuery" extension. So now I need to load it manually. I'm trying to use fs-bq-import-collection, but my issue is that the collection I want to import is a subcollection e.g. /collection/{document}/sub_collection. I've read the documentation https://github.com/firebase/extensions/blob/master/firestore-bigquery-export/guides/IMPORT_EXISTING_DOCUMENTS.md and there they say that I need to use a collectionGroup query. But I really have no idea how to do that, I've spent several hours checking the net but I cannot find any place that explains it in a easy to understand way.

Method 3: - Distributed Counters - Whenever you deal with any real scaling, you need something like the sharding to accurately keep track of document counts. If you have more than 1 page view a sec, or more than one person clicks like a post a second, the server will slow down, and potentially be inaccurate. You can fix this with sharding. Here is the Firebase Extension and the Source Code. The code is really well written, but it should never have had to be written! Indexes, indexes, indexes!