adv-firestore-functions VS j-firebase

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.

As you can see from the source code, you can input as many paths as you like. Now you will have your user document count on the user's document as postsCount. I have more options and customization, but that is it in a nutshell. I plan on writing all this up as well as more options on this site soon. If you have questions, feel free to create an issue until I can get the docs up.