What’s New in Hmily? A Deep Dive into the Latest Architecture and Roadmap

The article presents Hmily’s monthly report, detailing its high‑performance distributed transaction solution, recent architectural refactoring, newly added modules and SPI implementations, community‑driven bug fixes and feature releases, and outlines upcoming versions supporting TCC and TAC modes.

Programmer DD
Programmer DD
Programmer DD
What’s New in Hmily? A Deep Dive into the Latest Architecture and Roadmap

Hmily Restart Monthly Report

Hmily is a high‑performance, highly reliable, easy‑to‑use flexible distributed transaction solution that currently supports RPC frameworks such as Dubbo, Spring‑Cloud, Motan, and gRPC, offering zero‑intrusion Spring‑Boot and Spring‑Namespace integration for a financial‑grade transaction system.

Adjusted Architecture and More Reasonable Module Division

Panorama:

Architecture adjustments:

Extracted core execution module, supporting multiple transaction modes and hybrid use (TCC, TAC).

Removed Spring dependency from core module.

Defined implementations for various SPI interfaces.

Added hmily-rpc: aggregates support for multiple RPC frameworks.

Added hmily-spi: custom SPI mechanism implementation.

Added hmily-bom: resolves version dependency conflicts.

Added hmily-metrics: monitors JVM, threads, transaction status, latency, etc.

Added hmily-tcc: core implementation of TCC mode.

Added hmily-tac: core implementation of TAC mode.

SPI Module Division

Added hmily-repository: transaction log storage supporting MySQL, Oracle, PostgreSQL, SQLServer, Zookeeper, Redis, MongoDB, and file.

Added hmily-serializer: transaction log serialization supporting Hessian, JDK, Kryo, Protobuf.

Added hmily-config: configuration module supporting local mode, Zookeeper, Nacos, Apollo, Etcd.

Added hmily-tac-sqlparser: SQL parsing for TAC mode.

Community Issue Triage and Bug Fixes

The community focuses on sorting and resolving previously reported issues and collaborating on new development.

Bug fixes (examples)

dubbo

framework does not support annotation usage (spring-boot-starter-dubbo). motan framework does not support annotation usage. spring-cloud users encounter exceptions when integrating Feign with Hystrix and Hmily.

Transaction log serialization exceptions.

Timeout‑induced transaction hanging bugs.

Transaction scheduled recovery bugs.

Community completed features (examples)

build

: added Travis‑CI integration.

Transaction log storage added support for Oracle, PostgreSQL, SQLServer, MongoDB, Zookeeper, file, and Redis.

Configuration module added support for Apollo, Etcd, and Nacos configuration centers.

Demo added motan-rpc usage with Hmily distributed transaction demo.

Community Co‑building Principles

Core principles: simple, happy, elegant, harmonious.

Code standards follow hmily-checkstyle with flexibility.

Open principle encourages collaborative code review and problem solving without authoritarian control.

Recent Updates

Upcoming release of hmily-2.1.0 will support only the TCC mode.

Configuration module now supports dynamic refresh across all configuration centers.

Future Plans

More RPC framework support, e.g., brpc.

Support for XA mode.

Further roadmap details are open for community contribution via the GitHub and Gitee repositories.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

MicroservicesBackend DevelopmentDistributed TransactionsHmily
Programmer DD
Written by

Programmer DD

A tinkering programmer and author of "Spring Cloud Microservices in Action"

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.