title: What is Sqlite used for?
body: <p>I don't know how authoritative this is but I found this:</p>
  
  <p><a href="http://www.sqlite.org/cvstrac/wiki?p=PerformanceConsiderations" rel="noreferrer">http://www.sqlite.org/cvstrac/wiki?p=PerformanceConsiderations</a></p>
  
  <p>and it doesn't seem good to have a lot of connections to sqlite.  This seems to be bad for the web and most applications that have more than a few users.  I'm having a hard time thinking of what sqlite would be used for when you don't need that many connections.  Every program I can think of needs users, lots of them sometimes, so what would I use a database for that doesn't allow that many connections?  I thought about prototypes but why would I use that when I can just connect to a larger database?  Embedded apps maybe?</p>
  
  <p>Thank you.</p>
  
  <p>EDIT:  Thanks everyone.  I look at the page recommended below but an confused about something:</p>
  
  <p><a href="http://www.sqlite.org/whentouse.html" rel="noreferrer">Under appropriate uses for sqlite it has:</a></p>
  
  <p>Situations Where SQLite Works Well</p>
  
  <p>•Websites</p>
  
  <p>SQLite usually will work great as the database engine for low to medium traffic websites (which is to say, 99.9% of all websites). The amount of web traffic that SQLite can handle depends, of course, on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.</p>
  
  <p>Situations Where Another RDBMS May Work Better</p>
  
  <p>•Client/Server Applications</p>
  
  <p>If you have many client programs accessing a common database over a network, you should consider using a client/server database engine instead of SQLite. SQLite will work over a network filesystem, but because of the latency associated with most network filesystems, performance will not be great. Also, the file locking logic of many network filesystems implementation contains bugs (on both Unix and Windows). If file locking does not work like it should, it might be possible for two or more client programs to modify the same part of the same database at the same time, resulting in database corruption. Because this problem results from bugs in the underlying filesystem implementation, there is nothing SQLite can do to prevent it.</p>
  
  <p>A good rule of thumb is that you should avoid using SQLite in situations where the same database will be accessed simultaneously from many computers over a network filesystem.</p>
  
  <p>The Question:</p>
  
  <p>I'm going to show my ignorance here but what is the difference between these two?</p>