Exist some ways to persist information on Android, in this talk we show some ways with this pros and cons.

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 CacheBe 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 CacheA Key value xml file.

13. Mem Cachecommit vs apply.

14. Mem CacheAre not thread save.

15. Mem Cache
Shared preferences has cache.
Be careful with StringSets.

16. Databases

17. Mem CacheDon’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 CacheNetwork is other kind of persistence.

23. Mem CacheUse 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 CachePersistence and network invasion.

29. Mem CacheMinimize 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
UsersRealmSt
orage
IQuery
UserApiModel
Persist
Query
User
UsersApi
Data
Mapper
Repository
User
findById(id)

33. 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

34. Find meI am very social!
jorge@karumi.com
@flipper83
+JorgeJBarroso
Questions?