catty

RPC framework

License

License

GroupId

GroupId

pink.catty
ArtifactId

ArtifactId

catty-parent
Last Version

Last Version

0.2.6
Release Date

Release Date

Type

Type

pom
Description

Description

catty
RPC framework
Project URL

Project URL

https://github.com/zhengrenjie/catty
Source Code Management

Source Code Management

https://github.com/zhengrenjie/catty

Download catty-parent

Filename Size
catty-parent-0.2.6.pom 3 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/pink.catty/catty-parent/ -->
<dependency>
    <groupId>pink.catty</groupId>
    <artifactId>catty-parent</artifactId>
    <version>0.2.6</version>
    <type>pom</type>
</dependency>
// https://jarcasting.com/artifacts/pink.catty/catty-parent/
implementation 'pink.catty:catty-parent:0.2.6'
// https://jarcasting.com/artifacts/pink.catty/catty-parent/
implementation ("pink.catty:catty-parent:0.2.6")
'pink.catty:catty-parent:pom:0.2.6'
<dependency org="pink.catty" name="catty-parent" rev="0.2.6">
  <artifact name="catty-parent" type="pom" />
</dependency>
@Grapes(
@Grab(group='pink.catty', module='catty-parent', version='0.2.6')
)
libraryDependencies += "pink.catty" % "catty-parent" % "0.2.6"
[pink.catty/catty-parent "0.2.6"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

  • core
  • invokers
  • example
  • test
  • benchmark
  • all
  • config
  • extension
  • spring

Build Status Maven Central License

Catty

Whole new RPC framework!

Features

  • High performance.
  • Async & reactor oriented.
  • Micro-kernel & Easy to customize
  • ProtoBuf supported.

Project Status

Catty has released a few versions, which means you could use Catty in your own project!

But as the version is senior than 1.0.0, which means catty is not stable and has not adequately tested yet, I temporarily do not recommend you to use it in any large distribution system. But I do recommend you to use it in a smaller system or point-to-point system, in which cases Catty would be more easier to use and control.

Usage

See example package or test package.

Maven:

<dependency>
    <groupId>pink.catty</groupId>
    <artifactId>catty-all</artifactId>
    <version>0.2.6</version>
</dependency>

build:

mvn clean install -DskipTests -Dmaven.javadoc.skip=true -Dgpg.skip

test:

mvn clean test

Sync:

Server:

ServerConfig serverConfig = ServerConfig.builder()
    .port(20550)
    .build();
ProtocolConfig protocolConfig = ProtocolConfig.defaultConfig();

Exporter exporter = new Exporter(serverConfig);
exporter.setProtocolConfig(protocolConfig);
exporter.registerService(IService.class, new IServiceImpl());
exporter.export();

Client:

ClientConfig clientConfig = ClientConfig.builder()
    .addAddress("127.0.0.1:20550")
    .build();
ProtocolConfig protocolConfig = ProtocolConfig.defaultConfig();

Reference<IService> reference = new Reference<>();
reference.setClientConfig(clientConfig);
reference.setProtocolConfig(protocolConfig);
reference.setInterfaceClass(IService.class);

IService service = reference.refer();
System.out.println(service.say0());
System.out.println(service.say1("catty"));

Async:

Server:

ServerConfig serverConfig = ServerConfig.builder()
    .port(20550)
    .build();
ProtocolConfig protocolConfig = ProtocolConfig.defaultConfig();
Exporter exporter = new Exporter(serverConfig);
exporter.setProtocolConfig(protocolConfig);
exporter.registerService(IService.class, new IServiceImpl());
exporter.export();

Client:

ClientConfig clientConfig = ClientConfig.builder()
    .addAddress("127.0.0.1:20550")
    .build();
ProtocolConfig protocolConfig = ProtocolConfig.defaultConfig();

Reference<IService> reference = new Reference<>();
reference.setClientConfig(clientConfig);
reference.setProtocolConfig(protocolConfig);
reference.setInterfaceClass(IService.class);

IService service = reference.refer();
CompletableFuture<String> future = service.asyncSay("catty");
future.whenComplete((value, t) -> System.out.println(value));

Welcome to join me!

There are lots of things need todo:

  • doc
  • benchmark
  • test
  • more useful extensions
  • log & annotation
  • code review & refactor

Versions

Version
0.2.6
0.2.5
0.2.4
0.2.3
0.2.2
0.2.1
0.2.0
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.0