Product = bridging customer value with the code that delivers it

Your job is to understand what customer value is worth delivering and think of the best way to deliver it with code. Delivering the code start with thinking the code i.e. the Frontend, Backend, and Database as a complete consistent and simple product that works.

This involve a lot of structuring decision for the company to be able to deliver the value in the best timing.

This is why it requires to design these layers together in a way both the Business and Engineering understand and commit on it.

Table of contents

Understanding the system - the dining, the kitchen and the storage room

The typical mistake in product building: the gap between Business and Tech

The missing recipe in Tech: the system functional specifications

The design process of a product - it starts from the customer value definition and builds it from the storage

Understanding complexity

Understanding what is system design - the dining, the kitchen and the storage room

Frontend, the interaction layer as "The dining area"

The frontend is what you see, touch, and interact with. The menu, the decor, the service. It's all about user experience.

Frontend is what you interact with.

Backend, the applicative layer as "The kitchen"

Backend is the kitchen — where all the orders (requests) are received, processed, and sent back as delicious dishes (responses).

Backend is the cooking logic executed in the kitchen. This is the business logic in the background.

It often refers to the elements the user doesn't see (intermediate states, computations happening, etc.).

Backend is how things really work to deliver the interaction.

Database, the storage layer as "The storage room for ingredients and recipes”

Database is the storage: the storage room where all the ingredients (data) are kept, and the recipe books where all the best practices to deliver the dishes are stored.

The kitchen (backend) accesses all the ingredients and recipes to run the actual cooking logic.

It often refers to the elements the user doesn't see, in a kitchen the intermediate dishes states, the gestures, the cooking time, the assembly, in an application the intermediate states, computations happening, etc …

The backend accesses this storage to serve the right data to the frontend.

Together, they form a complete system — just like how a good restaurant relies on all three: dining area (frontend), kitchen (backend), and storage room (database) to run smoothly!

https://www.linkedin.com/posts/ramya--kadiyala_ever-wondered-what-frontend-backend-and-activity-7335515925988724736-8-bD/

The typical mistake in product building: the gap between Business and Tech