---
# System prepended metadata

title: <center><i class="fa fa-edit"></i> DBaaS </center>
tags: [DBaaS]

---

# <center><i class="fa fa-edit"></i> DBaaS </center>
###### tags: `DBaaS`

:::warning
**References:**
- [DBaaS](https://www.stratoscale.com/blog/dbaas/what-is-database-as-a-service/)
- [IBM DBaaS](https://www.ibm.com/cloud/learn/dbaas?mhsrc=ibmsearch_a&mhq=DBaaS)
- [SDL and DBAAS service integration](https://wiki.o-ran-sc.org/display/ORANSDK/Accessing+Shared+Data+Storage)
:::

---
## DBaaS
### Definition
The term **“Database-as-a-Service” (DBaaS)** refers to software that enables users to setup, operate and scale databases using a common set of abstractions (primitives), without having to either know nor care about the exact implementations of those abstractions for the specific database.

For example, a developer could instantiate a database instance using the same set of API calls  or UI clicks regardless of whether the database was MySQL, Oracle or MongoDB. Similarly, the IT admin user could request a backup of the database, or create and resize a database cluster using the same call regardless of the particular database being used. It’s the platform’s responsibility to implement backup, cluster resizing or any other abstract operation correctly for each of the underlying databases that the platform supports

**In O-RAN DBaaS used to provide backend services for the SDL API.**

----
### Benefits
Compared to deploying a database management system on-premises, DBaaS offers your organization significant financial, operational, and strategic benefits:

- **Cost Savings**: Laying down infrastructure for database management is expensive; scaling it as needed is costly and often wasteful. With DBaaS, your organization pays a predictable periodic charge based on the resources you consume—there’s no need to purchase additional capacity to have on hand for hypothetical future needs.
- **Scalability—up and down**: You can quickly and easily provision additional storage and computing capacity at run time if you need it, and you can scale down your database cluster during non-peak usage times to save cost.
- **Simpler, less costly management** : To manage and maintain a database on-premises, you’d need an in-house administrative team. With DBaaS, the cloud provider manages everything (although you can choose to manage certain aspects yourself if you wish). DBaaS lightens the administrative burden on your existing IT staff and frees them to work on applications and innovation.
- **Rapid development and faster time-to-market**: With an on-premises database system, development teams typically need to request access through IT, a process that can take days or weeks. In contrast, with DBaaS, developers can help themselves to database capabilities and spin up and configure a database that’s ready to integrate with their application in minutes.
- **Data and application security**: Cloud database providers typically offer enterprise grade security, including features like default encryption of data at rest and in-transit and integrated identity and access management controls. Some also meet specific regulatory compliance standards.
- **Reduced risk**: DBaaS offerings from major cloud providers typically include a service-level agreement (SLA) guaranteeing a certain amount of uptime. In the unlikely event that your provider doesn’t meet the requirements stipulated in the SLA, you’ll be compensated for any excess downtime you experience.
- **Software quality**: The major cloud providers offer a wide variety of highly configurable DBaaS options—each preselected for quality, so you won’t have to worry about the wading through hundreds of different databases.

---
### SDL and DBAAS service integration
The RIC platform provides a shared data storage through its DBaaS service. SDL library in the app SDK is configured to automatically connect to the DBaaS service using parameters passed from the RIC platform instance.

![](https://i.imgur.com/lJmwnOr.png)
