6:40 AM
List of dishes available in the restaurant including info such as price, review, name, ingredient
Account for customer including list of to-go order he made in the last month with discount after certain times he or she purchase orders certain number of times.
Storage of search info from customer looking for dishes.
Account for employees including details such as amount of salary payment received, schedule for next week. Account admin should be total number of revenue, cash flow, cost, plus the customer search data to identify current customer appetite trend.
Account for customer including list of to-go order he made in the last month with discount after certain times he or she purchase orders certain number of times.
Storage of search info from customer looking for dishes.
Account for employees including details such as amount of salary payment received, schedule for next week. Account admin should be total number of revenue, cash flow, cost, plus the customer search data to identify current customer appetite trend.
5 hours later…
12:07 PM
@kungho Really, any tech stack would work. What you've written sounds reasonable. However, I notice that you're focusing entirely on the backend. How will you do the frontend? Classic web application where a HTML page is generated on backend and sent to browser? Or some JavaScript framework like React? Personally, I like to keep it simple and to add small elements of interactivity e.g. with VueJS or vanilla JavaScript.
For Search, you do not need Elasticsearch or other special services. Postgres has a full text search extension that will already cover most search needs, though it's more “acceptable” than “very good”. See this tutorial.
3 hours later…
« first day (3834 days earlier) ← previous day next day → last day (1148 days later) »
Transcript for
Mar2
Mar '213
Mar4
The Whiteboard
General Discussion for softwareengineering.stackexchange.com P...