I'm not sure where to begin, but yes - it does take a special kind of idiot to believe that appointed judges can launch a coup to protect the elected president.
and why on earth is this on Hacker News? I guess even Jovem Pan is beginning to realize this whole movement is a clown show.
> it does take a special kind of idiot to believe that appointed judges can launch a coup to protect the elected president
What else do you call the massive censorship campaign that's been going on before, during and after the elections? They censored some pro-Bolsonaro videos without even looking at the content, this "fake news" stuff is pure bullshit. They clearly conspired to elect Lula and abused their powers to help him.
Actually I'll go even further. We are living under a judicial dictatorship right now. Censorship equals dictatorship, it's that simple. These judges are traitors who couldn't care less about the constitution.
> and why on earth is this on Hacker News?
Why wouldn't it be? Lots of people here are brazilians and have brazilian employees. What happens here matters. Lula has already signaled that he plans to regulate the software developer profession and that will have major implications for remote work.
> I guess even Jovem Pan is beginning to realize this whole movement is a clown show.
This "clown show" just turned into an official matter. Bolsonaro's party just submitted a formal request to dismiss the votes of the older, less thoroughly audited voting machines that mysteriously have no serial number. They can't censor it anymore.
When using a non database-based queue you'll have to find another mechanism to make sure your operation is still atomic.
In other words you can end up in a situation where a record is inserted but the job to work on it is not enqueued, or worse - that an insert fails but the job to work on it is enqueued.
Point 2 is still necessary despite idempotency imo: lets say some value is updated to "a" and then to "b", enqueuing two jobs. If the request to update "b" runs before "a" then your receiver will end up with the wrong value. Same if the initial request to update "a" fails.
It seems to me that XA transactions one of those patterns that need to be rediscovered every generation. I see folks start with 0mq or Redis and hit edge cases where messages get lost.
I'd love to see a somewhat simple distributed transaction standard for http api's emerge.
There has to be a middle ground between the fiddly bits of soap's ws-reliable or full on JMS broker and ad-hoc Redis queues.
Perhaps I wasn't clear. What I meant was that if you enqueue the job directly and the job is idempotent, using approach 2 will introduce dependencies like the ones you pointed out.
Most of the time migrations are developed in a feature branch, so the owner is responsible for splitting his branch into two or three before sending pull requests (as many as required to address issues with hot compatibility).
This means that we have two or more merges (and deploys) from master, each requiring a full run of the test suite.
I'm not sure where to begin, but yes - it does take a special kind of idiot to believe that appointed judges can launch a coup to protect the elected president.
and why on earth is this on Hacker News? I guess even Jovem Pan is beginning to realize this whole movement is a clown show.