If you’ve worked with relational database systems for any length of time, you’ve probably participated in a discussion (argument?) about the topic of this month’s column, surrogate keys. A great ...

A database that maintains a set of separate, related files (tables), but combines data elements from the files for queries and reports when required. The concept was developed in 1970 by Edgar Codd, ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

Most applications need some form of persistence—a way to store the data outside the application for safekeeping. The most basic way is to write data to the file system, but that can quickly become a ...

Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with content, and download exclusive resources. Cory Benfield discusses the evolution of ...

Key-value, document-oriented, column family, graph, relational… Today we seem to have as many kinds of databases as there are kinds of data. While this may make choosing a database harder, it makes ...

Databases are used in many different settings, for different purposes. For example, libraries use databases to keep track of which books are available and which are out on loan. Schools may use ...

Even with all the hype around NoSQL, traditional relational databases still make sense for enterprise applications. Here are four reasons why. Dave Rosenberg Co-founder, MuleSource Dave Rosenberg has ...