Building sustainable microservices – our opinions and advice • Hacker News Board

Building sustainable microservices – our opinions and advice

#1

Post by zgryw » Wed, Nov 06, 2019, 5:53 PM UTC

Building sustainable microservices – our opinions and advice
building.echo.co.uk

Re: Building sustainable microservices – our opinions and advice

#2

Post by alexrbarlow » Wed, Nov 06, 2019, 6:29 PM UTC

Hi, I'm the Author of this. Feel free to ask any questions!

Re: Building sustainable microservices – our opinions and advice

#3

Post by dreur » Wed, Nov 06, 2019, 6:57 PM UTC

alexrbarlow wrote: post #2

Hi, I'm the Author of this. Feel free to ask any questions!

Thanks a lot for this post.

Could you expand on the techniques you use to implement idempotency in your workers/queues and in your rpcs?

I have seen a mix of doing nothing if there is nothing to do, locking, using a idempotency key and so on. But I am always curious to see what others do.

Re: Building sustainable microservices – our opinions and advice

#4

Post by alexrbarlow » Thu, Nov 07, 2019, 9:30 AM UTC

dreur wrote: post #3

alexrbarlow wrote: post #2

Hi, I'm the Author of this. Feel free to ask any questions!

Thanks a lot for this post. Could you expand on the techniques you use to implement idempotency in your workers/queues and in your rpcs? I have seen a mix of doing nothing if there is nothing to do, locking, using a idempotency key and so on. But I am always curious to see what others do.

Yeah, basically all of the above. We rely heavily on database row locking and then checking if it's already done. Sometimes you just don't need to check to (for example, just updating a timestamp)