Upgrade to Pro — share decks privately, control downloads, hide ads and more …

My storing story (Persistiendo que es gerundio)

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.

Karumi

June 21, 2016
Tweet

More Decks by Karumi

Other Decks in Technology

Transcript

  1. Adam Tornhill “Offline is not an error, Offline is a

    fact of mobile life.” Alex Feyerke
  2. 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
  3. Mem Cache “There are only two hard things in Computer

    Science: cache invalidation and naming things.” Phil Karlton
  4. Mem Cache ORMs as ORMLite is a good solution. I

    like ORMLite over GreenDAO and SugarORM.
  5. Mem Cache Realm is not an ORM. Not SQL. Fast.

    Good choice. Be careful sharing info between threads.
  6. Mem Cache It’s not mandatory use a database behind the

    content provider. You can use a MatrixCursor.
  7. 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.
  8. Client Business Logic Data Mapper Data Source Query Object Business

    Entity Persist Query Business Entity Data Source Data Mapper Repository
  9. 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