S
Sakura Data
Guest
Goal:
Have a common and same menu content link (for instance Home, about, consumer product, support) when you are using Angular, NativeScript and Android.
Background:
The menu contain seven different name. Each name is distinguish.
The backend is .net core with SQL server.
Problem:
Two approaches:
First solution:
Should the name from the menu should be located inside of backend? In order words, you retrieve the content of the menu from the backend and display in each UI (angular, android etc.)
Cons:
You use the concept DRY and less maintenance.
Second solution:
The second one is to have the content of the menu in each UI without request for the content of the menu at backend.
The main question is:
What experience have you been through in this situation.
Which of these two solution should I go and why?
Any pros and cons?
Thank you!
Continue reading...
Have a common and same menu content link (for instance Home, about, consumer product, support) when you are using Angular, NativeScript and Android.
Background:
The menu contain seven different name. Each name is distinguish.
The backend is .net core with SQL server.
Problem:
Two approaches:
First solution:
Should the name from the menu should be located inside of backend? In order words, you retrieve the content of the menu from the backend and display in each UI (angular, android etc.)
Cons:
You use the concept DRY and less maintenance.
Second solution:
The second one is to have the content of the menu in each UI without request for the content of the menu at backend.
The main question is:
What experience have you been through in this situation.
Which of these two solution should I go and why?
Any pros and cons?
Thank you!
Continue reading...