Technology Choices for My SaaS in Retrospect

#1

Post by Fudgel » Sat, Sep 24, 2022, 12:05 AM UTC

Technology Choices for My SaaS in Retrospect
thomasbandt.com

Re: Technology Choices for My SaaS in Retrospect

#2

Post by mooreds » Sat, Sep 24, 2022, 12:10 AM UTC

Always fun to read reports from real life tech decisions. Hope you do a follow up in a year and share what you've learned then.

Re: Technology Choices for My SaaS in Retrospect

#3

Post by schemescape » Sat, Sep 24, 2022, 12:44 AM UTC

Looks like he’s storing data in the server’s file system, but I see no mention of backups. Hopefully there’s more than one copy of the data somewhere (or it’s not critical data)!

Re: Technology Choices for My SaaS in Retrospect

#4

Post by human » Sat, Sep 24, 2022, 1:13 AM UTC

I applaude you for keeping things simple, not over-engineering, and resisting the urge to use the latest tech.

Re: Technology Choices for My SaaS in Retrospect

#5

Post by davnn » Sat, Sep 24, 2022, 1:41 AM UTC

Old-school monolith architecture with not-so-boring technology. I went the same path for a project, but in hindsight I would chose popular, well maintained, not necessarily boring, technology and a cloud architecture for most use cases I can think of.

Re: Technology Choices for My SaaS in Retrospect

#6

Post by personjerry » Sat, Sep 24, 2022, 2:19 AM UTC

Speaking of marketing, he probably could've plugged his product at some point in that article and leveraged the inbound traffic

Re: Technology Choices for My SaaS in Retrospect

#7

Post by threeseed » Sat, Sep 24, 2022, 2:45 AM UTC

human wrote: post #4

I applaude you for keeping things simple, not over-engineering, and resisting the urge to use the latest tech.

> resisting the urge to use the latest tech

They are using React, Tailwind, Typescript, Docker, FP etc. which is what you would find in many modern tech stacks.

That's what I love about this "we should only use old tech" argument. There is no specifics, justification or technical basis for any of it.

So you end up wondering how old should my choices be in order to satisfy the crowd.

Re: Technology Choices for My SaaS in Retrospect

#8

Post by threeseed » Sat, Sep 24, 2022, 2:47 AM UTC

schemescape wrote: post #3

Looks like he’s storing data in the server’s file system, but I see no mention of backups. Hopefully there’s more than one copy of the data somewhere (or it’s not critical data)!

Also the problem everyone makes with backups is that they don't regularly test them.

At which point storing the files on S3 would have been far easier, quicker and safer.

Re: Technology Choices for My SaaS in Retrospect

#9

Post by leetrout » Sat, Sep 24, 2022, 3:03 AM UTC

personjerry wrote: post #6

Speaking of marketing, he probably could've plugged his product at some point in that article and leveraged the inbound traffic

Seemed like he was scared to share the idea.

Re: Technology Choices for My SaaS in Retrospect

#10

Post by ofrzeta » Sat, Sep 24, 2022, 3:53 AM UTC

I'd say this is quite biased, which is fine I guess, we all have our biases. Seems his choice of F# is set in stone, so you either go with Bolero or you have 1+1 languages in your stack.

This is also reflected in his choice of Xamarin: he "doesn't like" Dart as a language, so he's forced to choose "dotnet MAUI as a platform [which] might not be as mature and capable as Flutter even today". Flutter as well "suffers from many bugs and problems". Is Flutter really that buggy?