Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
isultan.bearblog.dev
Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
1–10 of 117 posts
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#2Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing.
These technologies are great for prototyping and building a v1 release to see if what you're trying to achieve is actually possible, but you will regret it later on.
The reason I know this, I work at a startup where we literally had the same backend stack and its been nothing but preformance issue after preformance issue. And it all needs to be replaced. We would have been better off building everything with go/rust in the first place. Or even java.
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#3This article doesn't really help me choose and based on the title I expected it would. I don't think OP made a "hype" driven decision, but this is certainly one of the most popular modern stacks and what I would like to see instead is a comparison between the popular and less popular options and why OP chose exactly this stack.
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#4Seems like this is lacking a lot of crucial stuff. What happens when you want to run a background job?
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#5(shameless plug) I wrote a (biased) article about choosing the tech stack for one of my side projects
https://learn.shortruby.com/blog/tech-stack
It is nothing fancy and I say it is biased because I started with what I know. But I tried to get into details about each choice.
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#6PocketBase + Go + HTMX
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#7Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing. These technologies are great for prototyping and building a v1 release to see i…
i don't agree at all. nodejs backends are as performant as you build them. the whole premise of node was async io, so if you're doing a bunch of blocking stuff then yeah, you're going to have issues. otherwise there's nothing innately non-performant about the platform.
it's impossible to debate more without going into details on your performance issues. typical backend architecture for any platform these days is the scalable container model, if you wanted scale-to-zero i wouldn't necessarily use node because of cold starts.
prisma can be great, can be slower than writing your own query, but that's the whole point of it. most of the time, it works and you can forget about queries and typings. when it doesn't, you can just eject to raw sql anytime you want.
i'm not a total nodejs fanboy, and have used more jvm (java/kotlin/scala) in my life, but if i was building a web-app today i'd absolutely consider node for all the reasons the author listed
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#8Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing. These technologies are great for prototyping and building a v1 release to see i…
Node.js backend performance is comparable to Java. Perhaps you had bad developers - trust me, if they screwed it up so bad they wouldn't be able to make your Java backend any faster, and probably couldn't get Go or Rust to work at all.
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#9To me this is a valuable write-up because it (a) clearly describes paper cuts accumulated when building with unfamiliar tech and (b) showcases how much nonsense developers are willing to tolerate in the name of "new" or maybe "speed".
Some of the paper cuts described include:
- Inexplicable interaction between the data layer and a hosting service's environment variable
- Migrations that don't work reliably
- Cron jobs that don't work reliably
- Inexplicable caching behavior for serverless functions, requiring an obtuse workaround
- An auth library that makes it hard to... get the ID of the logged-in user, apparently
I dunno, I suppose I'm happy to stick with boring old tech.
Re: Developing a Modern Full-Stack Application: Choosing the Right Tech Stack
#10Typescript (nodejs) backends are not performant, and your ultra modern stack is going to just cause you issues going forward if you need to scale. Prisma is really bad too, slow queries and no flexibility. If you ever need to do any sort of complex query you will just have to write sql anyway. And typescript is only sort of static typing. These technologies are great for prototyping and building a v1 release to see i…
This sounds weird to me. What kind of scale / traffic did you have? Must be incredible read write heavy with millions of users?
I'm saying this because i myself have, and lots i know, have launched production sites with 100s of thousands of users on ready-made stacks like, Laravel, Rails, Flask (Php, Ruby, Python). But it's my impression that these fall short on millions of users and enormous concurrent traffic, but then you're already at huge evaluation, years into your project, or have 200+ positions, ie. you've already refactored your project multiple times.