21–30 of 74 posts
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.
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.
Disclaimer: I work for AWS in Professional Services. I specialize in “application modernization”. Basically that means a focus on serverless technology. That being said, if someone who doesn’t know “cloud” and has a deadline just to get something done like the author asked for advice, even I would suggest they just throw a monolith on a VM. If they really wanted the optionality to go all in on AWS later, I would sugg…
Hetzner has very performant, spacious servers for cheap. Provisioning time is usually less than 2 hours. In my experience using their servers over the last 5 years, they are reliable. And since he's using Docker and CI/CD, he can probably easily move to a new physical server if his died.
Hetzner does offer VPS as well, but you pay more for the provisioning speed and the usage-based billing (assuming you run it 24/7). Plus they have much less space and performance compared to the physical servers.
Earlier quoted context omitted.
Disclaimer: I work for AWS in Professional Services. I specialize in “application modernization”. Basically that means a focus on serverless technology. That being said, if someone who doesn’t know “cloud” and has a deadline just to get something done like the author asked for advice, even I would suggest they just throw a monolith on a VM. If they really wanted the optionality to go all in on AWS later, I would sugg…
I don't think he used a VPS; I think he just has a bare metal server (Linux). Hetzner has very performant, spacious servers for cheap. Provisioning time is usually less than 2 hours. In my experience using their servers over the last 5 years, they are reliable. And since he's using Docker and CI/CD, he can probably easily move to a new physical server if his died. Hetzner does offer VPS as well, but you pay more for…
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.
Earlier quoted context omitted.
> 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.
React and Docker are both almost a decade old (both released in 2013). TypeScript is from 2012. Functional programming is very, very far from being a modern concept even if it's (maybe, finally?) getting a bit more attention.
I’m in the same boat as previous commenter - React et al feels like new tech to me.
But that’s because I’m an old fart who’s been using php for over 20 years.
Earlier quoted context omitted.
> 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.
React and Docker are both almost a decade old (both released in 2013). TypeScript is from 2012. Functional programming is very, very far from being a modern concept even if it's (maybe, finally?) getting a bit more attention.
My point is that what often gets criticised as "new tech" is actually quite old. Hence the stupidity of that argument.
I write in Go, use protocol buffers to define the api but will handle it via http(manual routing, not grpc gateway), event sourcing for the domain entities, db will by good old mariadb(i never found postgres interesting with its "exotic" types and lack of ui tools), front-end will be written in quasar which i will also use for mobile app(my first).
a lot of things can be done very easily and cheaply if one has the skill and time.
I applaude you for keeping things simple, not over-engineering, and resisting the urge to use the latest tech.
Earlier quoted context omitted.
One advantage of using docker for everything is reproducibility. Your dev and prod environmentsncan be almost identical.
Is it really that much easier than just installing the same version of Postgres and running SQL queries to create the schema/seed the data? You’re not going to be using the same data in production and dev.
Earlier quoted context omitted.
I would never choose a Google specific cross platform environment. A cross platform mobile environment constantly needs updating to stay consistent with the vendor’s platform. I wouldn’t trust Google to give that much attention to Flutter especially seeing they are moving away from it internally for iOS development. https://9to5google.com/2021/10/10/google-ios-apps-native/
So .. what would you use?