This series of articles demystifies marketing myths and
jargon for software product design and MVPs.
Here is the summary:
People will use the term “Back-end” to talk about servers. That's where
all the hidden logic comes in.
The server is like the "Maestro" of your digital product. He
communicates with all parties in the Stack and coordinates their work. He
is also responsible for communication with the client (browser, mobile
device, IoT device, etc.) who presents the user interface.
The server is also responsible for contacting third party services.
For example, talking with payment gateways, querying twitter
A little bit of technique
In reality, the back-end is one or more programs working together to
fulfill their role as a "maestro".
There are two ways to conceive the back-end: either in a single
large program managing all tasks, called monolithic
architecture. Or, in a bunch of small specialized programs,
called micro-service architecture.
Again, there is no one-size-fits-all solution. It all depends on the
context of the project. Nevertheless, since we are building an MVP and we
need to focus on the rapid approach, I personally agree with the MonolithFirst approach, as Martin Fowler
Now that you have an idea of the back-end role, you understand the
need for versatile developers as back-end developers. They will need to
have experience with the particular technologies you have chosen, but also
the ability to adapt to Stack's changes.