Database Technology

Databases are our stock in trade. We pretty much take it for granted that applications we design must be database-driven; it is a truly rare event when we embark on a project that does not involve a database in some way. At its simplest, a database is a way of storing organized information persistently. That concept is so fundamental to the needs of computing and the digital environment that databases these days are invisibly ubiquitous. Well, in our work anyway. But then, we're geeks.

There are really two sides to any database-driven application. First there is the database itself, which pretty much lays low and out of sight under the hood, and then there is the interface, or to stretch this metaphor even further, the dashboard. And probably the steering wheel and gas pedal and little knob that resets the odometer. But both aspects are equally important, though in completely different ways. It's important to have a powerful and reliable engine, but cup holders and leather seats - comfort and style - are what really determine a person's love or dislike of that vehicle. A database application must fuse left-brain engineering with right-brain design for a whole-brain experience. We pay equal respect to both the purely logical demands of the database and the visually "ergonomic" experience expected in these days of increased user sophistication.

Depending on the need, we employ Inmagic and/or SQL Server databases.