[AWS DB Series] On-Prem DB Vs AWS RDS #1

In this blog post, we talk about AWS Relational Database Service (RDS) and why should be considered RDS as an alternative to On-prem traditional databases.

Note- This is a start and there will be more on the way. So subscribe/follow.

But before starting on AWS RDS, it is also necessary to discuss the traditional database system.

Traditional Databases:
When we start thinking about the traditional or on-prem databases worked on, a picture comes to mind where a Server (Bare Metal) with huge hardware having supported OS (Operating System) with RPM/Packages installed as recommended by the database vendor before proceeding for database installation followed by configuring. Even we know the challenges during installation till configuration to connecting applications and performance. Typically, it looks like below:

Now we need different teams to be involved to maintain all levels of this infrastructure starting with:
(1) Hardware Team
(2) System Administrator (For OS related activities)
(3) Database Administrator (DBA)
(4) Security

An important factor we definitely have to consider with this architecture is the huge CAPEX in setting up the server and administration overhead with the risk associated and a few indirect tasks.

Also, it’s important to know about different Cloud models including the responsibilities of AWS and Customers through the diagrammatic presentation below:

AWS Relational Database Service (RDS):
Amazon Relational Database Service (Amazon RDS) is a collection of managed services that makes it simple to set up, operate, and scale databases in the cloud.

AWS RDS falls under PaaS Category i.e., blocks in RED need to be managed by the Customer and green blocks will be managed by Cloud provider AWS.

Now compare the On-Prem database discussed initially with the AWS RDS considering PaaS.

In the case of AWS RDS, many of the administrative tasks required to keep the database running smoothly will be handled by AWS RDS itself.

Having AWS RDS is definitely advantageous instead of managing own relation databases on-prem. How? We will come to know about it in a future blog post.

Ref:

• AWS RDS

Important - The information shared above will help you further in the future blog post in the series. This is also going to help you if you are planning for AWS Certified Database Speciality Exam as these will contain a few questions asked in the exam. Refer to details on the exam here.

In case any help is required connect me over LinkedIn and topmate.io.

Please share your thoughts/feedback, which definitely matters the most to make the blog post more refined and useful.

Happy Learning and Sharing...