Tony C. Batista

[Tony C. Batista @tony_tcb]

@Krishnasagrawal FREE

[Tony C. Batista @tony_tcb]

@PrajwalTomar_ claude

[Tony C. Batista @tony_tcb]

@systemdesignone system design

[tsu.node ➔ tsunode.com @tsu_node]

Nova landing page em 1, 2, 3...conferem o vídeo e depois nossa página também.

Aqui não tem tempo ruim, deploy feito 🫡

[Raul Junco @RaulJuncoV]

After reading a dozen articles, I still had questions.

That's why I created this manual.

Event Bus vs Message Queue vs Message Broker.

Event Bus

Designed for publishing events to many subscribers, Publish-Subscribe (Pub-Sub), One-to-many.

The publishers and subscribers don't need to know about each other. High level of decoupling!

Generally, the systems consume messages as they arrive instead of storing them.

Does not guarantee delivery.

When to use it:

- Real-time notifications across many subscribers

- Situations where many services need to react to specific events

Examples:

Inventory System: Notify other services when a product is out of stock.

Monitoring Systems: Alert other departments when the system exceeds a certain threshold.

Message Queue

Designed to hold messages until a consumer service can process them.

Use Point-to-Point or Producer-Consumer communication model. One-to-One.

The sender delivers the message and waits for an acknowledgment.

When to use it:

- Decoupling producer and consumer services

- Asynchronous processing of tasks

Examples:

Order Processing: Queue orders for one-by-one processing.

Data Ingestion: Collect data at high velocity and process it when possible.

Message Broker

A robust system that includes the features of both Event Bus and Message Queue. Pub-Sub and Point-to-Point.

Can be one-to-one, one-to-many, or many-to-many.

When to use it:

- Complex data routing scenarios.

- Many communication patterns within a single application.

- Transformation and aggregation of messages.

Examples:

Multi-service Orchestration: Coordinate tasks among various microservices using complex routing rules.

Have you used any of them? Share your war stories.

[Jaana Dogan ヤナ ドガン @rakyll]

Life is too short to waste. If you are waking up every day and don't/can't celebrate your accomplishments, you are wasting your life with wrong people.

[Tony C. Batista @tony_tcb]

@KennethCassel @facina_s

[Daniel Moka⚡ @dmokafa]

Many software engineering teams don't have time to do it right.

But surprisingly, they have time to do it twice.

[Tony C. Batista @tony_tcb]

@jacksonfall @_thiagob @facina_s

[Tony C. Batista @tony_tcb]

@facina_s @brunomtorrao @sseraphini Que doidera bixo! A tecnologia tá aí pra ser usada, pro bem ou mal.

[Tony C. Batista @tony_tcb]

@wahVinci @_thiagob @facina_s

[Gergely Orosz @GergelyOrosz]

A big difference between two type of software 'architects':

#1: Speaks the tech jargon. But *only* uses the jargon.

#2: Speaks the tech jargon. But *only* uses jargon when it's helpful - and they know the other party understands - else uses plain language to explain ideas.

[Tony C. Batista @tony_tcb]

@raquelrealofc @vitorkeese @_thiagob kkkkkkkk

[zerohash @zerohashx]

Zero Hash adds Support for the MATIC token in the State of New York on both the Polygon and Ethereum blockchains.

Learn more: https://t.co/sQIaB9e4L7

#crypto #matic #polygon #ethereum #usdc #litecoin #chainlink #erc20 #bitlicence

[Tony C. Batista @tony_tcb]

@mariaverneke @iconcepcional Kkkkkkkk bora procurar uma dessa aí pra ele

[ripkeniv @ripkeniv]

@MemeingBitcoin @DocumentingBTC If you are buying a fixed amount of Bitcoin, then yeah, the difference is negligible. But if you are buying with a fixed amount of dollars, then it makes a big difference.

[Alex Xu @alexxubyte]

I just put all my technical threads in one big PDF. It has 75 topics and 158 pages!

Here are some sample topics:
🔹 Why is Redis fast?
🔹 Design Google Maps
🔹 How does HTTPs work?

The PDF Link is in the first post of my newsletter: https://t.co/PczMAd8Jdb

Hope it's helpful.

[Tony C. Batista @tony_tcb]

@_thiagob @steevehook Que isso cara. Obrigado você 👊👊👊

[Addy Osmani @addyosmani]

The "Software Engineering at Google" book is now free to read online: https://t.co/cqX79uZNFK. Great insights on improving code quality & scaling engineering teams.

[Golang News & Libs & Jobs - human 🗣️ , no 🤖 @golangch]

An interesting article about "80x caching improvement in Go by moving away from JSON and using gob instead"
#golang

https://t.co/YHjK3dqvO2