-1

Me and a friend are going to be working on an iPhone app that is going to be sending and requesting a lot of information from a 24/7 server (a 2009 Mac Mini). There's going to be a lot of realtime information floating around, and we're not sure what a robust database solution for that info would be. We're essentially looking for a db that's really fast and powerful, but still pretty simple to use, especially since we'll be accessing it from Objective-C, which is still pretty new for us. Is Sqlite what we're looking for? A colleague of ours suggested using PostGres, but isn't PostGres pretty dated?

benjammin
  • 537
  • 5
  • 23
  • Is this database going to be used on the iPhone or the Mac side? – bbarnhart Feb 17 '12 at 21:43
  • 1
    If it'll run on a 2009 Mac Mini as a "server" then pretty much any RDBMS should suffice. It's not like you will be deploying an enterprise-level solution that way. This sounds like the equivalent of wanting to get the best delivery truck for a trip to the grocery store when a minivan will be perfect. – JNK Feb 17 '12 at 21:45

2 Answers2

1

SQLite is great for the iPhone side. Are you asking about that or the server?

David Dunham
  • 8,139
  • 3
  • 28
  • 41
  • Yeah, I was actually asking about the server side of things... it's an area I'm admittedly not too familiar with – benjammin Feb 17 '12 at 23:30
  • Then I'm pretty sure you don't want SQLite. I believe MySQL is the kneejerk answer for server-side databases, but I'm not expert there. – David Dunham Feb 18 '12 at 00:16
0

Take a look at the Core Data, Apple's native solution for object graph management and persistence. It uses SQLite internally (though you can set different storage type, including in-memory one), and it is very flexible and optimized.

secondcitysaint
  • 1,158
  • 12
  • 20