Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Most people attempt to achieve Idempotence whenever possible, and there are several reasons this is desirable in HA systems. Fundamentally, the REST paradigm broke peoples brains, and set many projects on a doomed trajectory into the sun.

That being said, for some types of problems a high-latency finite state machine greatly simplifies the complexity of handling data stream consolidation efficiently. The trick is knowing when it should be avoided like in shared-state awareness problems... you know, the "lets pause the internet while I do this one op" guy we all work with sometimes... =)



> Most people attempt to achieve Idempotence whenever possible, and there are several reasons this is desirable in HA systems. Fundamentally, the REST paradigm broke peoples brains, and set many projects on a doomed trajectory into the sun.

Respectfully… wha?


If you have under 40k users, than you can get away with a lot of bad choices. =)


Sure, I’m just trying to understand the thing you previously said.


I would recommend David Schmitz's talk: https://www.youtube.com/watch?v=GWgRw5jiYy0

While I don't agree with many of his points (riffs on Erlang/Elixir are silly), there is still some good hints in the talk.

Hope it helps =)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: