My storing story (Persistiendo que es gerundio)

Store information is a really common problem in Android development. In this talk we try to give some framework solutions for store information in a easy way and we give some architectural clues for work with stored information.

Transcript

1. Persistiendo que es gerundio (My Storing story) Jorge Juan Barroso Carmona jorge@karumi.com @flipper83 +JorgeJBarroso Android expert
2. Basho. Poet Karumi is the beauty of ordinary things spoken of in a simple way.
4. Offline first
5. Adam Tornhill “Offline is not an error, Offline is a fact of mobile life.” Alex Feyerke
6. Adam Tornhill “Once out of bed, internet and apps are used almost constantly, peakin during the daily commute with 70 percent usage.” Ericsson. Traffic and Market Report, june 2012
7. Mem Cache
8. Mem Cache Be careful with OutOfMemories.
9. Mem Cache cache2k DANGER!!!!!
10. Mem Cache “There are only two hard things in Computer Science: cache invalidation and naming things.” Phil Karlton
11. Shared Preferences
12. Mem Cache A Key value xml file.
13. Mem Cache commit vs apply.
14. Mem Cache Are not thread save.
15. Mem Cache Shared preferences has cache. Be careful with StringSets.
16. Databases
17. Mem Cache Don’t Use a sledgehammer to crack a nut.
18. Mem Cache Serialize JSON to disk can be an option if you don’t need queries.
19. Mem Cache ORMs as ORMLite is a good solution. I like ORMLite over GreenDAO and SugarORM.
20. Mem Cache Realm is not an ORM. Not SQL. Fast. Good choice. Be careful sharing info between threads.
21. Network
22. Mem Cache Network is other kind of persistence.
23. Mem Cache Use Retrofit only if your api is REST.
24. Content Providers
25. Mem Cache The way to share information between apps and processes.
26. Mem Cache It’s not mandatory use a database behind the content provider. You can use a MatrixCursor.
27. Repository pattern
28. Mem Cache Persistence and network invasion.
29. Mem Cache Minimize duplicate query logic.
30. Mem Cache “Use a repository to separate the logic that retrieves the data and maps it to the entity model from the business logic that acts on the model. The business logic should be agnostic to the type of data that comprises the data source layer. For example, the data source layer can be a database, a SharePoint list, or a Web service.” Msdn.
31. Client Business Logic Data Mapper Data Source Query Object Business Entity Persist Query Business Entity Data Source Data Mapper Repository
32. Data Mapper UsersRealmStor age IQuery UserApiModel Persist Query User UsersApi Data Mapper Repository User findById(id)
33. Data Mapper UsersRealmStor age IQuery UserApiModel UsersApi Data Mapper Repository findById(id) Cache Policy Populator
34. Bibliography They’re the cracks! Offline first. Alex Feyerke. May 2014. Webdirections Patterns of Enterprise Application Architecture. Martin Fowler Domain driven design. Eric J. Evans The Repository Pattern. Msdn Software design patterns. Pedro Vicente Gomez. Droidcon Spain 2013
35. Find me I am very social! jorge@karumi.com @flipper83 +JorgeJBarroso Questions?