SQLite directly embedded in your application #softwareengineer #database #developer

Another little bonus of using SQLite directly is that you can use it right in your application. You won't have to set up a separate container for Postgres and MySQL. Sure, running those on your system is usually pretty straightforward anyhow. But with SQLite, it's not a problem at all. You don't have to worry about it. It's seriously just a file and this makes testing things quicker and simpler. Plus, you can also run multiple instances in the same app at the same time without any problems at all. That's a really neat thing. So creating and testing with SQLite is quite powerful and makes your experience smoother overall. Another small thing is that you won't have to deal with setting up a complex connection. Usually, you connect to the database using connection parameters and a host name or IP address. But with SQLite, we don't have to worry about those extra credentials, host names or other dependencies. It's just a file on your disk. This makes things a lot simpler and straightforward. Also, if you have a test data set, you can save that data locally. You could keep it in a file, maybe a small one so it can be included in your GitHub repository. You can use it as test data that stays there. Then, you can put that data in a volume directory using Docker, so it can access the test data. You don't have to actually copy it into the Docker container.