Getting Small: Building Lightweight Web Applications with Small-Footprint Databases
Not every application needs a full-featured enterprise-scale database. In such cases, you can reduce costs and save resources by using a small-footprint database.
by Vikram Vaswani
July 20, 2007
f you've done any open-source database development recently, you probably already know that when it comes to selecting a database for your application, you have a plethora of choices. You are no longer limited to commercial products such as Microsoft SQL Server or Oracle; open-source products such as MySQL and PostgreSQL are viable alternatives, offering similar features at a fraction of the cost.
However, while these products have rich, robust feature sets and reduce costs, they're not smallthe latest downloadable versions of PostgreSQL and MySQL weigh in at 12 MB and 57 MB respectively. For small-scale applications that have minimal database needs, using any large feature-rich database products is often overkill; it's often more appropriate to use a small-footprint database instead. Even though small-footprint databases may lack sophisticated features such as triggers, views, and stored procedures, they make up for the reduced feature set by requiring minimal resources and disk space.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!