pink.catty:catty-registry

RPC framework

License	Apache License, Version 2.0
GroupId	pink.catty
ArtifactId	catty-registry
Last Version	0.1.3
Release Date	Feb 16, 2020
Type	jar
Description	RPC framework

Download catty-registry

Filename	Size
catty-registry-0.1.3.pom
catty-registry-0.1.3.jar	7 KB
catty-registry-0.1.3-sources.jar	3 KB
catty-registry-0.1.3-javadoc.jar	47 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/pink.catty/catty-registry/ -->
<dependency>
    <groupId>pink.catty</groupId>
    <artifactId>catty-registry</artifactId>
    <version>0.1.3</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/pink.catty/catty-registry/
implementation 'pink.catty:catty-registry:0.1.3'

Gradle Kotlin

// https://jarcasting.com/artifacts/pink.catty/catty-registry/
implementation ("pink.catty:catty-registry:0.1.3")

Apache Buildr

'pink.catty:catty-registry:jar:0.1.3'

Apache Ivy

<dependency org="pink.catty" name="catty-registry" rev="0.1.3">
  <artifact name="catty-registry" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='pink.catty', module='catty-registry', version='0.1.3')
)

Scala SBT

libraryDependencies += "pink.catty" % "catty-registry" % "0.1.3"

Leiningen

[pink.catty/catty-registry "0.1.3"]

Dependencies

compile (3)

Group / Artifact	Type	Version
pink.catty : catty-core	jar	0.1.3
org.apache.curator : curator-framework	jar	4.0.1
org.apache.zookeeper : zookeeper	pom	3.4.14

Project Modules

There are no modules declared in this project.

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.1.3 Feb 16, 2020
0.1.2 Feb 12, 2020
0.1.0 Feb 11, 2020