[AWS DB] Why AWS Databases/RDS #2

In the last blog post, we mentioned the On-Prem (Bare Metal) database servers and AWS RDS service. If you haven't gone through the first article then go through the same first. URL

Now we will continue with the advantage of using AWS RDS a PaaS Service by AWS, but we can’t ignore some cons as well with RDS to discuss.

Here, I am going to compare the cloud and on-prem in a dramatic way. Say, we have two companies named “ABC” and “XYZ”, both got a pre-requirement from their project about an On-Prem DBMS system.

This requirement is understanding came in the initial phase of the project discussion with the customer along with some other application, which the customer is planning to outsource to either company ABC or XYZ.

As this is an initial requirement, clarity is missing regarding server capacity (CPU/RAM/Storage, etc.), Database flavor, and how soon H/W is required in turn vendors associated.

Here company ABC is calm and proceeding with further discussion, on the other hand, XYZ is moving here and there with different technical teams/vendors, etc, and is worried about requirements.

Company XYZ is not clear on the hardware requirement as this is the initial phase and talking with vendors with different RFP with different configurations. Vendors respond with cost and varied time per requirement, by which they can deliver the hardware.

At the same time, XYZ is finding out the team as below:

• System Admin
• DBA
• Backup team

Which is again time-consuming in the case of on-prem.

Now big picture, considering procuring a server at one point in time was too costly and you can think of all hardware. There was a case when a team kept waiting for a RAM increase from 128GB to 256GB for a month or two and similarly for storage devices. And this was far costlier and the company has to invest beforehand i.e., HIGH CAPEX.

Yes, you are right, how we can ignore the space required and associated cost to install the new servers and provision necessary requirements like Air-Conditioning 😊.

In addition to physical infrastructure, you need multiple teams to install/manage/maintain the complete infra from start to end as we already discussed in the previous blog.

On the other hand, company, ABC is calm and proceeds with further discussion with customers. ABC is playing its part efficiently, and instead of On-prem they were talking about Cloud since initially and that is the secret of their calmness.

Refer below picture for a comparison.

Yes, again got it right. Cloud gives you flexibility where you don’t have to worry about launching your infrastructure without worrying about finding the vendor, long wait time, or huge cost investment i.e., CAPEX beforehand.

But you can launch your server with different configurations within minutes with just a few clicks and no more wait/vendor discussion etc. Even this hardware is not purchased in advance on-prem, so no big investment and can’t be discontinued when not required saving cost.

In addition, the capacity requirement is not a big challenge now, anytime you can upgrade your servers as and when required within seconds. How? This will be discussed later considering databases. So, keep following 😊.

Cloud also reduces your administrative overhead, which we are responsible in case of on-prem as below:

- Database administrative burden.
• Backup
• OS patching
• Database patching (Optional)
• Internal hardware maintenance.

Amazon RDS Features
• Lower administrative burden. Easy to use
• Performance. General Purpose (SSD) Storage
• Scalability. Push-button compute scaling
• Availability and durability. Automated backups
• Security. Encryption at rest and in transit
• Manageability. Monitoring and metrics.
• Cost-effectiveness. Pay only for what you use.

Cloud Benefits:
• Faster time to market
• Scalability and flexibility
• Cost savings
• Better collaboration
• Advanced security
• Data loss prevention

Of course, like any technology, there are pros and cons to cloud computing.

Disadvantages of cloud computing include:
• risk of vendor lock-in
• less control over underlying cloud infrastructure
• concerns about security risks like data privacy and online threats
• integration complexity with existing systems
• unforeseen costs and unexpected expenses.

Note– Just refer to the “Shared Responsibility Model” diagram shared in part-1.

In conclusion, company ABC won the bid and the customer is more focused on their application release.

Important to think about the information shared above and this will help you further in future blog post. This is also going to help you if you are planning for the AWS Certified Database Speciality Exam as these will contain a few questions asked in the exam.

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 the 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...