Soltuion space not problem space 


What and why 

Why we need to build the solutiion ?
→ building real time chat app with quarks and event streaming can streamline the process here 

What problem does it solve?
→ we need to check if we need to migrate a node js backend api into spring boot java code and later 



We need to build a sematic search search bar in out website (e-commerce , retails , icons) 
→ to improve the reseach exeprience of the app
Software development classics suggest the idea of functional and nonfunctional requirements. Shortly: functional requirements are about the functionality of a new feature or system, its value and user flow, while nonfunctional requirements are about aspects like performance, security, portability, and so on. In other words, functional requirements determine what we should design, and non-functional requirements shape the understanding of how it should work under the hood. So, when we talk about potential risks and limitations, we effectively gather non-functional requirements. 

*****************************

Now we are going to touch on the solution space, the next important step on the way to creating a design document for your system. Together with the previous chapter, this part of the book will prepare us to start with the actual system design. There are several key aspects of your preparation that we will cover in the next 10–12 pages of text. These include choosing between building from scratch and finding a ready-made solution on the market, finding existing use cases that would fit your problem and give you valuable insights, and understanding what level of innovation you need.

What problems can inspire you?

Let’s summarize this case based on the information above: The problem is based on face recognition. Thus, as a system designer, you need to familiarize yourself with the domain. The solution should be mobile-first. Thus, knowledge about machine learning on mobile devices is crucial. The solution should be resistant to fraud attempts (a dishonest driver can try to show a photo of a legitimate driver instead of their own face). Thus, experience in liveness detection will be useful.




→ Business/product aspect 
Solutions with similar business problme and goals 
We have a same app “todlist” 
We user can : 
Create a task 
Delete a task 
Modify a task
→ Technical aspect 
Solutions with similar solutions with matching technical requirement 
We have a youtube video with similar poject 
The same ui (react )
But here instead of node js we need to migrate to spring boot java code oky 
***************
Here we start by geting famillar with the backend solution with node js 
The project folder structure and dependencies

*****
The project folder strutre 
Backend 
Frontend 

*** 
For the backend 
This structure 
The folder structure displayed in the image is as follows:

- **configs**
  - `keys.js`
  - `prod.js`
  
- **demo**
  - `demo.gif`
  
- **models**
  - `todo.js`
  
- **routes**
  - `todos.js`
  
- `.gitignore`
- `LICENSE`
- `README.md`
- `app.js`
- `package-lock.json`
- `package.json`

This structure suggests that it is likely part of a Node.js project. The main components include configurations, routes, models, and the necessary files for package management (`package.json`, `package-lock.json`), as well as the main application file (`app.js`).

Q- my first question given i want to migrate to spring boot backend i want you to give me the folder strutre here