JarCasting
JarCasting JarCasting

org.dromara:hmily-admin

Parent pom providing dependency and plugin management for applications built with Maven

License

License
GroupId

GroupId

org.dromara
ArtifactId

ArtifactId

hmily-admin
Last Version

Last Version

2.0.2-RELEASE
Release Date

Release Date
Type

Type

jar
Description

Description

Parent pom providing dependency and plugin management for applications built with Maven
Project URL

Project URL

https://projects.spring.io/spring-boot/#/spring-boot-starter-parent/hmily-admin
Project Organization

Project Organization

dromara

Download hmily-admin

Filename Size
hmily-admin-2.0.2-RELEASE.pom
hmily-admin-2.0.2-RELEASE.jar 39 MB
hmily-admin-2.0.2-RELEASE-sources.jar 448 KB
hmily-admin-2.0.2-RELEASE-javadoc.jar 238 KB
Browse

How to add to project

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

Dependencies

compile (17)

Group / Artifact Type Version
org.dromara : hmily-common jar 2.0.2-RELEASE
org.springframework.boot : spring-boot-starter-web jar 2.0.2.RELEASE
org.springframework.boot : spring-boot-starter-aop jar 2.0.2.RELEASE
org.springframework.boot : spring-boot-configuration-processor Optional jar 2.0.2.RELEASE
org.springframework.boot : spring-boot-autoconfigure jar 2.0.2.RELEASE
org.springframework.boot : spring-boot-starter-data-redis jar 2.0.2.RELEASE
org.springframework.boot : spring-boot-starter-jdbc jar 2.0.2.RELEASE
org.springframework : spring-web jar 5.0.7.RELEASE
com.zaxxer : HikariCP jar 3.2.0
org.springframework.data : spring-data-mongodb jar 2.0.8.RELEASE
org.mongodb : mongo-java-driver jar 3.5.0
org.apache.zookeeper : zookeeper jar 3.4.9
org.apache.commons : commons-lang3 jar 3.3.2
commons-beanutils : commons-beanutils jar 1.9.2
commons-codec : commons-codec jar 1.11
com.jayway.jsonpath : json-path jar 2.4.0
mysql : mysql-connector-java jar 5.1.46

test (2)

Group / Artifact Type Version
org.springframework.boot : spring-boot-starter-test jar 2.0.2.RELEASE
junit : junit jar 4.12

Project Modules

There are no modules declared in this project.

Financial-level flexible distributed transaction solution

https://dromara.org/

English | 简体中文

gitee stars github forks github stars github contributors


Panorama of distributed transaction solutions

Features

  • high reliability ：supports abnormal transaction rollback in distributed scenarios, and abnormal recovery over time to prevent transaction suspension

  • usability ：provide zero-invasive Spring-Boot, Spring-Namespace to quickly integrate with business systems

  • high performance ：decentralized design, fully integrated with business systems, naturally supporting cluster deployment

  • observability ：metrics performance monitoring of multiple indicators, and admin management background UI display

  • various RPC ： support Dubbo, SpringCloud, Motan, Sofa-rpc, brpc, tars and other well-known RPC frameworks

  • log storage ： support mysql, oracle, mongodb, redis, zookeeper etc.

  • complex scene ： support RPC nested call transaction

Necessary premise

  • must use JDK8+

  • TCC mode must use a RPC framework, such as: Dubbo, SpringCloud, Montan

TCC mode

when using the TCC mode, users provide three methods: try, confirm, and cancel according to their business needs. And the confirm and cancel methods are implemented by themselves, and the framework is only responsible for calling them to achieve transaction consistency。

TAC mode

When the user uses the TAC mode, the user must use a relational database for business operations, and the framework will automatically generate a rollback SQL, When the business is abnormal, the rollback SQL will be executed to achieve transaction consistency。

Documentation

EN doc

CN doc

If you want to use it, you can refer to Quick Start

About Hmily

Hmily is a flexible distributed transaction solution that provides TCC and TAC modes。

It can be easily integrated by business with zero intrusion and rapid integration。

In terms of performance, log storage is asynchronous (optional) and asynchronous execution is used, without loss of business methods。

It was previously developed by me personally. At present, I have restarted at JD Digital. The future will be a distributed transaction solution for financial scenarios.。

Follow the trend

Stargazers over time

User wall

Support

Versions

Version
2.0.2-RELEASE