soa 1.0.0 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Gemfile.lock +1 -1
- data/README.md +11 -10
- data/lib/soa.rb +2 -2
- data/lib/soa/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 3faf94fb12cd24e83311714817660bec0203de87eb43fd22edf6ce18b96a2129
|
4
|
+
data.tar.gz: 2e37a6c464bbfa2d3bceabccad4a4cf503dcc22d65163e944a91e78118115165
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: c35e78eb711be8829b1c9c59ac47c7c4bc5317a46123e1a1b863a7b764dc103d543d215203bc0f3fc6f6695a062da8ce9ad62a906a25a38d82d501e3b97a3eec
|
7
|
+
data.tar.gz: cb7a6ea5f2393d192fa0677746808bb0c8affb1bcea55b156dd3e0cd718ad192a9bf7d46bee3bb5e86b84f1cc59ca8bc3adef20690ce035f1d25345a1d9fb756
|
data/Gemfile.lock
CHANGED
data/README.md
CHANGED
@@ -7,16 +7,16 @@ called Twitter dot com:
|
|
7
7
|
|
8
8
|
> Microservices are great for turning method calls in to distributed computing
|
9
9
|
> problems
|
10
|
-
- [Aaron Patterson](https://twitter.com/tenderlove) on [Aug. 9,
|
10
|
+
> - [Aaron Patterson](https://twitter.com/tenderlove) on [Aug. 9,
|
11
11
|
2018](https://twitter.com/tenderlove/status/1027591532847816704)
|
12
12
|
|
13
|
-
I've helped teams maintain old, slow,
|
14
|
-
it's taught me one thing: monolithic codebases become more complex over
|
15
|
-
time
|
13
|
+
I've helped many teams maintain old, slow, & confusing monolithic applications
|
14
|
+
and it's taught me one thing: **monolithic codebases become more complex over
|
15
|
+
time**. As a result, many companies have decided to build non-monolithic
|
16
16
|
applications instead (these are called "services"; the better, more modern ones
|
17
|
-
are called "microservices"). Applications built with services are initially
|
18
|
-
|
19
|
-
|
17
|
+
are called "microservices"). Applications built with services are initially much
|
18
|
+
more difficult to create and operate, but they also tend to die sooner, which is
|
19
|
+
the best known way to reduce code complexity.
|
20
20
|
|
21
21
|
But how do you write services and microservices in a monolithic language like
|
22
22
|
Ruby? Up until now, writing services required JavaScript and AWS Lambda. But
|
@@ -27,11 +27,12 @@ The SOA gem is a drop-in replacement for Ruby's built-in method dispatch system.
|
|
27
27
|
You can continue to call legacy methods like you always have alongside new
|
28
28
|
service invocations registered with the SOA gem. It's the perfect companion for
|
29
29
|
teams looking to make a more gradual transition to a services architecture
|
30
|
-
without rewriting their entire
|
30
|
+
without rewriting their entire decades-old application in JavaScript and AWS
|
31
|
+
Lambda.
|
31
32
|
|
32
33
|
## Installation
|
33
34
|
|
34
|
-
To install SOA, we use the command line
|
35
|
+
To install SOA, we use the command line program `gem` which communicates with
|
35
36
|
the RubyGems.org microservice to download the necessary files:
|
36
37
|
|
37
38
|
```
|
@@ -49,7 +50,7 @@ require "soa"
|
|
49
50
|
with JRuby, you'll need to wait for the release of a SOAP gem.]
|
50
51
|
|
51
52
|
Once required, the SOA gem will prepare your Ruby runtime to run services and
|
52
|
-
|
53
|
+
microservices instead using our easy-to-use DSL.
|
53
54
|
|
54
55
|
## Usage
|
55
56
|
|
data/lib/soa.rb
CHANGED
data/lib/soa/version.rb
CHANGED