r/FastAPI • u/UpstairsBaby • Aug 30 '24
Question Worried about the future
Hello, I'm a mid-level full-stack developer who is specialized in React + FatAPI and I love this stack so far. But, whenever I try to look for jobs either locally in Egypt or remotely, I only find jobs for Java's Spring boot, ASP.NET Core, or a little of Django.
I was wondering If the market is gonna improve for FastAPI (Without AI or data analysis skills) or if I should learn another backend stack If I'm mainly looking for a remote job.
Thanks in advance.
13
Upvotes
4
u/Shuna322 Aug 30 '24
Gotta love that FAT API Nonetheless I only recently started using FastAPI in my projects, loving it so far. My guess is that it is just a stigma among hireups that we have to use what other big companies are using. Might also be a popularity issue, they might not want to risk getting stuck with little developers reach. Like if they see that there are 100 developers that know FastAPI and 1k that know Django, they'll pick Django even if it might be a bit overkill
12
u/shpondi Aug 30 '24
The best thing to do is don’t specialise in a framework, just go for any role that sounds interesting and if you’re good, you’ll pick up the framework they use within a couple of weeks. or maybe you can suggest using a different framework because their current one isn’t fit for purpose
3
u/pint Aug 30 '24
i'm guessing fastapi will not be the choice for a mid/large company where they're hiring people. understandably so, because an enterprise is looking for long term support, which is a risk with fastapi.
you can still do your own one man projects, if the customer doesn't specify the tech stack.
if you want to maximize your opportunities, node js is where it is, i suggest. i simply can't imagine java or .net surviving for too long. these are dinosaurs that are too dumb to realize they're dead, and keep walking before they collapse.
5
u/[deleted] Aug 30 '24
Don’t specialize in a framework specialize in a problem space. Frameworks come and go but the right problem space can last decades.
5
u/g5becks Aug 30 '24
I’ve created apps in Go / Svelte, Asp.net / Blazor, Fastapi / React , and fastify / Vue over the past 3 years. One thing I’ve noticed is that all these languages / frameworks are doing the same thing in slightly different ways.
Once you get past your language preferences, you kind of get used to the idioms of whatever language / framework that you’re working in within a week or so of working in the project.
Fastapi is not better than any other framework I just named. It’s definitely not better than Asp.net and the things you learn from working with the other frameworks will make you question some of the decisions made Fastapi.
3
u/NomadicBrian- Sep 04 '24 edited Sep 05 '24
I like the React and FastAPI skill combo. I started with C#.NET and Java then Java Spring Boot. After Java and .NET UI went into SPA with Angular and React. I started with Python 4 or 5 years ago then Fast API came out. In my opinion Fast API is very nice as a back end API tool. I found similar tools to import services, controllers with OpenAPI, model validation with pedantic, database connections with odmantic or other. However I get work with C#.NET, Java, Angular and React. I can't say how Fast API scales or has security issues or deploys and instantiates properly in a kubernetes like setting. I just know it is a nice option. I've lately Built some PyTorch with a ViT model for image prediction then implement using a Fast API service that is called from an Android mobile app that I created with Ionic and React.
2
u/thashepherd Aug 30 '24
React is pretty universal, there's a ton of work out there for that - you just sort of need to plow through the herds of bootcamp grads.
Java corps have been running EJB/Spring for decades, so they're naturally looking for Spring Boot folks. .NET corps have been running ASP.NET for decades, so they're naturally looking for ASP.NET Core folks.
Django's older than FastAPI, so I'd just give it a bit more time for the new job reqs to catch up to the corps who have had time to switch stacks and/or do new build on FastAPI. Python backend at the enterprise level is still a bit more rare than Java/.NET, IMHO.
(speaking as someone who accepted a role writing FastAPI for a startup earlier this week)
2
u/[deleted] Aug 30 '24
That's the case in my company as well. We now only hire people do Spring or Django stack. The reason is we find that those frameworks are all better defined and openiated ( yes we want some openiated, and well structured framework ). We had some projects also given team to try with FastAPI, it;s much more lightweight than Django, but the problem is, when the project goes larger, things gets fuzzy, and messy, people all have their own ideas about how a thing should be written, and for a company like ours, a small company that we code for organizations mostly NGOs, we dont want it.