# Organizing Data in Long Lived Applications

DevFeed: [Organizing Data in Long Lived Applications](<https://devfeed.tech/articles/organizing-data-in-long-lived-applications-40618.md>)

Original publisher: [Read original article](<https://eviltrout.com/blog/2013-05-26-organizing-data-in-long-lived-applications/>)

Published: 2013-05-26T00:00:00Z

Content type: opinion

Language: en

Sources: [Robin Ward](<https://devfeed.tech/sources/robin-ward.md>)

Topics: [Ember](<https://devfeed.tech/topics/ember.md>), [Framework](<https://devfeed.tech/topics/framework.md>), [App](<https://devfeed.tech/topics/app.md>), [Database](<https://devfeed.tech/topics/database.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [application](<https://devfeed.tech/tags/application.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [developer](<https://devfeed.tech/tags/developer.md>), [ember](<https://devfeed.tech/tags/ember.md>), [framework](<https://devfeed.tech/tags/framework.md>), [js](<https://devfeed.tech/tags/js.md>), [performance](<https://devfeed.tech/tags/performance.md>), [refactor](<https://devfeed.tech/tags/refactor.md>), [server](<https://devfeed.tech/tags/server.md>), [state](<https://devfeed.tech/tags/state.md>)

## AI overview

The article examines trade-offs in designing long-lived Ember.js applications. It contrasts their larger initial downloads with benefits for users who navigate extensively, then compares server-side request handling with client-side state retention using a user directory as a case study.

## Source excerpt

Trade offs As a developer you're constantly faced with issues of choice: What library is best? What framework is best? What platform should we deploy on? Most of the time there isn't a clear winner. The decision you make comes down to a series of trade offs. Do you want to optimize for developer happiness or performance? Do you care more about platform maturity or cost? One trade off Ember.js has made relates to how it favors long living applications.