Android offline

In this talk we look at options/ways that we can benefit from Android Database and persistence.

make sure to checkout the Video of the presentation:
http://bit.ly/2RYjeGK

Transcript

1. In the name of God
2. Who Am I? Seyed Mohammad Hossein Jafari Android Team Lead @ Noavaran
3. Android Offline
4. How? Persistence By persisting data we mean to store our data in a place that we can access it later even if system goes through restart/shutdown. Usually done by writing files on disks.
5. File With? Shared Preferences DataBase
6. File Pros and Cons Shared Preferences DataBase • No Structure • Bulk Read/Write • Easy (no need to learn) API • Binary data • Synchronized • Key-Value based • Small data • Framework Managed • Small API • Observing Changes (Surprised?) • Synchronized • OEM Bugs! • Structural • Transactional • Large Data sets • Relational • New API • Observing Changes • UnSynchronized • Lot’s of third party Libs
7. File/DB
8. Structured Query Language SQL / RDBMS / Relation Types of DataBases Non-SQL or non-relational No-SQL
9. SQL Wikipedia: “ SQL is a domain-specific language used in programming and designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS).”
10. NoSQL Wikipedia: “ NoSQL database provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. ”
11. Android DataBase SQLite
12. Why to use Database on Android • Content received from remote data source (Caching) • User entered data and application generated data • Storing app states and User Management • Storing Requests and Works (WorkManager)
13. SQLite
14. Object Relational Mapping (ORM)
15. Beyond the basics SQL NoSQL
16. Room GreenDAO SQLDelight Realm Objectbox
17. GreenDAO Room SQLDelight ORM
18. Realm Objectbox NoSQL
19. Too many options? Which one to choose?
20. ORMs • Native • Fully backward compatible • Small Size • Minimum method Count • Easy to migrate Pros • SQLite base • Very Slow • Not Fully Crossplatform • Not many features • Lots of people suggest not to use it any more Cons
21. NoSQL DBs • Fast • Scalable • Constant Update • Fully featured • No more SQL • Cross platform • Easy to use Pros • Extra C binaries • Huge method count • Not Fully backward compatible(9/15) Cons
22. What does Stats say?
23. Room GreenDao SQLDelight Realm ObjectBox Size 50-100KB 3-4MB 1-2MB Methods 300 2000 1500
29. Testing
30. Room • No Real Unit Testing Only Instrumentation test • In Memory DB Realm • No Real Unit Testing Only Instrumentation test • Mock master! • In Memory DB Objectbox • Write tests on JVM • No need to mock • Use real configuration not stub version
31. Satisfied?
32. Where to begin with ObjectBox? https://docs.objectbox.io/getting-started
33. Entities(Tables) @Entity data class StudentEntity( @Id var id: Long = 0, val name: String )
34. DataBase Instance val store = MyObjectBox .builder() .androidContext(applicationContext) .build(); val box: Box<StudentEntity> = store .boxFor(StudentEntity::class.java)
35. Create store.put(student)
36. Read store.get(studentID) store.getAll() store.find(StudentEntity_.name, "name")
37. Update store.put(student)
38. Delete store.remove(studentID)
39. Thank you
40. Forget SQL Try Objectbox Today https://objectbox.io https://github.com/objectbox Twitter : @worldsnas https://worldsanas.com
41. The End