Scribd
Upload
10 views2 pages

Hema Saireddy - Module 2 - Research - Assignment

Uploaded by

krishnachandu6561
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views2 pages

Hema Saireddy - Module 2 - Research - Assignment

Uploaded by

krishnachandu6561
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1

Introduction

Learning the architectural foundations of databases such as Cassandra and PostgreSQL is a

must before you can do a compare of them. Both databases, being frequently used, serve

different aims and differ in application scenarios because of their distinctive architectures.

A NoSQL database Distributed Cassandra was constructed which could manage huge

volumes of data across thousands of cheap computers. Unlike other databases, it neither has a

single point of failure nor gives high availability of the data. Its architecture is based on two

models: Google Bigtable and Amazon Dynamo DB. The two architectures have consistent

objectives of horizontal scalability and partition tolerance. Peer to peer distributed technique

is used in all the nodes of Cassandra which helps in fault tolerance and scalability with no

breaks. Each Cassandra cluster node is equivalent to any other node in the cluster and the

data is evenly distributed across the cluster. It specifically excels where writing performance

is critical and when the environment demonstrates rapid scalability and high fault tolerance

(using such architecture). These include vast online services, real-time analytics, and the

Internet of Things.

Unlike PostgreSQL, PostgreSQL is a well-known and stable RDBMS that has shown its

strength of reliability, adherence to SQL, and compliance to ACID. Its purpose is the

management of the data that is relational, which includes the complex searches, transactions

and data integrity constraints. PostgreSQL architecture is client-server type and has great

features for concurrency control and transactional consistency. This is a popular choice for

applications focusing on reliability, data integrity as well as comprehensive queries due of its

adaptability and the fact that it complies with standard. Financial systems, data warehouses,

and business applications are some of the types of such applications. The remarkable

differences between centralized and relational PostgreSQL architecture and decentralized and
2

distributed Cassandra architecture are why both hold up well in range of cases. Unlike

Cassandra with emphasis on enormous scalability, high availability, and eventual consistency,

PostgreSQL prioritizes complex operations with strong consistency and integrity assurances.

You might also like