Accessing Persistent Data in a Relational Database

Introduction Most applications need to access persistent data at a certain point in time that exists in relational databases, flat files, mainframe systems, LDAP repositories, or through services via external systems. When a business component needs to access a data source, it must connect and manipulate the stored data using the appropriate mechanism. The mechanisms for accessing these different types of persistent storage are diverse and often include proprietary APIs; access mechanisms for different data sources have little in common.

Databases are an important part of web applications. If you want to load data or if you want the application to survive after the page has been updated, you need to connect to the database. First, we describe the possible associations between different types of databases (relational and nonrelational databases), data (one to many, many - to - many etc) and their associated branches (external IDs). I learned to use SQL for accessing and manipulating databases, but then replaced these long SQL commands with the Sequelize ORM which converts the data from the JavaScript object model to the format used by the SQL database manager. We use Postgres to run the database, but there are many more options. Finally, we integrated the Sequelize code and Express routing to create a (very basic) persistent full stack web application.

Web applications use relational (SQL) databases or nonrelational (NoSQL) databases for persistent data storage. The focus of this article is to explain a simple high-level overview of relational and non-relational databases, highlight the differences, review the scenarios where each database is used, It is to examine the system easily. I am not claiming to be a database expert, so some languages ​​in this article use generalization. I have studied more about databases, but I know that I am a good developer, and this article will give you enough information-based decisions about databases I hope to give you some information.

In most application development projects, the technology used to persist data is a relational database. Database designers are responsible for defining detailed database designs, including tables, indexes, views, constraints, triggers, stored procedures, and other database-specific structures necessary for storing, retrieving, and deleting persistent objects. This information is managed in the deliverables: data model.