android - Data Access Service/Layer with an event-driven Firebase database -
i'm writing android app , using firebase real time database it.
i'm struggling event driven concept of database.
in "normal" sql relational world implement data access service/layer alongside mvvm pattern have controlled data flow. layer, example, implements crud methods return pocos/pojos.
but in event driven, nosql environment of firebase database r in crud doesn't make sense, not actively reading in database anymore rather being informed through event has changed.
can replace active reading part in crud event listeners , continue using data access service/layer approach i'm used to, or there significant flaws approach? if so, approaches on handling data flow event driven database?
the firebase database used persistent, event-driven view model in mvvm implementations.
so instead of building own data access layer map database view model, store view model in firebase database , don't write own layer anymore.
Comments
Post a Comment