mimi-messaging 1.2.7 → 1.2.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 527a758d4b21ce645d864f0653e69fc9c190e736
-  data.tar.gz: 77b21de1f5e0b3a0ca2430468e9981b8ecf58f9b
+SHA256:
+  metadata.gz: 8fa18eabeb0e00848c4eaf7eca202e77cef3526bd6995506ce810f0000dbdc9e
+  data.tar.gz: 34808e22b8405e89de11f0c571ac98004a2be18fa52e3587877e8f9eeb9c0dc0
 SHA512:
-  metadata.gz: 9b64ee4bda0243a7a5f60a54f2b34ce43b83e4d8dc0d6c931bd3e73e1bc5a9716a5f97acaec555f2ccd3728442af54d17dd483d8122b23dea1ce982dc3ea4429
-  data.tar.gz: 9b930b5b3b13c3b6d5a5e984ad10a96c5e644659374a416708820a7c42e94ba546a6c9c802b371bcfd1a918b6bd0697022f236ee34a1114c1883cf6678282094
+  metadata.gz: c88607df18839125d858dea4ca4a076403910ac0f1ced785289dbe990910ff193ca069d16e6a72e67a43119ef983671e2dde3582a1871b9118fca3ac774746b8
+  data.tar.gz: 485b23c110854107a0580f0932a1bd60a1a5d3bf45ae57cf914dd778733a328adf0c642fbcdde1cf2ee2ba5d87b627a5fc97486e1682daef09277d0dbd168fdc

data/README.md

@@ -1,7 +1,11 @@
-# [WIP] mimi-messaging
+# mimi-messaging
 
 Interservice communication via message bus for microservices.
 
+## Is it production ready?
+
+No. Consider this project a WIP.
+
 ## What
 
 `mimi-messaging` is a Messaging layer -- an interservice
@@ -15,6 +19,9 @@ See also: [Overview of Messaging layer properties](docs/Messaging_Layer_Properti
 
 ## Why
 
+When it comes to organizing communications between different microservices of a system,
+currently there is only two options: to use HTTP or a message bus.
+
 [Why HTTP is a bad choice for interservice communication?](docs/Why_HTTP_is_a_bad_choice.md)
 
 TBD: Message bus pro's and con's.
@@ -45,10 +52,20 @@ Mimi::Messaging.start
 
 ## Usage
 
+Producing messages:
 ```
+# COMMAND
+Mimi::Messaging.command("users/lock", id: "b3cc29c8d2ec68e0")
+
+# QUERY
 response = Mimi::Messaging.query("orders/show", id: 123)
+
+# EVENT
 ```
 
+See (/examples)[/examples] folder for more examples on how to produce and consume messages.
+
+
 ## Adapters
 
 `mimi-messaging` is not bound to a specific message broker implementation like RabbitMQ or Kafka. It interacts with a message broker using an adapter interface and
@@ -58,7 +75,7 @@ there are several available adapters:
 * RabbitMQ (TBD)
 * NATS (TBD)
 * [Amazon SQS/SNS](https://github.com/kukushkin/mimi-messaging-sqs_sns)
-* in-memory (single process)
+* (in-memory (single process))[lib/mimi/messaging/adapters/memory.rb]
 
 ## Designing apps
 
@@ -71,6 +88,9 @@ There are only two hard problems in distributed systems:
 2. Exactly-once delivery
 ```
 
+
+[Messaging API specification format](https://github.com/kukushkin/mimi-messaging-spec)
+
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/docs/Messaging_Layer_Properties.md

@@ -95,7 +95,7 @@ For commands and queries, the target of the message consists of a queue name
 and a method name (e.g. `"customers/create"`).
 
 For events, the target of the message consists of a topic name and an
-event type (e.g. `"customers/created"`).
+event type (e.g. `"customers#created"`).
 
 This allows to model the communication around your business domain concepts,
 and not the implementation details like application or host names.

data/docs/Why_HTTP_is_a_bad_choice.md

@@ -1,6 +1,4 @@
-# Why HTTP is a bad choice for interservice communication
-
-[WIP]
+# [WIP] Why HTTP is a bad choice for interservice communication
 
 Downsides of HTTP:
 * inherently synchronous
@@ -17,4 +15,6 @@ Downsides of HTTP:
 
 Pro's of HTTP:
 * synchronous communication is simple
-* HTTP as technology is well known by engineers
+* HTTP as technology is well known by engineers
+* more stable and simpler to setup if the services are not closely deployed (e.g. in different datacenters/regions)
+

data/lib/mimi/messaging/version.rb

@@ -2,6 +2,6 @@
 
 module Mimi
   module Messaging
-    VERSION = "1.2.7"
+    VERSION = "1.2.8"
   end
 end

data/mimi-messaging.gemspec

@@ -36,6 +36,6 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency "bundler", "~> 2.0"
   spec.add_development_dependency "pry", "~> 0.12"
-  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "rake", "~> 13.0"
   spec.add_development_dependency "rspec", "~> 3.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mimi-messaging
 version: !ruby/object:Gem::Version
-  version: 1.2.7
+  version: 1.2.8
 platform: ruby
 authors:
 - Alex Kukushkin
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-10-14 00:00:00.000000000 Z
+date: 2021-02-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: mimi-core
@@ -58,14 +58,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '10.0'
+        version: '13.0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -145,8 +145,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.14.4
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: Interservice communication via message bus for microservices