Need advice about which tool to choose?Ask the StackShare community!
.NET vs Flask: What are the differences?
What is .NET? A free, cross-platform, open source developer platform for building many different types of applications. .NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.
What is Flask? a microframework for Python based on Werkzeug, Jinja 2 and good intentions. Flask is intended for getting started very quickly and was developed with best intentions in mind.
.NET and Flask are primarily classified as "Frameworks (Full Stack)" and "Microframeworks (Backend)" tools respectively.
"Tight integration with visual studio", "Stable code" and "Great community" are the key factors why developers consider .NET; whereas "Lightweight", "Python" and "Minimal" are the primary reasons why Flask is favored.
.NET and Flask are both open source tools. Flask with 44.8K GitHub stars and 12.6K forks on GitHub appears to be more popular than .NET with 11K GitHub stars and 2.37K GitHub forks.
According to the StackShare community, .NET has a broader approval, being mentioned in 1561 company stacks & 231 developers stacks; compared to Flask, which is listed in 502 company stacks and 509 developer stacks.
I have to write an application for a Windows Server that either runs on a scheduled task or can run on a Windows server and triggered by a webhook. What other .NET project types or methods within a project can I do this with?
I know I could probably host an API on IIS on the Windows server and do it that way, but all my APIs are in Azure App service, and this has to integrate with the Windows desktop application.
It all depends on your use case. You mentioning "scheduled task" appears you want to use a Worker Service
If you want to trigger your actions you can host a webapi, too.
Bottomline: Both use cases suffice your needs so your course depends on where you want to "control" your app ( set delay, maybe sometimes start the action manually ). WorkerService -> Config file on the host Api -> Configure from client

What you mean integrate on "all my APIs are in Azure App service and this has to integrate with Windows desktop application.". Try to explain a little bit what's your requirements.
If you want to Read/Write a SQL DB on premises, you can use a Azure Gateway without deploy anything in your server, another choice with SQL Server is to move the DB to Azure (if supported). You can use the triggers on Azure Functions to write/read something on Azure Storage, from your Server you can read the storage and perform some tasks. As you can see there are multiple choice without writing much code on premises, try to clarify your requirements.
My journey to developing REST APIs started with Flask Restful, and I've found it to be enough for the needs of my project back then. Now that I've started investing more time on personal projects, I've yet to decide if I should move to use Django for writing REST APIs. I often see job posts looking for Python+Django developers, but it's usually for full-stack developers. I'm primarily interested in Data Engineering, so most of my web projects are back end.
Should I continue with what I know (Flask) or move on to Django?

If you want to be a Web developer with knowledge in another frontend and NoSql technology, maybe continue with Flask. However, if you want to create very fast solutions to grow up with a new business and merge these with data analysis and other tools, Django is the answer. Basically read more about the service architecture where you feel more comfortable, Microservice or Monolithic, but please will not married with any because they solve issues to different contexts.
Which is the best Python framework for microservices?
We are using Nameko for building microservices in Python. The things we really like are dependency injection and the ease with which one can expose endpoints via RPC over RabbitMQ. We are planning to try a tool that helps us write polyglot microservices and nameko is not super compatible with it. Also, we are a bit worried about the not so good community support from nameko and looking for a python alternate to write microservices.
I have just started learning Python 3 weeks ago. I want to create a REST API using python. The API will be used to save form data in an Oracle database. The front end is using AngularJS 8 with Angular Material. In python, there are so many frameworks to develop REST APIs.
I am looking for some suggestions which REST framework to choose?
Here are some features I am looking for:
Easy integration and unit testing, like in Angular. We just want to run a command.
Code packaging, like in java maven project we can build and package. I am looking for something which I can push in as an artifact and deploy whole code as a package.
Support for swagger/ OpenAPI
Support for JSON Web Token
Support for test case coverage report
Framework can have features included or can be available by extension. Also, you can suggest a framework other than the ones I have mentioned.
For starters flask provides a beautiful and easy way to create REST APIs. Also its supported by excellent beginner docs as well as a very active community. Another good thing with Flask is its widely available list of plugins which allow you to build as you go. Its also good in performance and can scale to a quite decent level. However, if you are sure your project is going to be fairly big, it would be better to start with Django as it provides a lot of features out of the box and is extremely stable in performance. Both these frameworks have support for Swagger, JWT, Coverage Report although you have to install plugins for them. Deploying both of these are fairly simple and there is huge documentation available. Django has one of the best documentations I have come across. I hope I was able to answer your queries.
Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.
Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.
Pros of .NET
- Tight integration with visual studio271
- Stable code261
- Great community187
- Reliable and strongly typed server side language.181
- Microsoft140
- Fantastic documentation119
- Great 3rd party libraries89
- Speedy79
- Great azure integration71
- Great support63
- Linq33
- Highly productive33
- C#33
- High Performance30
- Great programming languages (C#, VB)28
- Open source24
- Powerful Web application framework (ASP.NET MVC)19
- Clean markup with razor16
- Fast16
- Powerful ORM (EntityFramework)15
- Dependency injection13
- Visual studio + Resharper = <310
- Constantly improving to keep up with new trends10
- High-Performance9
- Security8
- TFS8
- Integrated and Reliable7
- Huge ecosystem and communities7
- Job opportunities7
- Light-weight6
- Lovely6
- {get; set;}5
- Variations5
- Asynchrony5
- Concurrent4
- Entity framework4
- Support and SImplicity4
- Default Debuging tools4
- Useful IoC4
- Scaffolding4
- Blazor3
- Nuget package manager2
- F♯2
- F#2
Pros of Flask
- Lightweight319
- Python275
- Minimal217
- Open source149
- Documentation100
- Easy to use69
- Well designed55
- Easy to setup and get it going55
- Easy to develop and maintain applications51
- Easy to get started48
- Beautiful code22
- Rapid development19
- Powerful16
- Expressive15
- Customizable14
- Flexibilty14
- Simple to use14
- Love it13
- Get started quickly13
- Awesome13
- Speed12
- Perfect for small to large projects with superb docs.11
- Easy to integrate11
- For it flexibility10
- Productive9
- Flexibilty and easy to use9
- Flask8
- Not JS8
- User friendly7
- Secured6
- Unopinionated5
- Orm3
- Secure2
Sign up to add or upvote prosMake informed product decisions
Cons of .NET
- C#12
- Too expensive to deploy and maintain11
- Microsoft dependable systems7
- Microsoft itself7
- Hard learning curve4
- Tight integration with visual studio3
- Not have a full fledged visual studio for linux1
Cons of Flask
- Not JS10
- Context7
- Not fast5
- Don't has many module as in spring1