---
title: "Lê Công Tuấn (@tuanlc) | Hashnode"
description: "Software Engineer. Read the latest articles by Lê Công Tuấn on Hashnode."
url: "https://hashnode.com/@tuanlc"
---

@tuanlc

# Lê Công Tuấn

@tuanlc · Hanoi, Vietnam · Joined November 2021

Software Engineer

## Comments

[Nice article! Thank Mariusz Michałowski!](https://hashnode.com/posts/iam-roles-gcp-vs-aws/649849a55824b660173f4d4d/comment/64abb114a25b1020144642c3#reply-64abb3ea395b682e51ab8a01)

Reply · Article · Jul 10, 2023 · [IAM Roles - GCP vs AWS](https://hashnode.com/posts/iam-roles-gcp-vs-aws/649849a55824b660173f4d4d)

[Thanks for the article, it will save me a lot of time next week! 😅 I have some concerns. 1/ For the createProcessTicker method: try { for (const record of records) { await processRecord(record); await cursorRepo.setPosition(record.id); processedRecords++; } } catch (error) { logger.error('Could not process record', { processName, record, error, }); } finally { await cursorRepo.unlockCursor(); } Should error be forwarded in the catch block? Otherwise, the cursor process won't terminate if failed to process a record. 2/ For this termination flow } catch (error) { logger.critical('Terminating server: cursor process error', { processName: props.processName, error, }); // we use structured logging await lifecycle.close(); process.exit(1); } When a node is terminated and the cursor lock is released, will the terminated process propagate to the remaining nodes? I guess, there will be the scenario that container managers (CR, K8S) keep initialize new nodes to replace terminated nodes until the error is fixed.](https://hashnode.com/posts/implementing-the-outbox-pattern-in-nodejs-and-postgres/6444f865abf1eca215f1b508/comment/64450d67994f853a1efec769)

Comment · Article · Apr 23, 2023 · [Implementing the Outbox Pattern in Nodejs and Postgres](https://hashnode.com/posts/implementing-the-outbox-pattern-in-nodejs-and-postgres/6444f865abf1eca215f1b508)
