3 ms·
- I would suggest make a small app with just basic crud operations. It should have a front-end, backend and a database and then work incrementally to the other
by srawat1001 6y ago
- I would suggest make a small app with just basic crud operations. It should have a front-end, backend and a database and then work incrementally to the other steps mentioned below.
- Use k8s to deploy and run your app.
- Add more business logic where you will be needing more tools like elasticsearch, message-queues, etc.
Some examples from the top of my head are Stock Ticker app, Ticketing software like Zendesk, Food delivery App, etc.
Note: Start small, add one feature at a time.
- Silver3 6y agoWhat are the differences and pros and cons of a Database vs local storage? I'm thinking of creating a site where users can add there own urls and titles and this information should persist after the browser is closed, should I store these strings client side and tie it to there browsers local storage or tie it to some account on a database ran by me? Keep in mind there is no limit to the amount of strings a user could make and I predict there will be lots of users with at least 200 individual strings needing storage. Don't want to commit without being sure first.
- tomklein 6y agoIf you either want to do stuff like processing or analyzing it on the backend, or let users access their data from other devices, use a database. If not, use local storage. Local storage has the benefit of saving you bandwidth and storage cost, no matter how much your users save, and probably more privacy. Databases on the other hand, allow you to „do stuff“ with the data when the user is offline, share it through cross-device sessions and things like that. However the users can’t be sure what you are doing with it.
- Silver3 6y agoAight thanks for the reply will keep this in mind