RE: Oracle DBA to PostGreSQL DBA?

A big chunk of migration (back to time sharing, er, the cloud) is on. More chunks will follow. Jeremiah’s advice here is juicy with wisdom.  

If you’re a database operator (Database Administrator::Database Operator as Mainframe Systems Administrator::Machine Room Operator), your stay in place options are at risk.  

If you resemble this: “DBAs with responsibilities for managed cloud databases still need to be architects, designers, tuning experts and leaders to software development groups, so that their organization makes use of database technology wisely and effectively. The cloud is a net positive to high-value IT contributors by relieving the organization and its employees of the undifferentiated heavy lifting of routine tasks. It elevates DBAs and makes them more influential.” in your current on premise role, your future is bright. Whether the threat to your role is off shore expertise at a price you cannot compete with or a move to the cloud, the skills Jeremiah has framed so well dovetail extremely well with the institutional knowledge I mentioned earlier in the thread.  

Regarding the migration: some very large institutions vary from being all in to having a toe dipped in the water. (Some are immune for now because of issues like super low latency to be the first to bid on stock trades. Some are immune [I hope permanently] because of national security. But not all operations of such institutions need any special features, so just because there are aspects of an institution that are problematic to duplicate in the cloud do not mean the other 95% of the computing needs have to stay on premise. [95% just yanked out of the air; no study or accuracy implied.])  

There are four major concerns any serious business addresses to its comfort level:  

1. Is our data secure?
2. Can we always get our data back?
3. Can a service outage put us out of business?
4. Can we reasonably migrate amongst utility providers to maintain leverage on price?

Books could be written on each of these topics and I’m not claiming that is an exhaustive list.  

Regarding this thread, there is an interesting play regarding 2): I claim the first thing a company should do when proceeding to remote services from anyone is to make sure they can get their data back continuously by actually getting their data back continuously. This does not need to be a system that can be spun up to handle application load. But you need to define what your important data is and be certain you have it in a reasonably portable form that you can read to verify.  

If you’re an IT professional at a firm migrating to the cloud, the project to prove you have custody of all your important data in a readable and portable form is an interesting play. (And never underestimate the bandwidth of a box of media on a bus or truck. Right Tim?)  

And of course the rates for COBOL programmers just keep going up. (Anecdotal data only. I don’t know whether that is an overall trend.)  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jeremiah Wilton Sent: Saturday, December 17, 2016 5:47 PM To: Andrew Kerber
Cc: tim evdbt; Oracle Mailing List
Subject: Re: Oracle DBA to PostGreSQL DBA?  

I do. In spades. For the same reason commercial cloud automation is more reliable than most one-off homegrown automation, commercial cloud security, safeguards and auditing is more reliable as well.  

http://www.cnbc.com/2016/11/30/how-amazon-web-services-is-luring-banks-to-the-cloud.html  

Jeremiah  

Sent from my iPhone

On Dec 17, 2016, at 2:38 PM, Andrew Kerber <andrew.kerber_at_gmail.com> wrote:

Migrating to the cloud is a pretty nebulous description. I think more companies are implementing virtualization and private clouds. I dont see any big movement to the public cloud in industries with privacy concerns or financial data.  

On Sat, Dec 17, 2016 at 2:26 PM, Jeremiah Cetlin Wilton <jcwilton93_at_earlham.edu> wrote:

There's a bright future for top DBAs in the cloud world. Managed cloud database services like Amazon RDS automate database deployment, backups, recovery, HA, DR, upgrades, patching and cloning. All of these things should be more or less automated anyway if a DBA has been in their position for a while and is doing their job fairly well. The benefit of using the cloud's automation over your own is that it has been produced as a commercial service, subjected to the standards of such a service, and perfected by having to run correctly every time on tens of thousands of systems for many years.  

