hi there, my name is Bradley Knapp, with IBM, and the question that i want to help you
answer today, is what is DBaaS? what is this DBaaS thing? so DBaaS
what is it? DBaaS is an acronym that stands for database as a service that's our D and our B here
literally stand for database. What is database as a service? So if we think about our cloud model
of as a service products, and as a service offerings, and if you've got any questions
about that we've got a bunch of other videos on the channel that you can review to learn about
that as a service model, DBaaS is the ability to deliver a database in that as a service model,
and so if you think about the traditional way to deploy a database, right? Is you'd go over here,
and you'd order some sort of a server, and on top of that server you'd put linux,
and then on top of that linux, you would install your database software, right? So
MySQL, and so there's a lot of work involved in this, right? You have to go out you order the
server, configure the server, put your linux on it, whatever it may be download compile,
and install your database software. There's a lot that goes on into this. Now you can script it.
You can make it faster. You can make it easier, but there's still a lot to get it set up, but
getting it set up isn't the hard part. Once it's set up, you've got to keep it running, and that's
where the real challenge comes in, right? Because what do you have to worry about when you have all
of these things? Well you've got to worry about your users right, and so with all of the users
who can log into the server? Who can log into the operating system? Who can log into the database?
What kind of access levels do they need? What kind of permissions do they need? You've got to worry
about patching, hardware patching, firmware patching, software patching for the operating
system, software patching for your database. You have to have somebody who keeps up with
all of those patches protecting against security vulnerabilities. You've got to think about your
access control model? Who can get into this? Why? And when do you have separation of duties between
your database administrators and your server administrators? Or can people cross-pollinate?
There's a lot of work that goes into successful operation of a database server,
particularly something that's going to be hosting a production workload.
You’ve got to build it. You've got to secure it and, oh hey by the way, you've got to operate it,
and what does that mean? What do i mean when i say you've got to operate it? Well
so you've got these three components here, that you also have to have backup.
What happens if the server goes down? You've got to have backups of it. You've got to have
quiest versions of the database. You're going to have backups of your operating system,
all of your configuration if the server goes down. You need to restore from those backups. You need
to bring it back up live again and there's a lot of work that goes into all of that hence,
database is a service. So what happens? Well the whole idea behind database as a service is
instead of you doing all of this work, we the cloud provider are going to do most of this for
you, and so you're going to come to us and rather than ordering the server, and telling us what
operating system, and what version of database software, and all that, you want, you're going
to say, “hey bradley, i want MySQL database as a service, I want an ms, a MySQL database
that i can just log into and start using, and it's going to have connections on it. You're going to
open some ports up for me so that it can work for a web server or another application server,
and i just want to interact with it in an as a service manner. I don't want to worry about
backups. You take care of that. I don't want to worry about running it highly available.
You take care of that. I don't want to worry about it crashing and me having
to restore it. You guys take care of all of that. What i want is a database
that has connections for user sessions, that has connections for app server sessions, and then it
has connections for admin, admin services, and i don't want to worry about backups and all of those
kinds of things.” The cloud provider takes care of. All of that, that is the as a service part,
and so on the back end to the cloud provider that you are buying this database serve, this
database as a service product from, they're going to take care of the hardware the operating system,
the patching, the user access, the security, the backups, running it highly available guaranteeing
that it's always up always available. They are going to take care of all of those things for you.
You're just going to subscribe to this service, as a service, right? You're going to pay an amount
per month, and that amount is going to be built up of how many writes do you make the database,
how big is the database, how much storage space does it take up, uh what level of availability
do you want, does it have to be, available with three nines or four nines or five nines of uptime,
and then some other little little add-ons, but it allows you to tailor your spend to where
you are only spending what you need to run your workload, and so when it's pitched like this of
course everybody comes back and they say, "oh man, that sounds great! why wouldn't everybody only buy
database as a service? Why would anybody go out and ever stand up their own database ever again?”
This is a good question and let's talk about that for a minute because the big difference between
database as a service and running it yourself is that, in a database as a service model a lot
of the administrative control the very specific tweaking and tuning that you can do on a database
to make it run faster. That gets abstracted away from you, the person who are consuming it, because
it's run by the cloud provider and so if we think about our two models, right? Our as a service
model versus our role your own model enroll your own which is where you set up everything yourself,
you have a hundred percent administrative control over everything. You decide what users get access,
you decide what your backup strategy is, what your restore strategy Is, you decide
everything on your own, and like in spider-man with great power comes great responsibility.
Now in that as a service model cloud provider is going to make a bunch of those decisions for you
makes your life easier, but you can't get in and twist all of those dials and knobs and tune that
database so that it runs at 100 performance, all the time, specific to your workload, and so you
may end up having to oversize your database as a service from a performance perspective
as compared if you rolled your own, but that's okay because if you don't want to go out and
hire your own database administrators, and hire your own server administrators,
and deal with the headaches of user access and security and integration you don't have to. You
can consume it in an as a service model. You don't need to worry about that cloud providers going to
take care of that. All you worry about is plugging your endpoints in to where they need to be
and being sure that the right people have the credentials and everything else is going to get
taken care of for you. So that you can focus on what you really want to do which is running that
workload and providing the service out to your customers, your partners, and your consumers.
Thank you so much for your time today. If you have any questions please drop us a line below. If you
want to see more videos like this in the future, please do like, and subscribe, and let us know.