The pros and cons of DBaaS Database as a Service

With DBaaS you can test multiple solutions and buy only the licenses and hardware you need to be successful.

Almost every company is now a data center. Whether the data is for internal applications and systems, or for other services offered, let’s be honest …

Data management is a key to success.

Before we list the pros and cons of DBaaS, we need to explore some of the decisions companies need to make.

These include countless quick data processing decisions that can put them on a path that, if incorrect, is difficult and costly to correct. Those decisions are:

What type of database, SQL or NoSQL?

What are the data storage and query needs? Transactional? Big data?

Which database system to use? A few SQL choices may be Oracle, MySQL, MSSQL and Sybase. A few No-SQL choices are MongoDB or Cassandra.

Do we have DBA (database administrator) talent or should we hire?

What kind of server or resources are needed? What are my requirements for power, server, disk, processing, network and IO?

How can I maintain, backup, manage and otherwise own the database framework?

What are my cost of ownership?

First let’s see which database type to use, SQL or NoSQL.

Traditional database types classified as SQL occupy an important place in companies and are a mainstay of business choices. However, when companies start making applications that make decisions based on a significant database analysis of large, almost unfathomable amounts of data, they migrate to NoSQL solutions such as MongoDB or Cassandra.

NoSQL’s architecture makes it a great choice for big data solutions, while the built-in protection of a transaction-based system like Oracle makes it a better choice for banking or similar solutions.

When it comes to choosing a specific system, companies stick to what they know. In other words, if they already have Oracle and Oracle talent, it would come as no surprise that when management asks individuals which database system to use on Project X, they choose Oracle.

Tailoring a specific database system to a range of business requirements is a tough task that should always be viewed with a fresh eye. It should not be based only on what talent is already employed or on which systems a company feels comfortable.

Let’s face it, if a company chooses correctly, everything is fine. If they choose incorrectly, they have wasted a lot of resources, which amounts to dollars. Enter DBaaS.

What DBaaS excels at is that it gives companies the opportunity to test the waters a bit, to try before investing heavily.

DBaaS acts as a stepping stone to total ownership, a cost effective solution to help you identify your needs before investing heavily.

DBaaS has both advantages and disadvantages.

First, a distinction must be made between “hosting database systems” and DBaaS.

There are many cloud-based solutions that ‘host’ a database system but do not provide significant assistance in configuring, tuning, consulting and providing the talent needed to actually use those systems.

True DBaaS offers both the system and the talent to help you use the database and determine how to store, retrieve and analyze your data. The value of DBaaS goes far beyond hosting.

The benefits of DBaaS include:

No equipment or software licenses.

Flexibility. Multiple choices are available to test your applications and choose the right platform for your business requirements.

· Significantly less staffing needs. The DBaaS provider takes care of the installation, configuration and in many cases development.

Offsite hosting, protection against local power failures or disasters. Many companies design their system for power redundancy, but in reality rarely meet those goals.

SLA agreements with redundancy, uptime and backup protection. A DBaaS provider has tried to focus on protecting your data.

Meanwhile, the drawbacks of DBaaS are:

Limited access to underlying servers. This can present itself as a feeling of no control.

Very little knowledge about how your data is protected against cyber threats. This can be dangerous for sensitive data.

So how do you decide? Is there a transition from one to another? Yes, almost always, but by following a few guidelines to get you started, DBaaS can be used correctly.

Those wishing to use DBaaS should adhere to the following guidelines:

1. Perform all development with DBaaS. This is your chance to test different architectures and functions.

2. Unless you fully disclose how your data is protected, managed and secured by DBaaS providers, it is recommended that you consult with database architects to host sensitive data internally. Note, these are usually not big data. When we use the terms sensitive data, we mean exactly that. Data such as SSNs, account data, financial data, personal data, etc. Does this mean that you cannot use DBaaS for this? No, it means you need to find a DBaaS provider first that will show you everything from how your encrypted data gets into their system to storage, access, etc.

3. If you are not sure what your database needs, use DBaaS first. This allows you to try SQL or NoSQL. This allows you to explore the encryption capabilities of Oracle versus MySQL. Think of DBaaS as buying a car. You test sedans, trucks and SUVs and try different manufacturers and functions. You can decide to lease or buy.

4. Always check and evaluate the cost of ownership. As your system grows, running costs can make sense to drop DBaaS and build an internal system. However, by then you have already decided what you really need.

The goal of DBaaS is to test multiple solutions and only buy the licenses and hardware you need to be successful. You can then hire the right talent to manage your system.



Source by David Moye