How to implement Firebase version control?

Question

I am currently using Firebase as a prototype tool to demonstrate front end design for a documentation tool . In this process, we really liked the power of Firebase in real time, and we are exploring the potential of using it for our instance to develop an open source version / community.

The first task is version control . Our old project used Hibernate / Envers in the Java stack, and we previously looked at Gitlab as a way to migrate to a more “familiar” git environment.

This way?

Is there a way to track time and version control of stored data? And thoughts on how best to recall this data without redoing the wheel (for example, any open source modules?)?

A real-time aspect of something like Firepad is great for documentation, but we need a means to fix it, or else clearly mark the time state or save the document.

Or?

Or is it better to use Firebase only for real-time functionality and implement Gitlab to transfer the instance to a non-real-time database. In other words, is abstraction of version control completely related to the more traditional attitude towards db?

Thoughts?

Answer 1

Both options that you offer are valid and possible. In general, I suggest you use firebase only as a stack in real time (data synchronization). And connect it to your own server (gitlib or custom-db).

I went this way, and find the best solution - integrate my own backend backend with firebase on top. It depends on firebase solely on everything, and sooner or later you hit walls.
The best solution is to constantly monitor your data structure, security and access systems, as well as use firebase, where necessary, to synchronize clients (online and offline). Integration is simple.