About databases guide
What is a database?
A database is simply a place where you store information, you might want to use later. Ideally, this information should be organized efficiently, so information is easy to access. Libraries, address cards photo albums, email account mail boxes, numbered lockers are all great examples of physical databases.
These are in many forms, and we feel the most important features of a database is that they are ACID;
The simplest way to think of this is that information never gets lost if these databases are configured correctly.
Most common form of databases
Relational Databases (OLTP)
Relational databases are the most common form of databases inside enterprises. They offer full ACID compatibility, and allow for more optimal storage of information. We have extensive experience in building and reporting from OLTP databases.
Vendors we work with:
- Microsoft SQL Server
NoSQL or document databases
It is rare to find full ACID compatibility. NoSQL databases store data as documents, typically, these types of databases are used by websites which are less concerned about collecting data, and more concerned with retrieving data to support more users. Examples of websites which uses NoSQL are; traveling websites, hotel websites, and larger websites. One downside to these solutions is the lack of ACID, which may mean both a relational and NoSQL database is used in parallel.
Vendors we can consider include;
Multidimensional databases - Cubes
These sit on top of a standard form of database called a data warehouse. These are known as OLAP databases and allow for powerful analysis and presentation of data.
We think OLAP is a fantastic technology we love to work with.
Decentralised databases - blockchain
Blockchain, is a distributed ledger of events. You may know that cryptocurrencies sit on top of blockchain. A way to think of it, is that once a payment is validated, there are multiple copies of that payment saved everywhere. We, at Info Rhino are looking into using Bitcoin or Litecoin payments for our property platform, findigl.
We have no experience of using graph databases. Graph databases can dramatically help in linking information together. It just so happens, SQL Server - Info Rhino's weapon of choice supports graph databases, so, at some point we will venture into this area too.