Selecting and implementing an embedded database system

Abstract

Although embedded systems share many characteristics with their desktop and server counterparts, the unique advantages, limitations, and requirements of the applications they run demand a careful selection process and tailored implementation. The key strategy in choosing database tools for embedded systems is to focus on the application's requirements. Embedded database products vary widely from vendor to vendor. Some will do less than a particular application needs, some will do much more. By surveying the choices carefully, you can choose the tool that most closely matches your requirements. After choosing the operating system, hardware platform, and database software for a new embedded system, you must design a system that runs reliably with little or no human intervention. Unlike desktop and server systems, embedded systems cannot ask for operator help when the application encounters a problem. Finally, performance matters. Designing for performance up front, and evaluating it once you've built the application, is crucial. Fortunately, you can choose from a variety of techniques for evaluating and improving performance in database applications. To arrive at the best embedded-database-system solution, you must select the product that best matches your specific needs, then integrate that solution with your application. Start this process by evaluating which services your embedded application will provide.