Hello, my dear, today we will dive deeper into the abyss of ORM configuration.
We will add one more resource, set a relationship between this one and the one we already had after this post and will cover some useful tuning options. Spoiler: we will even change a bit the old one. So, fasten your seatbelts, let’s start!
Hello friends, please sit down and have a cup of tea, today we’re going to talk about ArangoDB. It is a database. Have you ever heard of it? I had not, until yesterday. But I came across a brilliant article from this database developers. Let me tell a few words about the database itself and about their article.
After the previous post, our application server works, can receive requests and even return some kind of responses, which is already great and you can go into production with it! But probably it would make sense to add some more functionality to it. And in this post, we will integrate a database and implement a RESTful API.
A few days ago I read Joe Nelson’s post about DB’s transactions anomalies and Postgres’s isolation levels to prevent them.
I found it very useful and descriptive, so I decided to make a short summary of the information he showed there for those who tl;dr.