For each database below, you will find two instructions: one to install and start the database using Docker and one to install and connect to that database using a CLI. To connect to a database, you will need a client - ideally, one that you can quickly use via the command-line/terminal. Once you have your account, log in to it either in the UI or with docker login. That will be needed for some of the databases. Once you have Docker installed, make sure you have an account in the Docker Store - sign up here. It's easier to manage the containers in your system once you create them (start/stop/restart/delete). And while Kitematic is optional, I recommend you download it, as well. This will be useful not only for this article but pretty much for everything you will eventually install in the future. If you haven't already done it, make sure you install Homebrew and Cask - package managers for Mac OS. Running RDBMS in containers may not be suited for production, but for development/testing environments, it is the perfect fit. If you really want to make your developer life easier, get used to using Dockerand spinning up databases in containers. In today's containerized world, this is in the past. Sometimes, I'd face problems like dependency hell, conflicts, and missing native libraries, and would eventually end up running the databases in isolated VirtualBox VMs. Now, in the past when I used to run Linux on my laptops, I'd just install each database directly into my environment. If you are beginning your software development career using a Mac and are interested in using relational databases like MySQL/MariaDB, PostgreSQL, Microsoft SQL Server, Azure CosmosDB SQL, or Oracle Database, then this article is for you!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |