Re:How we built Hamiltix.net for less than $1 a month on AWS
by alex_duf on Friday March 02, 2018 @05:16AM
(#16500363)
yeah but to each stage of a project its solution. If that works at that scale why not?
Re:How we built Hamiltix.net for less than $1 a month on AWS
by lugg on Friday March 02, 2018 @07:25AM
(#16500903)
You know for people who live in an ever changing environment and are constantly editing our own reality - so much so that we need to track it in "source control" - developers are kind of funny how they get stuck on doing things "the right way."
Re:How we built Hamiltix.net for less than $1 a month on AWS
by BoorishBears on Friday March 02, 2018 @08:50AM
(#16501299)
Do they really get stuck on doing things "the right way",
or do they get stuck on making off-the-cuff remarks about doing things "the right way" for easy karma?
Re:How we built Hamiltix.net for less than $1 a month on AWS
by zimbatm on Friday March 02, 2018 @06:49AM
(#16500747)
Or better yet, forward the errors to https://sentry.io/ and let them deal with error grouping.
Re:How we built Hamiltix.net for less than $1 a month on AWS
by badsectorlabs on Friday March 02, 2018 @11:37AM
(#16503025)
A valid concern. However even after reddit and hacker news has had their way with the site, my phone has been impressively quiet. These push notifications are only for cases where the lambda functions thrown an error that isn't handled anywhere else (i.e. something is very wrong).
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.