Skip navigation
Entities: iOS App Development: Design Patterns for Mobile Architecture
Entities: iOS App Development: Design Patterns for Mobile Architecture

Database and Network technologies change constantly. Several years ago XML/SOAP was the thing. Now it's JSON. Google has other more efficient data structures to work with. This year you might be using Core Data, next year it could be Realm or plain SQL/SQLite. Many developers arent interested or don't understand the nuances of these different technologies, especially when it comes to threading and asynchronous processes. This is a complex, and ever changing portion of code, and should be isolated, along with all of it's implementation details. Returning JSON, Core Data Objects, Realm, or SQL result sets leaks that implementation detail and complexity to the upper layers. The best way to avoid this is to work with POSOs (Plain Old Swift Objects) aka Entities. These entities contain no connection to the database and contain little to no logic. This allows them to be passed to any layer. The Translation layer is responsible for taking in the different Database/Network logic and returning these Entities.

Resume Transcript Auto-Scroll
Author
Skill Level Intermediate
1h 52m
Duration
8,328
Views
Show More Show Less
Skills covered in this course
Developer Mobile Apps Mac OS iOS

Continue Assessment

You started this assessment previously and didn't complete it. You can pick up where you left off, or start over.

Start Your Free Trial Now

Start your free trial now, and begin learning software, business and creative skills—anytime, anywhere—with video instruction from recognized industry experts.

Start Your Free Trial Now