Fake it till u make it (isolates!)

[Raghuvorkady]

Create an isolate for firebase and hive process (network and database)
Let it return the model ASAP on adding and then do the background process

---

But Hive operations can be performed in isolates, if we pass path to the isolate

---

• compute(), R/W from/to hive, and bg for firebase
• do CRUD first in Hive and then upload in firebase in the background using Isolates.
• Create a sync field in the transaction model to know whether the record is uploaded to firebase.
• Also create metadata for all tables created in Hive, to know the status.
• Worker isolate

---

metadata examples:

• tables,
• columns,
• Table size
• Datatype size
• Variable size
• Program size
• Number of rows and columns
• sync status
• last modified time

[Raghuvorkady]

do not create a nested isolate! (not sure)
call compute(), which will call different methods

[Raghuvorkady]

update:

1. Unfortunately it is not possible to use Firebase services in isolate, because even if we use simple firebase method for networks R/W requests, we need to use Firebase.initializeApp(), which in turn requires to use platform tools to use native codes. To provide access to this, we need to use WidgetsFlutterBinding.ensureInitialized().
   Acc to doc, secondary isolate cannot get access any methods related to UI in other words only main thread can use this method.