JarCasting
JarCasting JarCasting

com.github.nalim2:common-java

Shop Floor Service Connector

License

License
Categories

Categories

Java Languages
GroupId

GroupId

com.github.nalim2
ArtifactId

ArtifactId

common-java
Last Version

Last Version

0.1.10
Release Date

Release Date
Type

Type

jar
Description

Description

Shop Floor Service Connector

Download common-java

Filename Size
common-java-0.1.10.pom
common-java-0.1.10.jar 94 KB
common-java-0.1.10-sources.jar 43 KB
common-java-0.1.10-javadoc.jar 757 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/com.github.nalim2/common-java/ -->
<dependency>
    <groupId>com.github.nalim2</groupId>
    <artifactId>common-java</artifactId>
    <version>0.1.10</version>
</dependency>
// https://jarcasting.com/artifacts/com.github.nalim2/common-java/
implementation 'com.github.nalim2:common-java:0.1.10'
// https://jarcasting.com/artifacts/com.github.nalim2/common-java/
implementation ("com.github.nalim2:common-java:0.1.10")
'com.github.nalim2:common-java:jar:0.1.10'
<dependency org="com.github.nalim2" name="common-java" rev="0.1.10">
  <artifact name="common-java" type="jar" />
</dependency>
@Grapes(
@Grab(group='com.github.nalim2', module='common-java', version='0.1.10')
)
libraryDependencies += "com.github.nalim2" % "common-java" % "0.1.10"
[com.github.nalim2/common-java "0.1.10"]

Dependencies

compile (3)

Group / Artifact Type Version
com.github.nalim2 : proto jar 0.1.10
org.slf4j : slf4j-api jar 1.7.30
org.zeromq : jeromq jar 0.5.2

Project Modules

There are no modules declared in this project.

Shop Floor Service Connector

This project aims to provide a user friendly framework to implement a message based, service oriented architecture in the shop floor.

The core requirements are

  • user-friendliness with the support of common patterns like pub sub and client server
  • peer to peer, with no need for central infrastructure
  • possible support of multiple languages
  • low hardware requirements to support embedded devices
  • performance

The middleware is build up from two parts:

  • a "core" which can be run on industry PCs or servers and who is responsible for service registry and message routing
  • a lightweight "adapter" part which can be run anywhere and executes the services

Communication between them can be established via IPC or TCP.

As core libraries, ZMQ and Protobuf are used. The registry is implemented with Hazelcast.

Versions

Version
0.1.10
0.1.9
0.1.7
0.1.6
0.1.1
0.1.0