com.github.nalim2:common-java

Shop Floor Service Connector

License	Apache License, Version 2.0
Categories	Java Languages
GroupId	com.github.nalim2
ArtifactId	common-java
Last Version	0.1.10
Release Date	Jan 29, 2021
Type	jar
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

How to add to project

Apache Maven

<!-- 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>

Gradle Groovy

// https://jarcasting.com/artifacts/com.github.nalim2/common-java/
implementation 'com.github.nalim2:common-java:0.1.10'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.github.nalim2/common-java/
implementation ("com.github.nalim2:common-java:0.1.10")

Apache Buildr

'com.github.nalim2:common-java:jar:0.1.10'

Apache Ivy

<dependency org="com.github.nalim2" name="common-java" rev="0.1.10">
  <artifact name="common-java" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.github.nalim2', module='common-java', version='0.1.10')
)

Scala SBT

libraryDependencies += "com.github.nalim2" % "common-java" % "0.1.10"

Leiningen

[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 Jan 29, 2021
0.1.9 Jul 31, 2020
0.1.7 May 26, 2020
0.1.6 May 26, 2020
0.1.1 Apr 30, 2020
0.1.0 Feb 18, 2020