https://github.com/jzillmann/tweaky
Pieces of a traditional master-node cluster setup with modern technology
https://github.com/jzillmann/tweaky
cluster-computing dagger grpc-java
Last synced: 7 months ago
JSON representation
Pieces of a traditional master-node cluster setup with modern technology
- Host: GitHub
- URL: https://github.com/jzillmann/tweaky
- Owner: jzillmann
- License: apache-2.0
- Created: 2018-05-31T17:30:33.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-06-18T21:10:14.000Z (over 7 years ago)
- Last Synced: 2025-05-23T12:40:03.913Z (9 months ago)
- Topics: cluster-computing, dagger, grpc-java
- Language: Java
- Size: 277 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Tweaky
Pieces of a traditional master-node cluster setup with modern technology.
## Build
- `./gradlew generateProto` - Generate protbuf sources
- `./gradlew cleanEclipse eclipse` - Create Eclipse files
## TODO
- √GRPC sample
- √Logging
- √NodeRegistrationValidator
- √Junit5 ExternalResource
- √Implement Node registration
- √Dagger example
- Remove log4j impl from pom.xml
- NodeAcceptor
- Dagger for nodes
- Push node-name to node
- Convert Node/Conductor into pure GRPC services (with proto files, Component & Component.Builder interfaces ?)
- stuff like serverServices() would come out of the GRPC module
- Think about how that influence advanced stuff like node communication (strategies), listener, event-bus, etc...
## Thoughts
- Example projects:
- Distributed Map
- Task Queue
- Node Role Support
- Conductor assigns role(s) to node on registration
- Node starts services based on roles
- Services
- Monitoring
- Monitoring-UI
- Utils
- CallTracing (from client, to conductor including all node calls. Use metadata. Check https://github.com/grpc-ecosystem/grpc-opentracing)
- Profiling (custom for apps. just have generic proto files available. Nodes can track their individual work steps)