NoSQL isn't immediately useful

Non-relational databases (NoSQL) differ from the tables and relationships we are used to in one simple way - they don't exist! Storage is done manually, i.e. intuitively, as we would like.

I really like this type of DB because it's easy to store, hard to process. But it's fun!
The most wonderful example (I haven't invented it myself yet, but I think it's a matter of time) of existing non-relational databases is GraphQL. Please love and favor it.

type User {
  fullName: String
  nickname: String
  name: String @deprecated(reason: "Use `fullName`.")
}

The description of structures is similar to Swagger, if you have worked with it. When writing an API, we usually use the name of the structure and its description in curly brackets {}.

A simple graph structure allows the use of vertices as storage points and edges as connections of specific data. A simple graph structure allows the use of vertices as storage points and edges as connections of specific data.

All abstract mathematical constructions are applied when you go beyond the classical software (e.g., spreadsheets) and start your own path. It is incredibly interesting and I wish it for everyone!

type Person {
  name: String!
  appearsIn: [Episode!]!
}

Objects can have any number of variables and characteristics, this affects the type of data stored and how it is processed later.

I have a series of articles devoted to the Hamiltonian path and working with graph traversal, where you can find algorithms and methods for working with abstract form.

type Query {
  droid(id: ID!): Droid
}

Database queries are written in a similar simple way, specifying arguments (ID in our case). The specifics of working with graphs will only come in handy here for complex queries; GraphQL encapsulates the internal structure for you.