io.kermoss:cmd-scheduler


License

License

GroupId

GroupId

io.kermoss
ArtifactId

ArtifactId

cmd-scheduler
Last Version

Last Version

0.0.1.RELEASE
Release Date

Release Date

Type

Type

jar
Description

Description

Project Organization

Project Organization

Pivotal Software, Inc.

Download cmd-scheduler

How to add to project

<!-- https://jarcasting.com/artifacts/io.kermoss/cmd-scheduler/ -->
<dependency>
    <groupId>io.kermoss</groupId>
    <artifactId>cmd-scheduler</artifactId>
    <version>0.0.1.RELEASE</version>
</dependency>
// https://jarcasting.com/artifacts/io.kermoss/cmd-scheduler/
implementation 'io.kermoss:cmd-scheduler:0.0.1.RELEASE'
// https://jarcasting.com/artifacts/io.kermoss/cmd-scheduler/
implementation ("io.kermoss:cmd-scheduler:0.0.1.RELEASE")
'io.kermoss:cmd-scheduler:jar:0.0.1.RELEASE'
<dependency org="io.kermoss" name="cmd-scheduler" rev="0.0.1.RELEASE">
  <artifact name="cmd-scheduler" type="jar" />
</dependency>
@Grapes(
@Grab(group='io.kermoss', module='cmd-scheduler', version='0.0.1.RELEASE')
)
libraryDependencies += "io.kermoss" % "cmd-scheduler" % "0.0.1.RELEASE"
[io.kermoss/cmd-scheduler "0.0.1.RELEASE"]

Dependencies

compile (6)

Group / Artifact Type Version
javax.interceptor : javax.interceptor-api jar 1.2
org.springframework.boot : spring-boot-starter-web jar 1.5.6.RELEASE
org.springframework.boot : spring-boot-actuator jar 1.5.6.RELEASE
org.springframework.boot : spring-boot-starter-data-jpa jar 1.5.6.RELEASE
org.springframework.cloud : spring-cloud-starter-feign jar
com.zaxxer : HikariCP jar 3.1.0

test (4)

Group / Artifact Type Version
junit : junit jar 4.12
com.h2database : h2 jar 1.4.196
com.github.tomakehurst : wiremock-standalone jar 2.18.0
org.springframework.boot : spring-boot-starter-test jar 1.5.6.RELEASE

Project Modules

There are no modules declared in this project.

Kermoss: A Reactive Business Flow

KERMOSS-LOGO

Build Status codecov GitHub Maven Central

Problem:

To improve performance and consistency in a distributed environment, an application shouldn't go for ways such as two-phase commit or you'll find your self in a situation similar to the two generals problem, instead the application should strive for eventual consistency. in such a model a transactional operation is devided into multiple steps. during the execution.

Kermoss ToolBox:

  • Saga of transactions distributed via federated orchestrators (realm-ambassador)
  • Idempotence out of box at all levels, out of the box
  • Very advanced auditabilty: Debugging and monitoring of the entire value chain managed by Kermoss
  • Reliability is the core principle of Kermoss and the dimension that gave it more chance to exist

See the reference documentation! for more information .

Acknowledgements

  • YourKit supports Kermoss with its full-featured Java Profiler. Take a look at YourKit's leading software products: YourKit Java Profiler.

io.kermoss

Kermoss

Reactive business flow projects for a saga distributed business transaction

Versions

Version
0.0.1.RELEASE