If it’s real-time → WebSockets If it’s scale → Kafka If it’s simplicity → REST If it’s chaos → GraphQL If it’s AI → Python If it’s infra → Go If it’s logs → ElasticSearch If it’s low-latency → Redis If it’s high-availability → Postgres If it’s streaming → Flink

@theskilledcoder Sockets are hard to scale, if you check X which is realtimr even they aren't using it

@theskilledcoder Interesting pairings. Context and nuance often determine the best tool though. One size rarely fits all.

@motiadev replaces most of these tools for good cause and simplification. If you want to test -> motia If you want workers -> motia If you want to see logs -> motia If you want to write API -> motia If you want to see traces -> motia If you want to run cron job -> motia If you want to run AI agents -> motia If you want real-time streams -> motia If you want to build multi-language workflows -> motia

@theskilledcoder If it’s automation → Ansible If it’s monitoring → Prometheus If it’s orchestration → Kubernetes If it’s search → Solr If it’s caching → Memcached If it’s messaging → RabbitMQ If it’s analytics → Spark If it’s ML → TensorFlow If it’s containerization → Docker

@theskilledcoder Elasticsearch for logs? Do you mean logstash?

@theskilledcoder If it's real time -> SSE (server sent events) Websockets are overkill for 90% of usecases when you just need one way communication

@theskilledcoder I'd replace Kafka with Nats Redis with Valkey ElasticSearch with anything else, that monster is memory hungry

@theskilledcoder Isn't mongodb better for high availability than postgres? Postgres is better for consistency i guess

@theskilledcoder ElasticSearch for logs is pricey - move to a specialized provider like Mezmo or a large do-it-all like Clickhouse

@theskilledcoder SQLite? how you dare!

@theskilledcoder And if it’s meetings → Jira

@theskilledcoder What rhe point for go for infra..?

@theskilledcoder Highly missing JavaScript

@theskilledcoder If it's all, @getDataOrb coming soon...

@theskilledcoder WebRTC > Websocket

@theskilledcoder If it’s web -> caddy

@theskilledcoder High Availability would be a NoSQL DB by default rather than Postgres. While it has some NoSQL like features and can be somewhat of a hybrid between SQL and NoSQL, it's primarily by default, an SQL DB that favors Consistency over Availability per CAP Theorem.

@theskilledcoder If it's marketing -> AI

@theskilledcoder MongoDB looking like this

@theskilledcoder Preach, but let's not forget the power of a well-crafted Rust API or a Node.js server. Tech debt is real

@theskilledcoder If it’s project management → Notion (or sticky notes)”

@theskilledcoder rust ?

@theskilledcoder Where is Rust?

@theskilledcoder Just use .NET and spare yourself the headache.

@theskilledcoder If it's AI, you also have this : dotnet.microsoft.com/en-us/apps/ai/…

@theskilledcoder Rust 🚀

@theskilledcoder No Rust?

@theskilledcoder no c/c++?

@theskilledcoder What is this are you preparing for an exam

@theskilledcoder If it’s realtime and read only. SSE

@theskilledcoder graphql is the reason chaos exists😂

@theskilledcoder it it's scale -> kafka is too much simplification

@theskilledcoder and If it is overthinking → JavaScript 😂

@theskilledcoder If its not a job -> Rust