Spring is generally more an enterprise solution, while I see Django being more startup oriented. Django is lightweight and fast (development time, not runtime!). Spring seems to have more focus on microservice architecture than django, if that matters to you at all. Starting your project in Django, it automatically creates a backend 'admin panel' for you to use and customize. You will not find this in the more serious Spring Boot.
I have experience in all three languages, and you should learn python first. These are three different languages (read: tools) to solve different problems you may have. Python is a high level language you can use for writing cross-platform scripts, web servers, AI, websites (e.g. Django) and the list goes on. Python can be used for most programming tasks while being the easiest to learn of the three and probably the most productive as well.
A lot of tech companies start out with Python for their web services, but due to Pythons slow speed and the pain that comes with dynamically typed languages when the code base grows, switch to Go later on when they need to scale. Go is a systems language that thrives when used for high performance cloud/web or networking services. Go is used in performance critical networking situations such as Twitch's streaming services and Uber's geofence services. It's also very clean and simple syntax that makes it very easy to quickly understand what code does.
Python is an interpreted language and Go is a garbage collected language, but Rust is a highly performant and reliable compiled programming language without the extra baggage of runtime memory management. Rust forces you to follow coding patterns that assure memory safety. This makes Rust a perfect fit for high performance algorithms, game engines or safety-critical systems, but would be overkill for web servers or scripts on modern hardware.
Good description on the languages. Though I'd recommend to start with Go instead as described in my recommendation.
Why go for a paid solution, when battle-tested Bootstrap is free? Bootstrap is easy to configure and customize, and is the most popular frontend library. Especially if this is going to be an in-house solution, I'd go for Bootstrap. Unless there are specific features you need that are only available in Kendo UI.
I have used Kendo UI in Html/JQuery and AngularJS, but not React. I have also used Bootstrap, and some other tools. In one applicaton we used both Kendo UI and an older version of Bootstrap. We used Bootstrap for its responsiveness and 12-column layout , and Kendo for all the UI. The product won an industry award for its UI. I think very highly of Kendo, due to 1) its many good examples, 2) its superior Grid (including nested rows), 3) the number of controls you get , including incredible graphs, 4) its attention to getting the details right, on even simple controls like single-select and multi-select Dropdowns. The cost of Kendo is recovered by all the time you save. Where I work now they are phasing out Bootstrap because they think FlexBox is better. Except that now I just saw that the latest Bootstrap uses FlexBox. Our QA was really big on automated UI testing, and they were able to that just fine with Kendo UI. Just make sure you give everything an ID.
I am going to build a backend which will serve my React site. It will need to interact with a PostgreSQL database where it will store and read users and create and use JSON Web Token for authenticating HTTP requests. I know EF core has good migration tooling, can Go provide the same or better? I am a one man team and I'll be hosting this either on Heroku or DigitalOcean.
From your question I gather that you don't have any specific requirements with regards to performance or technology: both PostgreSQL and JWT are well-supported in both ecosystems and so my recommendation would be to go with whatever you're most familiar with already which seems to be ASP.NET if I interpret the wording correctly.
Although there are very good frameworks and libraries for Go, you'll be looking forward to doing a lot of things manually. Although this can potentially lead to very optimized and high quality software, it can just as well slow you down because you're dealing with low-level stuff that doesn't actually add business value to your application.
The point in favour of Go would be that you can easily deploy it to Heroku, which (afaik) doesn't support ASP.NET.
As you're a one-man team, you might even want to reconsider the decision to have separate codebases and languages for back-end and front-end. You're going to need to be very focused on adding business value to your application without getting distracted by some low-level technical detail or context switch. With React being your chosen front-end technology, I'll throw Next.js in the ring. (It'll deploy on Heroku nicely, too).
In the end: choose the technology that will support your flow the most.
Thanks, next.js is my selection for the website / web panel! As you say, Go can be overkill for a one man team and I will be using nodejs with express js for most backend APIs. I also replaced Postges with MongoDB and I'm happy I did DX-wise.
I'm a dotnet developer, and recently enjoyed building cli apps in golang, it's been a fun experience. The main reason for me using golang will be its resource consumption, Small cross-platform executables. What I did notice though, building more complex applications, those benefits starts to erode quickly. And the latest articles about dotnet core single executables and AOT compile modes does suggest a much smaller footprint for dotnet apps going forward.
Either way, I like both languages
I built a boilerplate with hapi and typescript if you are interested :)
https://github.com/nomadovoip/hapi-typescript-boilerplate
Plan to introduce complete dev flow such as docker, compose, jest (already working with example), etc.
I don't understand your question. You are talking about creating a CRUD application in Node.js, where Mongoose is the ORM. And then you talk about if you make a REST API to perform CRUD operations instead? That does not make sense, at least in my head. First off; how is this going to be used? It's clear you want a CRUD application with MongoDB, but what are you going to use it for? Typically when we develop web systems we want a backend that takes care of storing data (database is Mongo in this case), a processing layer and the API layer. Then a frontend that speaks to the backend via the REST API, where the API layer calls functions in the processing layer which again uses the database layer. https://miro.medium.com/max/640/1*OC-wkRGzlV4NyhNeXYrTYw.png
