Dong Nguyen

I don't like Java so have no experience with Spring MVC. But there is a Spring team in my last company and I've found them to be quite effective on relatively complex projects.

For Python projects, I often play with Sanic and Starlette. I think that Django is not the best solution to develop REST API, as it's MVC framework, although it has a few good features, it is too cumbersome.

Most of the time I work with Node.js, and I have tried almost all the frameworks on this platform that I can find on Web Frameworks Benchmark . Express, Fastify, Koa, Restify are the reliable choices. However with me: Express is the norm, I have never had any problems while using it. The middlewares and its wide compatibility save significant development time.

A newer approach for fast development: the headless CMS live Directus, Strapi... Just setup them using docker, login and create the models, that's it. Your RESST API and even GraphQL API is ready to use!

Regarding security and robustness, no framework can help us. You can do it by yourself. My advice: keep your API simple as microservices without any security layer (except of data encryption if needed), then setup an API Gateway in front of them. You just need to protect your API Gateway.

I'm not sure how to use SQLite via web browser. If you mean Web SQL Database, it seems unsupported as well today. IMH, IndexedDB is the best choice. Theoretically its storage up to 50% of free disk space so you don't need to worry about the capacity. However working directly with IndexedDB is quite complicated and time consuming. So I like the wrappers at higher level such as localForage or JsStore, Dexie. Use localForage if you like simple key-value set/get syntax. Go with JsStore, Dexie if you need more complex queries. I'm also interesing with a new kind of database: the ones that sync automatically. A few names such as GUN or PouchDB. They are a combination of storage and socket IO. They may be suitable for applications that require a lot of real-time interaction.

For developer tech stack and roadmap, you can find some useful recommendations at https://roadmap.sh

Personally, I classify Angular into old style front-end framework. At client side, It's better to try more light weigth approach, the UI frameworks like React, Vue and Svelte. I recommend Svelte. In addition, you should take time on server side so that you can get overview of the entire system. WIth more server experience, you will understand backend team better.