thronglets 0.0.2 → 0.0.3
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/README.md +18 -3
- data/lib/thronglets/cli.rb +2 -0
- data/lib/thronglets/version.rb +1 -1
- metadata +15 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: fba4d35770e78f2d4b49c76815f3e3fc76362172cdeaadd85d43356a9617386b
|
4
|
+
data.tar.gz: 598b9b11d4664d469cdaa1cc8c4ea795f5f0e0a61795a9c467c7cc5e0cea7c33
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: '0929310fb4babb08a819509dc1ec91fa63679b7d87cdc51caf60cc62797ae7d9406dc43378f1703562b2c1f3a83295cc0c980fc17fa5eeac3686165a62d37213'
|
7
|
+
data.tar.gz: 92eba071c3e45b008bdf976741e256a32154bab2dbb0de7721fc6d5cc882875b95c4265dd78767f46b8ce6f92b6cd2f11c61e57a14cb935bcb971cc1eca92047
|
data/README.md
CHANGED
@@ -1,20 +1,35 @@
|
|
1
|
-
#
|
1
|
+
# Thronglets
|
2
2
|
|
3
3
|
[](https://rubygems.org/gems/thronglets)
|
4
4
|
[](https://www.ruby-toolbox.com/projects/thronglets)
|
5
5
|
[](https://github.com/kkdoo/thronglets/actions/workflows/ci.yml)
|
6
|
-
[](https://qlty.sh/gh/kkdoo/projects/thronglets)
|
7
7
|
|
8
|
-
|
8
|
+
**Thronglets** is an open source toolkit designed to assist engineering teams in systematically breaking down and decoupling monolithic applications into modular, scalable services. Whether you're targeting microservices, modular monoliths, or service-oriented architectures, Thronglets provides a set of practical tools and patterns to analyze dependencies, extract business domains, and incrementally refactor legacy codebases with minimal risk.
|
9
|
+
|
10
|
+
Built on top of [Temporal](https://temporal.io) to orchestrate long-running workflows and service boundaries, Thronglets seamlessly integrates with existing **Ruby on Rails** applications, making it ideal for teams modernizing legacy Rails monoliths.
|
9
11
|
|
10
12
|
---
|
11
13
|
|
14
|
+
- [Why Use Thronglets?](#why-use-thronglets)
|
15
|
+
- [Use Cases](#use-cases)
|
12
16
|
- [Quick start](#quick-start)
|
13
17
|
- [Support](#support)
|
14
18
|
- [License](#license)
|
15
19
|
- [Code of conduct](#code-of-conduct)
|
16
20
|
- [Contribution guide](#contribution-guide)
|
17
21
|
|
22
|
+
## Why Use Thronglets?
|
23
|
+
|
24
|
+
Decoupling a monolith is complex and risky without the right tools. Thronglets gives you insight into your codebase, helps you plan a phased decomposition strategy, and reduces the cognitive and operational overhead of large-scale refactoring efforts.
|
25
|
+
|
26
|
+
## Use Cases
|
27
|
+
|
28
|
+
- Legacy systems modernization
|
29
|
+
- Microservice migration strategies
|
30
|
+
- Technical debt management
|
31
|
+
- Domain-driven design alignment
|
32
|
+
|
18
33
|
## Quick start
|
19
34
|
|
20
35
|
```
|
data/lib/thronglets/cli.rb
CHANGED
data/lib/thronglets/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: thronglets
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.0.
|
4
|
+
version: 0.0.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Artem Mashchenko
|
@@ -37,6 +37,20 @@ dependencies:
|
|
37
37
|
- - ">="
|
38
38
|
- !ruby/object:Gem::Version
|
39
39
|
version: '0'
|
40
|
+
- !ruby/object:Gem::Dependency
|
41
|
+
name: dry-schema
|
42
|
+
requirement: !ruby/object:Gem::Requirement
|
43
|
+
requirements:
|
44
|
+
- - ">="
|
45
|
+
- !ruby/object:Gem::Version
|
46
|
+
version: '0'
|
47
|
+
type: :runtime
|
48
|
+
prerelease: false
|
49
|
+
version_requirements: !ruby/object:Gem::Requirement
|
50
|
+
requirements:
|
51
|
+
- - ">="
|
52
|
+
- !ruby/object:Gem::Version
|
53
|
+
version: '0'
|
40
54
|
- !ruby/object:Gem::Dependency
|
41
55
|
name: listen
|
42
56
|
requirement: !ruby/object:Gem::Requirement
|