DBAs with responsibilities for managed cloud databases still need to be architects, designers, tuning experts and leaders to software development groups, so that their organization makes use of database technology wisely and effectively. The cloud is a net positive to high-value IT contributors by relieving the organization and its employees of the undifferentiated heavy lifting of routine tasks. It elevates DBAs and makes them more influential.  

I think DBAs today should become experts in architecture, design, tuning, and multiple database engines and types. Oracle DBAs should probably move in the PostgreSQL direction, as that engine has become a favorite of enterprises moving off Oracle. You won't find PostgreSQL as wonderful as Oracle in every way (except one - price), but it has been improving rapidly, and suits many use cases already. The flip side of PostgreSQL's smaller feature set is that it makes it relatively easy to learn. Some companies like AWS (with the new edition of Aurora) and EnterpriseDB are making a concerted effort to build enterprise features onto PostgreSQL.  

Not all clouds are the same. Some boast only one managed database type, and as soon as you want to use another type, you have to go deploy and manage it yourself on a VM. Some clouds have ten years of maturity, while others were openly mocking the concept up until eighteen months ago. Some have huge geographical presence, orders of magnitude higher adoption, broad and deep service ecosystems.  

And also some have me and Kyle :-)  

Please let me know if you have questions about clouds or AWS in general. I'm in the belly of the beast and happy to be a resource.  

Jeremiah  

From: "Tim Gorman" <tim.evdbt_at_gmail.com> To: "Oracle Mailing List" <oracle-l_at_freelists.org> Sent: Friday, December 16, 2016 9:09:16 AM Subject: Re: Oracle DBA to PostGreSQL DBA?  

Bear in mind that the "cloud" has three layers: IaaS, PaaS, and SaaS.

SaaS (software as a service) involves complete IT solutions (i.e. Salesforce, Google Calendar, NetSuite, etc), so it means the elimination of most IT roles.

PaaS (platform as a service) basically means tools like databases, with AWS RDS as a classic example. With PaaS migration, the cloud company is supporting a limited set of database choices, and companies are developing solutions with those tools.

IaaS (infrastructure as a service) basically means "servers" and "storage", with AWS EC2 and S3 being classic examples, respectively. With IaaS, the SysAdmin role along with the datacenter has largely been eliminated, and DBAs, developers, and application admins are allocating virtual machines in IaaS. Migrating to IaaS is largely no different than migrating to different servers. The major gotcha is the OS platform, as most IaaS vendors only support x86 servers running Linux and Windows. Solaris, AIX, and HP-UX are largely supported only be vendor IaaS offerings, and they will soon be extinct. With IaaS migration, databases and applications are not "supported" by the cloud company unless such a service is purchased additionally.

So while "most companies" are indeed migrating to the "cloud", sometimes they are migrating to IaaS (a.k.a. someone else's servers), sometimes they are migrating to PaaS (a.k.a. someone else's tools), and sometimes they are migrating to SaaS (i.e. someone else's IT department).

The driving factor isn't necessarily lower cost, but more agility. As such, production systems are certain to migrate last, but non-production environments are certain to migrate first into what is called "hybrid data center".

Understand which choice your company is making, and plan accordingly.

If someone says "my company isn't migrating to the cloud", then someone is swimming in de Nile.

On 12/16/16 09:44, Mike Killough wrote:

That's a good point. I think that once there are no more premises databases, I will hit the retirement finish line anyway.  

Mike  

From: Dennis Williams <mailto:oracledba.williams_at_gmail.com> <oracledba.williams_at_gmail.com> Sent: Friday, December 16, 2016 10:39 AM To: tim.evdbt_at_gmail.com
Cc: mwkillough_at_hotmail.com; oracle-l-freelists Subject: Re: Oracle DBA to PostGreSQL DBA?  

All - I just saw an article stating that most companies are migrating to the cloud, so using the databases easily available and supported by the cloud company.  

Dennis Williams  

-- 

Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'



--
http://www.freelists.org/webpage/oracle-l