messaging   23722

« earlier    

ØMQ - The Guide - ØMQ - The Guide
ZeroMQ (also known as ØMQ, 0MQ, or zmq) looks like an embeddable networking library but acts like a concurrency framework. It gives you sockets that carry atomic messages across various transports like in-process, inter-process, TCP, and multicast. You can connect sockets N-to-N with patterns like fan-out, pub-sub, task distribution, and request-reply. It's fast enough to be the fabric for clustered products. Its asynchronous I/O model gives you scalable multicore applications, built as asynchronous message-processing tasks. It has a score of language APIs and runs on most operating systems. ZeroMQ is from iMatix and is LGPLv3 open source.
queue  messaging  concurrency 
3 hours ago by Hwinkler
Greg Young: A decade of DDD, CQRS and Event Sourcing - Ken Coenen — Ordina JWorks Tech Blog
Event Storming exercises help you to figure out which domains you have in your system and give you a clear view on the different events. You can then formalize events and commands.

Ideas about Event Sourcing have been spreading. Functional programming gained popularity in parallel with event sourcing. Event sourcing is a natural functional model. Every state is a left fold of your previous history.

A lot of other things also pushed Event Sourcing forward:

Cloud computing
Popularity of Actor Models
Some people see CQRS as a full-blown architecture, but it’s not. This is wrong. CQRS and event sourcing is not a top level architecture. You cannot build an Event Sourced system. Instead, you end up into building a monolith which is event sourced internally. Event sourcing is simply not a good solution to every problem. For example, once you deal with immutable events, you need to think about corrections to data. Whenever a user corrects a value and hits the save button again, you would need to have an event for that and it would be too complex to handle.
messaging  Patterns  concurrency  design 
2 days ago by janpeuker
Messaging that just works — RabbitMQ
"RabbitMQ is the most widely deployed open source message broker"
communication  database  messaging  data  opensource 
3 days ago by hannes
Watermill is a Golang library for working efficiently with message streams. It is intended for building event-driven applications, enabling event sourcing, RPC over messages, sagas and basically whatever else comes to your mind. You can use conventional pub/sub implementations like Kafka or RabbitMQ, but also HTTP or MySQL binlog if that fits your use case. It comes with a set of Pub/Sub implementations, which can be easily extended by your own implementations. Watermill is also shipped with a set of standard tools (middlewares) like instrumentation, poison queue, throttling, correlation and other tools used by every message-driven application. Our goal was to create a tool which is easy to understand, even by junior developers. It doesn't matter if you want to do Event-driven architecture, CQRS, Event Sourcing or just stream MySQL Binlog to Kafka. Watermill was designed to process hundreds of thousands of messages per second. Every component is built in a way that allows you to configure it for your needs. You can also implement your own middlewares for the router. Watermill is using proven technologies and has a strong unit and integration tests coverage for the critical areas.
golang  go  messaging  pubsub  agnostic 
4 days ago by dlkinney
Emitter: Scalable Real-Time Communication Across Devices
Emitter is a real-time communication service for connecting online devices. The Publish-Subscribe messaging API is built for speed and security.
communication  realtime  service  golang  go  messaging  mqtt  iot  internetofthings  mobile 
4 days ago by dlkinney

« earlier    

related tags

1password  2019  2020  academia  actor  aggregator  agnostic  alan  algorithm  all  amazon  amqp  android  anonymous  apache  api  app  application  apps  appscrossplatform  architecture  asynchronous  authenticity  aws  b2b  bcd  binary  bitcoin  blackberry  blogs  book  bots  bug  building  business  buying  camel  card  cards  chat  client  cluster  collaboartion  collaboration  combine  commercial  communication  comparo  computer  concurrency  cqrs  credit  criticism  crossplatform  crypto  cryptography  culture  daring_fireball  data  database  decentralized  democrats  design  desktop  destruct  distributed  dm  dr  duplex  early  eip  election  elections  email  employers  encoding  encryption  erase  eth  ethereum  events  eventsourcing  facebook's  facebook.messenger  facebook  feature  federation  filesharing  finance  fosdem  foss  framework  franz  go-to-market  go  golang  hack  healthcare  history  identity  im  imap  influencer  influencers  information  internet  internetofthings  ios  iot  iphone  irb  is  java  javascript  jms  jobs  kafka  kay  lang:go  locking  longread  macos  mathematics  message-queue  message  messenger  microservices  middle_east  mit  mobile  model  mqtt  mvvm  nats  nerd  networking  one  oop  opensource  ott  p2p  pager  pattern  patterns  payment  payments  personal  phishing  php  plan:  politics  postgresql  presentations  privacy  productivity  programming  protocol  psychology  pubsub  python  queue  queues  rabbitmq  radio  realtime  reference  reliability  research  rest  route  rule  scaling  scoop:  secure  security  server  serverless  service  sex  shannon  signal  skype  slack  smalltalk  sms  sns  soa  social  software  spying  sqs  storage  stream  streaming  surveillance  system  telecommunications  telegram  telephone  temporary  texting  them  theory  throttle  throttling  to  tools  topics  toread  totwitter  trust  twitter  type:framework  unix  viber  video  videochat  voip  web  websocketd  websockets  windows  xamarin 

Copy this bookmark: