In previous posts such as Linux vs Unix and Types of computer architecture (part 1) we’ve looked at operating systems and types of computer architecture. If you haven’t read these previous posts you may want to.
A platform in technology is the underlying OS + Hardware combination that application/s can run on.
“Computer architecture” could refer to any number of different things in the world of enterprise technology and computer engineering.
In the enterprise “computer architecture” is usually used to mean Instruction Set Architecture. Still no idea what i’m babbling on about? Let look at some examples of Instruction Set Architecture.
You may want to brush up on the post about N-Tier Architecture if you don’t know what that is.
Today we’re going to look at a very basic resiliency pattern. In fact three of them. One for each tier of our classic three-tier architecture.
In the Types of Database post we looked at different types of databases. This post looks at the most common type of database, the relational database. The concept of the relational database was created by a chap called Edgar Codd.
We looked at different data stores in the Types of Data Store post. Different data stores are suited to different use cases. This post focuses on one type of data store called a database. A database is way of storing data in an organised way to make it easy to access.