ENGINEERING $1 a month ★ 155 upvotes 2018

How we built Hamiltix.net for less than $1 a month on AWS

Shared by @gregorymichael · Cloud & Mobile Era (2014–2019) · 75 community discussions

Read Original Article View HN Discussion (75 comments)

SYNTHESIS & DOSSIER

Retrospective Overview & Key Insights

Distilled analysis of the business dynamics, operational challenges, and strategic takeaways:

In this technical retrospective (2018), @gregorymichael shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.

Core Principles for Independent Builders:

Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.

Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.

Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.

Community Debate Themes:

HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.

PEER EVALUATIONS

Community Discussions & Critical Reviews

High-signal perspectives, counter-arguments, and peer founder insights debated on Hacker News (75 total discussions):

EV @everdev Peer Contributor

2018 Thread ↗

After the free-tier expires it will be less than $5, but the fact remains: it's crazy cheap.

I like the idea behind serverless development, but DO is $5/month and is easy to setup and maintain. From what I understand as your business grows AWS costs skyrocket and just starting out it's more complicated than a DO solution.

The idea is great, but looking forward to the day where serverless is the default solution because it's easier and cheaper. Not sure we're there yet.

OU @outworlder Peer Contributor

2018 Thread ↗

"Getting a push alert any time there is an error helps us respond to issues as soon as they come up. "

Oh god no.

Maybe if this system is not expected to ever grow in complexity. Otherwise this will become a big source of frustration really soon. And even if it does not, it's very easy to get a flood of non-actionable alerts for a transient condition.

It would be better to collect error rates and alert on that. Also the other golden signals.

PA @pards Peer Contributor

2018 Thread ↗

We also made the decision to not use a javascript framework for the front end, mostly because they are incredebly [sic] complex and some people suggest they are all terrible (or maybe great?).

Not to mention that for back-end developers, the learning curve is steep and ever-changing especially when one considers the "build" process. Is it grunt, or gulp these days, or webpack, or NPM, or some Frankenstein combination of all of them?

NZ @nzoschke Peer Contributor

2018 Thread ↗

Very nice. I built a boilerplate Lambda app that puts a lot of this cost effective architecture into practice:

https://github.com/nzoschke/gofaas

One difference is that I use SNS for cheap email or SMS error notifications.

YO @yorby Peer Contributor

2018 Thread ↗

You can get below $1/month if you use a cheap VPS [1] ...

1. http://www.lowendstock.com/

Read All 75 Hacker News Comments ↗

CATEGORY Frugal Engineering →

HISTORICAL ERA Cloud & Mobile Era (2014–2019)