What database knowledge is needed for a beginner back-end developer?

Question

SQL

In the process of learning backend development, I approached the study of databases. The topic is quite broad, something is within the competence of analysts, and DBAs specialize in something. Actually, what exactly does a back-end developer need to know from all the variety? Preferably in order of priority.

BTW I'm planning to look for a job on GO, so I'm already studying SQL, there's no question here, although now many people manage without it.

Answer 1

Judging by the completely dense questions that are asked on the toaster, the biggest problem for novice developers is the principle of operation of a relational database, the presentation of data in normal form, basic relationship options, and data atomicity.
I recently googled a book by Svyatoslav Kulikov, looked through it - it seems to be what you need.
https://svyatoslav.biz/relational_databases_book/
Secondly, you need to know the basics of optimization and indexing. Everything that is not related to setting up the server is the responsibility of the developer.
Well, basic SQL.
About "now many do without it" - this is bullshit.
Firstly, they "get by" only on beautiful pictures that have nothing to do with real life.
And secondly, when they "get by", they still keep the final SQL in their heads. If you do not understand what ORM will set up for you there, then it will be very painful.

Answer 2

Everything you can do with SQL you need to know. Study the joints thoroughly, you should understand well what is happening on them. You should also have a good understanding of transactions and isolation levels - this is an important topic.
First of all, it is not worth taking on the study of query optimization (this is meaningless without understanding the work of joins, indexes, partitions). Well, window functions are also not in the first place in terms of urgency, but it will be necessary to study.
Last but not least, triggers and stored procedures. The expediency of their use often gives rise to holivars. As for me, in moderate amounts of HP is normal.

Answer 3

-A little general knowledge about the database
-Knowledge and understanding of migrations (how to write, how to update, etc.) is a primitive but important point.
-Ability to write requests - the more difficult (if required!) And the better you can write a request, the better. It is thanks to the correct organization of queries that it is often possible to achieve a performance increase. SQL chips already get here. You can look in the direction of pl pgsql - a cool thing.
Yes, and in general, everything
. This is what I use at my current place of work, having settled down as a junior (also go). Over time, you will dig deeper, studying details, rather than breadth.
In general, a regular CRUD may be enough for a jun. It all depends on the job