SFSC:sfsc

Shop Floor Service Connector

License	Apache License, Version 2.0
GroupId	com.github.nalim2
ArtifactId	sfsc
Last Version	0.1.10
Release Date	Jan 29, 2021
Type	pom
Description	SFSC:sfsc Shop Floor Service Connector
Project URL	https://www.isw.uni-stuttgart.de/forschung/steuerungsarchitekturen/SFSC/
Source Code Management	https://github.com/nalim2/SFSC

Download sfsc

Filename	Size
sfsc-0.1.10.pom	9 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.github.nalim2/sfsc/ -->
<dependency>
    <groupId>com.github.nalim2</groupId>
    <artifactId>sfsc</artifactId>
    <version>0.1.10</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.github.nalim2/sfsc/
implementation 'com.github.nalim2:sfsc:0.1.10'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.github.nalim2/sfsc/
implementation ("com.github.nalim2:sfsc:0.1.10")

Apache Buildr

'com.github.nalim2:sfsc:pom:0.1.10'

Apache Ivy

<dependency org="com.github.nalim2" name="sfsc" rev="0.1.10">
  <artifact name="sfsc" type="pom" />
</dependency>

Groovy Grape

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

Scala SBT

libraryDependencies += "com.github.nalim2" % "sfsc" % "0.1.10"

Leiningen

[com.github.nalim2/sfsc "0.1.10"]

Dependencies

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

Project Modules

• proto
• common-java
• core
• docker-core
• adapter
• hello-world
• framework

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