home.social

#pubsub — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #pubsub, aggregated by home.social.

fetched live
  1. Redis Pub/Sub drops messages when consumers disconnect. Swap it for Streams + Consumer Groups: append-only radix tree, offsets, ACKs, PEL per group. valtersit.com/vault/migrating- #redis #streams #pubsub

  2. Codex написал рабочий код, но не закрыл задачу: как меняется мой процесс разработки

    Я всё меньше пишу первую версию кода сам. Раньше backend-задача чаще начиналась для меня с реализации. Сейчас я могу описать её Codex, получить diff и уже от него идти дальше: разбираться в коде, проверять поведение системы, находить недостающий контекст и отдавать задачу на следующую итерацию. Недавно этот процесс хорошо проявился на интеграции между несколькими сервисами. Codex написал рабочий код, но end-to-end задача осталась незакрытой.

    habr.com/ru/articles/1082478/

    #codex #ai #pubsub #diff #qa

  3. Codex написал рабочий код, но не закрыл задачу: как меняется мой процесс разработки

    Я всё меньше пишу первую версию кода сам. Раньше backend-задача чаще начиналась для меня с реализации. Сейчас я могу описать её Codex, получить diff и уже от него идти дальше: разбираться в коде, проверять поведение системы, находить недостающий контекст и отдавать задачу на следующую итерацию. Недавно этот процесс хорошо проявился на интеграции между несколькими сервисами. Codex написал рабочий код, но end-to-end задача осталась незакрытой.

    habr.com/ru/articles/1082478/

    #codex #ai #pubsub #diff #qa

  4. Publish-Subscribe (pub/sub) is a messaging pattern that decouples publishers from subscribers through a broker. Publishers send messages without knowing who receives them; subscribers get only messages matching their interests.

    #PubSub #DistributedSystems #Fintech

  5. Publish-Subscribe (pub/sub) is a messaging pattern that decouples publishers from subscribers through a broker. Publishers send messages without knowing who receives them; subscribers get only messages matching their interests.

    #PubSub #DistributedSystems #Fintech

  6. Publish-Subscribe (pub/sub) is a messaging pattern that decouples publishers from subscribers through a broker. Publishers send messages without knowing who receives them; subscribers get only messages matching their interests.

    #PubSub #DistributedSystems #Fintech

  7. Publish-Subscribe (pub/sub) is a messaging pattern that decouples publishers from subscribers through a broker. Publishers send messages without knowing who receives them; subscribers get only messages matching their interests.

    #PubSub #DistributedSystems #Fintech

  8. New progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):

    goffi.org/id/libervia-progress

    I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).

    #Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless

  9. New progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):

    goffi.org/id/libervia-progress

    I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).

    #Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless

  10. New progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):

    goffi.org/id/libervia-progress

    I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).

    #Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless

  11. New progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):

    goffi.org/id/libervia-progress

    I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).

    #Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless

  12. I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).

    May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.

    Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.

    This is context of nlnet.nl/project/ServerlessXMP

    #Libervia #XMPP #Pubsub #nlnet #ngi0

  13. I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).

    May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.

    Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.

    This is context of nlnet.nl/project/ServerlessXMP

    #Libervia #XMPP #Pubsub #nlnet #ngi0

  14. I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).

    May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.

    Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.

    This is context of nlnet.nl/project/ServerlessXMP

    #Libervia #XMPP #Pubsub #nlnet #ngi0

  15. I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).

    May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.

    Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.

    This is context of nlnet.nl/project/ServerlessXMP

    #Libervia #XMPP #Pubsub #nlnet #ngi0

  16. Kafka: Queue & Pub-Sub Together 📨

    Queue (1-to-1):
    1 consumer group, consumers = partitions
    Each message → 1 consumer only

    Pub-Sub (1-to-many):
    Multiple consumer groups
    Each group → all messages

    Traditional systems need separate tools.
    Kafka does both natively!

    #Kafka #MessageQueue #PubSub #DevOps

  17. Server-Sent Events Beat WebSockets for 95% of Real-Time Apps (Here's Why) - DEV Community

    "Everyone defaults to WebSockets for real-time features. Most shouldn't.

    The reality: 95% of "real-time" applications only need server → client updates. Chat notifications. Live dashboards. Stock tickers. Log streams. AI responses.

    WebSockets give you bidirectional communication. But bidirectional comes with a tax: complexity, resource overhead, scaling challenges, debugging nightmares.

    Server-Sent Events (SSE) do one thing: stream data from server to client. They do it brilliantly. And for..."

    https://dev.to/polliog/server-sent-events-beat-websockets-for-95-of-real-time-apps-heres-why-a4l?context=digest

    #events #http #pubsub #sse #webdev

  18. Broadcast Channel API - Web APIs | MDN

    "The Broadcast Channel API allows basic communication between browsing contexts (that is, windows, tabs, frames, or iframes) and workers on the same origin.

    By creating a BroadcastChannel object, you can receive any messages that are posted to it. You don't have to maintain a reference to the frames or workers you wish to communicate with: they can "subscribe" to a particular channel by constructing their own BroadcastChannel with the same name, and have bi-directional communication between a..."

    https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API

    #pubsub #webdev

  19. @visionaire genau heute las ich xkcd mal wieder.

    Da macht sich also wieder jemand Gedanken wie man Social Media neu erfinden kann.

    Immerhin wurde #pubsub und #mastodon als Nische erwähnt.

    Schade das nicht erwähnt wurde WARUM man was neues braucht und nicht das #fediverse besser promoten kann

    xkcd.com/927/

  20. @visionaire genau heute las ich xkcd mal wieder.

    Da macht sich also wieder jemand Gedanken wie man Social Media neu erfinden kann.

    Immerhin wurde #pubsub und #mastodon als Nische erwähnt.

    Schade das nicht erwähnt wurde WARUM man was neues braucht und nicht das #fediverse besser promoten kann

    xkcd.com/927/

  21. @visionaire genau heute las ich xkcd mal wieder.

    Da macht sich also wieder jemand Gedanken wie man Social Media neu erfinden kann.

    Immerhin wurde #pubsub und #mastodon als Nische erwähnt.

    Schade das nicht erwähnt wurde WARUM man was neues braucht und nicht das #fediverse besser promoten kann

    xkcd.com/927/

  22. Libervia CLI Tip 16:

    You need to modify many pubsub items? `li pubsub transform` is there to help.

    It uses an executable (e.g., shell or Python script), gives it each item as input, and replaces it with the returned item. Use `DELETE` to retract the item, and `SKIP` to ignore it.

    Very handy if you, e.g., moved an URL and need to update all your blog posts, change a tag, or do any kind of massive modification.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #XMPP #pubsub

  23. Libervia CLI Tip 16:

    You need to modify many pubsub items? `li pubsub transform` is there to help.

    It uses an executable (e.g., shell or Python script), gives it each item as input, and replaces it with the returned item. Use `DELETE` to retract the item, and `SKIP` to ignore it.

    Very handy if you, e.g., moved an URL and need to update all your blog posts, change a tag, or do any kind of massive modification.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #XMPP #pubsub

  24. Libervia CLI Tip 16:

    You need to modify many pubsub items? `li pubsub transform` is there to help.

    It uses an executable (e.g., shell or Python script), gives it each item as input, and replaces it with the returned item. Use `DELETE` to retract the item, and `SKIP` to ignore it.

    Very handy if you, e.g., moved an URL and need to update all your blog posts, change a tag, or do any kind of massive modification.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #XMPP #pubsub

  25. Libervia CLI Tip 16:

    You need to modify many pubsub items? `li pubsub transform` is there to help.

    It uses an executable (e.g., shell or Python script), gives it each item as input, and replaces it with the returned item. Use `DELETE` to retract the item, and `SKIP` to ignore it.

    Very handy if you, e.g., moved an URL and need to update all your blog posts, change a tag, or do any kind of massive modification.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #XMPP #pubsub

  26. Libervia CLI Tip 15:

    When publishing a blog or other pubsub based feature, the item ID is often used in the URL when it is rendered for the web (e.g.; Libervia or Movim use something like `https://…/blog/<user>/<item_id>`).

    It is then important to have a user-friendly item ID (e.g.; `title-of-my-publication-abc123`), which is usually done by the software from the title.

    If you want to change it, you can use `li pubsub rename`.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #xmpp #pubsub

  27. Libervia CLI Tip 15:

    When publishing a blog or other pubsub based feature, the item ID is often used in the URL when it is rendered for the web (e.g.; Libervia or Movim use something like `https://…/blog/<user>/<item_id>`).

    It is then important to have a user-friendly item ID (e.g.; `title-of-my-publication-abc123`), which is usually done by the software from the title.

    If you want to change it, you can use `li pubsub rename`.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #xmpp #pubsub

  28. Libervia CLI Tip 15:

    When publishing a blog or other pubsub based feature, the item ID is often used in the URL when it is rendered for the web (e.g.; Libervia or Movim use something like `https://…/blog/<user>/<item_id>`).

    It is then important to have a user-friendly item ID (e.g.; `title-of-my-publication-abc123`), which is usually done by the software from the title.

    If you want to change it, you can use `li pubsub rename`.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #xmpp #pubsub

  29. Libervia CLI Tip 15:

    When publishing a blog or other pubsub based feature, the item ID is often used in the URL when it is rendered for the web (e.g.; Libervia or Movim use something like `https://…/blog/<user>/<item_id>`).

    It is then important to have a user-friendly item ID (e.g.; `title-of-my-publication-abc123`), which is usually done by the software from the title.

    If you want to change it, you can use `li pubsub rename`.

    libervia.org/__b/doc/backend/l

    #Libervia #CLI #li #tips #xmpp #pubsub

  30. ActiveMQ Artemis vs Apache Kafka

    Добрый день. Сегодня мы поговорим о двух мощных технологиях для асинхронного обмена данными — ActiveMQ Artemis и Apache Kafka. Мы разберемся, что они из себя представляют, как устроены под капотом, и главное — в каких ситуациях стоит выбрать одну, а в каких другую. Наш план на сегодня довольно насыщенный. Мы начнем с того, почему вообще все пришли к асинхронному общению сервисов. Затем подробно разберем ActiveMQ Artemis — что это и какие задачи решает. Заглянем в его техническую архитектуру, чтобы понять источник его производительности. После этого мы кратко вспомним основы Apache Kafka, чтобы затем перейти к самому интересному — детальному сравнению. Мы составим четкие рекомендации, поговорим о нагрузочных характеристиках и подведем итоги.

    habr.com/ru/articles/959660/

    #activemq_artemis #apache_kafka #брокер_сообщений #очереди_сообщений #асинхронное_программирование #messaging #jms #eventdriven_architecture #pubsub

  31. ActiveMQ Artemis vs Apache Kafka

    Добрый день. Сегодня мы поговорим о двух мощных технологиях для асинхронного обмена данными — ActiveMQ Artemis и Apache Kafka. Мы разберемся, что они из себя представляют, как устроены под капотом, и главное — в каких ситуациях стоит выбрать одну, а в каких другую. Наш план на сегодня довольно насыщенный. Мы начнем с того, почему вообще все пришли к асинхронному общению сервисов. Затем подробно разберем ActiveMQ Artemis — что это и какие задачи решает. Заглянем в его техническую архитектуру, чтобы понять источник его производительности. После этого мы кратко вспомним основы Apache Kafka, чтобы затем перейти к самому интересному — детальному сравнению. Мы составим четкие рекомендации, поговорим о нагрузочных характеристиках и подведем итоги.

    habr.com/ru/articles/959660/

    #activemq_artemis #apache_kafka #брокер_сообщений #очереди_сообщений #асинхронное_программирование #messaging #jms #eventdriven_architecture #pubsub