isidor
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
i believe it was from searching for saas starters yes
34 replies
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
it is, it is also kinda boring 😄
Kidding aside, we will not switch to TS for our main projects:
we just wanted to find a fun alternative for smaller scale projects that also ticks the boxes of enterprise requirements
TBH the closest equivalent to our current ecosystem is nestjs but it looks like java with extra steps 😄
so yeah, long answer short, we wanted a fun, faster but also professional alternative for smaller scale projects (that should have the ability to grow though).
also we are FP enthusiasts so your Haskell backend caught our attention 😄
34 replies
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
spring boot (java) with heavy vavr usage (might recognise the library being a FP gang) 😄
34 replies
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
Thank you again @sodic @martinsos for giving your time to discuss our concerns!
IMHO you have managed to perfectly market wasp to MVP builders, so it makes perfect sense to try doing the same for other types of products/devs (e.g. enterprise).
I think adding additional details for the “Production / Scaling” part of the docs would indeed be the best choice since you can pretty much explain what I was told here, that basically people have nothing to fear because at the end of the day they can use the same tools they could use directly from the JS ecosystem for scaling or tackling similar concerns (even if you don’t have internal solutions for that at this point).
In general, in these docs I would want to be reassured through that production section that Im “buying” into a framework(lang?) that takes care (or at least does not stop me from doing it) of security, scalability, maintainability since Im already sold on ease of use, speed and efficiency.
Actually that would solve a major issue of choosing to develop (backend) in the JS ecosystem in general not just wasp hehe 😄
34 replies
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
awesome, thank you very much for taking the time to write this detailed answer!
That makes sense, that's what we expected and it explains my previous question about ejecting /using the build version as we see fit - I hope that this will not change in the future! 🙂 On the other hand I would greatly appreciate blog posts/information on the architecture of the generated code.
In any case my main concern is covered, we wanted to make sure that wasp was not just a beginner friendly "vendor" lockin which seems to NOT be the case. Building on this it would be beneficial for this information to be transparent to help developers who DO want to fast track their development but also do have scaling concerns. This is to make sure that wasp does not appear just as a quick way to MVP but as a quick way to bootstrap enterprise quality webapps
again, thank you for your time!
34 replies
WWasp-lang
•Created by isidor on 8/26/2024 in #🙋questions
Scaling
Hi @sodic thank you for answering! Hypothetical!
At this point we are just evaluating wasp for our current and future needs
During the last 20 years of building we 've seen all of the above problems haha and surely it is not a xy problem 🙂
The question we are trying to answer is whether it makes sense for us to build new products with wasp
and for that we need to know if we can handle scaling without ejecting the app or trying to "fight" against it.
Right now from what we have seen it makes sense to keep very specific business logic in wasp and use other microservices for things that need to scale but maybe I m wrong
34 replies