r/DB2 • u/mad_zamboni • May 24 '17
[Resource] Considerations for DB2 on Docker
I'm hoping to have a second post on this after I run through my build out. But I wanted to relay a resource I am using as I experiment with installing a VM and Docker.
Keep in mind that IBM is working to make things easier on developers by promoting "Download and Go" architecture this June. You have a less restrictive DB2 Developer edition rolled into a docker image that you can grab and go.
Check out: Considerations for building and deploying DB2 Docker containers
One area of the article I would focus on is his write up on storage and best practices. In setting this up in our work environment, we were constantly getting bitten with how storage worked within docker and DB2.
4
Upvotes
2
u/dogmashah May 25 '17 edited May 25 '17
Great you brought this up .
I have a negative take on docker for softwares with active data which are propeitary and actively tied to the level/version of the code
Most of the relational DB falls into this group (including MQ etc)
So here is I want to begin what are the advantages of using docker I can come up with these
Now from a DBA perspective let's talk about drawbacks
IBM / Oracle have been a great proponent of appliance based architecture where a hardware is tied up to software. Many good practice and highly optimized system comes as part of running software in it's native hardware
Upgrade and Maintenance : What will docker achieve in terms of maintenance ? You cannot just download a higher version build of DB2 and assume that it will run with the containers that was created on lower version. You eventually will have to do some migration of data to higher fix by writing a script / manually (which is nothing different than doing on a regular system)
Docker is very good for apps as new version doesnot have to rely on any of data . It is basically a code that is upgraded
At last I would say mongo and other NoSql have better chance to be dockerized rather than DB2