Start with external services (Supabase, AWS, Firebase, Auth0, etc.) for early-stage.
Once you hit free limits, consider self-hosting.
1 VPS is enough for basics (e.g., lists), but for Kafka/WebSockets/big data/SLA/in-memory graphs cases, you'll probably need more than 1VPS.
@levelsio If your project needed WebSockets, real-time analytics (Kafka strms), high availability (SLA), and big data processing, 1 VPS wouldn't be enough. You use 1 VPS because your product is simpler, but that won't work for more complex needs. And yes: selfhost > cloud when costs matter
๐ Just wrapped up a custom feedback form for https://t.co/P4axySWziS! Took 3 hours, but totally worth it ๐ช. Why pay for fancy tools when you can build your own? #buildinpublic#SaaS
Excited to share that my scheduling app https://t.co/wuKijSEjGd, a free alternative to #Calendly, just hit 4x100 on Google PageSpeed! ๐๐ #WebPerformance#SaaS#WebDevelopment
When you choose UI library for your next #reactjs project, one thing that can help you with your choice is how many locales the library support. I picked #materialui because it had date components already translated to many languages #buildinpublic
If you're using @reactjs for your frontend and you need internationalization, I highly recommend Lingui.js - this lib has different approach and doesn't use key value vars, which makes your code easy to read and you don't need to come up with names for each text. #buildinpublic
I really recommend to use 'pseudoLocale' while doing translations of your side, that way you can easilly spot all missing translations, like "Country" text in attached example #indiehacker#buildinpublic
@levelsio@elonmusk Depends what the server is actually doing, if itโs just hosting some static landing page which is probably cached behind cloudflare then of course it can survive