---
title: "Ikem Ada (@Violacordis) | Hashnode"
description: "Software Engineer. Read the latest articles by Ikem Ada on Hashnode."
url: "https://hashnode.com/@Violacordis"
---

@Violacordis

# Ikem Ada

@Violacordis · Nigeria · Joined May 2022

Software Engineer

### [Message Queues: Why Your API Should Not Wait for Everything to Finish](https://violacordis.hashnode.dev/message-queues-why-your-api-should-not-wait-for-everything-to-finish?utm_source=hashnode&utm_medium=feed)

Picture a bulk payment endpoint that processes a batch upload of employee salaries. For every row in the file, it debits the company account, credits the employee, sends a payslip email, and writes a

6 min read · [violacordis.hashnode.dev](https://violacordis.hashnode.dev/message-queues-why-your-api-should-not-wait-for-everything-to-finish?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/message-queues-why-your-api-should-not-wait-for-everything-to-finish/6abf8b5fe0ba5c0fbedba9f1)

### [Idempotency: Why Tapping Send Twice Should Never Charge You Twice](https://violacordis.hashnode.dev/idempotency-why-tapping-send-twice-should-never-charge-you-twice?utm_source=hashnode&utm_medium=feed)

Chidi owes his friend ₦15,000 for his share of a restaurant bill. He opens his banking app, types in the amount, taps Send, and the screen hangs on a spinner. He waits. Nothing happens, and he cannot

6 min read · [violacordis.hashnode.dev](https://violacordis.hashnode.dev/idempotency-why-tapping-send-twice-should-never-charge-you-twice?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b) [Oct 1](https://hashnode.com/posts/idempotency-why-tapping-send-twice-should-never-charge-you-twice/6abe5a890d256d529e82760b)

### [AI Made Your Team Faster. It Also Made Your Mistakes Permanent.](https://violacordis.hashnode.dev/ai-made-your-team-faster-it-also-made-your-mistakes-permanent?utm_source=hashnode&utm_medium=feed)

Building software used to be slow enough to make you think. That's not a complaint. The friction was a feature. Before your team committed to anything, they had to justify it, refine it, and argue abo

5 min read · [violacordis.hashnode.dev](https://violacordis.hashnode.dev/ai-made-your-team-faster-it-also-made-your-mistakes-permanent?utm_source=hashnode&utm_medium=feed)

[Aug 26](https://hashnode.com/posts/ai-made-your-team-faster-it-also-made-your-mistakes-permanent/6a8f5503c5e473ad36447bcc)

### [Introduction to Computer Networks](https://violacordis.hashnode.dev/introduction-to-computer-networks?utm_source=hashnode&utm_medium=feed)

How Digital Communication Really Works

8 min read · [violacordis.hashnode.dev](https://violacordis.hashnode.dev/introduction-to-computer-networks?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/introduction-to-computer-networks/6a031369937b84f7796fdfd9) [May 12](https://hashnode.com/posts/introduction-to-computer-networks/6a031369937b84f7796fdfd9)

### [Inside the Query Optimizer: How Databases choose and Evaluate Query Plans](https://violacordis.hashnode.dev/inside-the-query-optimizer-how-databases-choose-and-evaluate-query-plans?utm_source=hashnode&utm_medium=feed)

You write a query. The database runs it. You get your result. Simple, right? Not quite. Before your query ever runs, the database is already making decisions behind the scenes. It evaluates different

7 min read · [violacordis.hashnode.dev](https://violacordis.hashnode.dev/inside-the-query-optimizer-how-databases-choose-and-evaluate-query-plans?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/inside-the-query-optimizer-how-databases-choose-and-evaluate-query-plans/69f9d77da386d7f1217d7039) [May 5](https://hashnode.com/posts/inside-the-query-optimizer-how-databases-choose-and-evaluate-query-plans/69f9d77da386d7f1217d7039)
