Member-only story
Database Running in Docker
Make it work with already running Go container
- part: creating the service
- part: improving the service
- part: upgrade for web
- part: adding SSE
- part: simple javascript frontend functionality
- part: frontend — backend communication
- part: server-side logging
- part: run it all in docker
- part: you are reading it right now
- part: database — service communication
Addition 1: functions, methods, pointers and interfaces
Addition 2: websocket communication
Addition 3: socket communication
Is it a good idea, to run database in Docker?
From the developer point of view… is is the best thing you can do. You can run multiple different databases on multiple ports so you can very easily develop your software against all of them. Running MySQL, MariaDB, PostgreSQL and SQL Server all at once? No problem.
Also… have you ever tried to uninstall SQL Server? I don’t know how about you, but on my machine, there was always something left. Using Docker you can very easily run, start, restart, stop and delete database as you like, and be sure that nothing was left.
From the user point of view… why not. And by this I mean using Docker in production. Our company is using MySQL and PostgreSQL in Docker for about three years on about 50 different machines, without any problems. Databases are huge, communication is huge and everything is working without problems on Linux and Windows machines.
As a bonus you can make your database secure, so it’s not accessible from outside Docker. More on that in the article.
My recommendation is: when running in production, prefer Linux machines. The reason is, that you have your database data stored directly on the hard drive, but in case of Windows, they are stored inside a virtual machine.
Run PostgreSQL in container
This article will help you to add PostgreSQL container, so we can (in the final…
