This series of articles demystifies marketing myths and
jargon for software product design and MVPs.
Here is the summary:
Design is about creating things for
Our technology stack will not install and work on its own. People
will interact with it, but those who use it are the developers and not
users of the product.
As a stack architect, you must use the principles of design when
choosing and wiring the stack.
Making the right decisions
Although at the MVP (Minimum viable product) stage, there is a good
chance that you will eventually rewrite the parts of your technology stack
when you scale it. A well-designed stack will make the task more
Since each technology adds complexity to a project, in an MVP, we
must minimize as much as possible the number of technological
In addition, the choice between two technologies solving the same
problem will not only concern efficiency/performance, but also the extent
to which it is adopted by the developer. This means documentation and
enterprise availability, upgrade procedures, stability and simplicity of
the API (How your programmers use this technology).
We will then see how to choose the right stack in more detail by
dealing with the following topics: