I'm a junior dev, so I try to stick with things that have been proven to work without problems. This is why I think you can almost never go wrong with SQL. Some

I'm a junior dev, so I try to stick with things that have been proven to work without problems. This is why I think you can almost never go wrong with SQL. Some say that PostgreSQL is one of the most advanced ones and it's free. Others say and I can confirm, if your projects isn't huge give a try to SQLite. On the other hand there's this "new" trend with no-SQL approach, but the only proven thing I know about it is that there are people out there who made their career from saving other companies from troubles generated by young devs / CTOs / architects wanting let's say MongoDB very much, which occurred to be often a terrible choice. That makes me cautious. Don't ask me about details regarding that - I don't know. I have personal experience with MariaDB / MySQL and SQLite. A pleasant thing about both is that they are reliable and you are going to find a lot of resources (also help) online, which saved me some headache a couple of times. In more complicated projects I'll be using Postgres. I'll try to keep Mongo-ish stuff away until I'm going to have a very specific reason to use its advantages, which I don't fully understand at this point. Again, I like things I can rely on. SQL is one of them. PS: I'd be willing to know more what are you going to simulate @curiousgal. MC simulators are cool!