COMMERCIAL DATABASE , NOSQL

BATCH (25)
DATABASE, AND OPERATIONAL DATABASE
AUNG MYINT TUN
SI THU LIN

PRESENT BY GROUP (1)

WINE HTUT
KAUNG ZIN HEIN
Commercial database
A Commercial Database is used by a commercial Company to store
and query data. This data can be customer's, Employees, Stock details and
any other data the company needs to store in their operations. The
Commercial Company is created with profit in mind and uses the database
for its commercial values. Theses types of databases can have a small
amount of involvement in the company's operations or the company can
fully rely on the database's functionality for its operations.
Key characteristics of Commercial
Database

Commercial databases, based on the relational database management

system (RDBMS) model, use tables with predefined relationships for
efficient data storage and manipulation through SQL. Some offer
object-relational capabilities, suitable for object-oriented programming.
They're designed for scalability, both vertical and horizontal. These
databases prioritize performance, durability, security, and encryption,
often using transparent data encryption (TDE). They come with
management tools for tasks like backup, performance monitoring, and
integration, including connectors and APIs. Vendor support ensures
ongoing maintenance and technical assistance.
ow Commercial database works?
Commercial databases work by organizing
structured data into tables with rows and columns,
using SQL for data interaction. They optimize
query performance, ensure data integrity, and
offer security features. Transactions, concurrency
control, and indexing manage multi-user access.
These databases support scalability, high
availability, and backup for data protection.
Monitoring tools aid administrators, and
integration with other systems enables data
analysis. Popular commercial databases include
Oracle, Microsoft SQL Server, and MySQL, with
variations in features but shared core principles of
data storage and management.
NoSQL database
Next Generation Databases mostly addressing some of the points:
being non-relational, distributed, open-source and horizontal scalable. The
original intention has been modern web-scale databases. The movement
began early 2009 and is growing rapidly. Often more characteristics apply
as: schema free, easy replication support, simple API, eventually
consistent /BASE (not ACID), a huge data amount, and more. So the
misleading term "NoSQL" (the community now translates it mostly with "not
only sql") should be seen as an alias to something like the definition above.
Key characteristics of NoSQL databases include:

Flexible Data Models: NoSQL databases can store and manage data in flexible ways, including key-
value, document, column-family, and graph formats. This flexibility is particularly useful for
handling data with varying structures.

Scalability: NoSQL databases are often designed to scale out horizontally, allowing them to handle
increasing data loads and traffic by adding more servers or nodes to the system.

High Performance: NoSQL databases are optimized for fast read and write operations, making them
suitable for applications that require low-latency data access.

No Fixed Schema: Unlike SQL databases, NoSQL databases typically do not enforce a rigid,
predefined schema, allowing for dynamic and evolving data structures.
Distributed Architecture: Many NoSQL databases
are distributed, which means they can operate
across multiple servers or data centers, improving
fault tolerance and availability.

Common types of NoSQL databases include

document databases (e.g., MongoDB), key-value
stores (e.g., Redis), column-family stores (e.g.,
Apache Cassandra), and graph databases (e.g.,
Neo4j). Organizations often choose NoSQL
databases when they need to handle large and
complex data sets, especially in web applications,
big data processing, and real-time analytics. The
choice between SQL and NoSQL databases
depends on the specific requirements and
characteristics of the project.
How NoSQL data base
works?
NoSQL databases work differently from traditional
relational databases. They are designed to handle
unstructured or semi-structured data and offer
flexible schemas. NoSQL databases use various
data models, such as document, key-value,
column-family, or graph, to store and retrieve
data efficiently. They often scale horizontally,
distributing data across multiple nodes or clusters
to handle high volumes of data and traffic. NoSQL
databases can be well-suited for applications that
require flexibility and rapid data ingestion, such
as social media platforms and real-time analytics,
but they may sacrifice some transactional
Operational database
An operational database is a database that is used
to manage and store data in real time. An operational
database is the source for a data warehouse. Elements in an
operational database can be added and removed on the fly.
These databases can be either SQL or NoSQL-based, where
Example:
the latter is geared toward real-time operations.
 Human resource database that include data identifying
each employee and his or her time worked, training
and development status
Key characteristics of operational databases include: Transactional Integrity:

Operational databases ensure data consistency and transactional integrity. They are ACID-
compliant (Atomicity, Consistency, Isolation, Durability), which means they guarantee that
each transaction is processed reliably and without errors.

Real-Time Processing: These databases are used in scenarios where real-time or near-real-time
data processing is essential. For example, they are used in point-of-sale systems, e-commerce
platforms, airline reservation systems, and more.

Schema and Data Structure: Operational databases have a predefined and structured schema,
often in a relational format, which enforces data consistency and integrity.
Read and Write Operations: They are optimized for frequent insert, update, and delete
operations, as well as quick retrieval of specific records.

Data Integrity: Maintaining data accuracy and ensuring that the data reflects the
current state of the business is a top priority for operational databases.

Concurrency Control: Operational databases implement mechanisms to manage

concurrent access by multiple users or applications, preventing conflicts and ensuring
data consistency.

Common examples of operational databases include SQL-based systems like Microsoft

SQL Server, Oracle Database, and MySQL, which are commonly used in businesses to
support various operational tasks, such as order processing, inventory management,
and customer record keeping. These databases are typically used to store structured
data and are distinct from analytical databases used for data warehousing and
How Operational database
works?
Operational databases, also known as OLTP
(Online Transaction Processing) databases, are
designed for day-to-day, transactional operations
within an organization. They handle routine tasks
like data entry, retrieval, and updates. These
databases use a normalized data structure to
minimize redundancy and maintain data integrity.
They are optimized for quick and efficient data
retrieval and support concurrent access by
multiple users. Operational databases ensure data
consistency, enforce constraints, and are typically
used for tasks such as order processing, inventory
management, and customer records in real-time,
THANK YOU
Any Question?