Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Java Java Data Structures - Retired Efficiency! Custom Serialization

Posted by Adiv Abramson
Adiv Abramson
6,919 Points

Why not use a lightweight database when prototyping the MVP?

Since the ultimate goal is to store/retrieve song and artist data in a database, why spend time coding a purely in memory data access paradigm with Arrays and Maps? Isn't that wasteful since it will be discarded in a production version? Or is the cost of developing a temporary data access scheme based on in memory constructs less than creating a rudimentary database when rapidly prototyping a solution?

Thanks!