teivah/gosiris

An actor framework for Go

Teiva Harsanyi

I’m a software engineer specializing in distributed systems, scalability, reliability, and observability topics. I’m currently working at Google as a senior software engineer in the ML SRE team. Meanwhile, I love meeting challenges, learning, and sharing.

I'm also the author of 📖 100 Go Mistakes and How to Avoid Them.

GitHub

Stats

Main Repositories:

General:

• algodeck and designdeck: Open-Source collections of flash cards to help developers preparing their algorithm & system design interview
• sre-roadmap: An opinionated roadmap to become an SRE
• docker-kafka: Simple Docker image for Kafka, pulled +250k times

Go:

• 100-go-mistakes: The official repository of 100 Go Mistakes and How to Avoid Them
• broadcast: Notification broadcaster library
• onecontext: Set of Go context's utilities
• go-lfu: A Go library for handling LFU cache operations in O(1)
• bitvector: Static bit vector structures library
• tourniquet: gRPC client-side load balancer
• multilock: A library to efficiently store a set of Mutex or RWMutex
• resequencer: Resequencer library
• majorana: A RISC-V virtual processor
• go-bbl: Brown Bag Lunch on Go

Rust:

• rust-cheatsheet: Rust language cheat sheet
• ettore: A RISC-V virtual processor
• franz: A collection of Kafka utility tools (load testing, replication)

Haskell:

• haskell-cheatsheet: Haskell language cheat sheet

Python:

• python-cheatsheet: Python language cheat sheet

Challenges:

• advent-of-code: My solutions to the Advent Of Code from 2015 to 2023
• gossip-glomers: My solutions to Gossip Glomers, a series of distributed systems challenges

Programming Languages

The programming languages on which I built at least some basic foundations:

gosiris's Issues

Couchbase external connector

Add a Couchbase 5 connector

Setup documentation

Hey @teivah,

I'd like to explore this framework, but I'm unsure how to get going here. Is go get the right option?

Protobuf serialization

Add a new serialization mode based on Protobuf

Zipkin integration

Documentation

Kafka options

Add configurable options to connect to Kafka

Zipkin options

Add configurable options to connect to Zipkin

gosiris-http

Develop an HTTP connector

Favor local communication if possible

Today even if two actors are deployed in the same actor system, gosiris will use the transport defined (if any). This means gosiris will publish a message to Kafka or AMQP for example.

If two actors are deployed in the same system (i.e. local), they should communicate using a local golang channel (just like if no transport was specified).

zipkin-related build issue

I got this error while running go build when trying to run the helloworld example

source.golabs.io/growth/actor-model-demo/vendor/github.com/openzipkin/zipkin-go-opentracing/_thrift/gen-go/scribe

vendor/github.com/openzipkin/zipkin-go-opentracing/_thrift/gen-go/scribe/scribe.go:101:15: cannot assign 1 values to 2 variables

vendor/github.com/openzipkin/zipkin-go-opentracing/_thrift/gen-go/scribe/scribe.go:147:28: cannot use scribeProcessorLog literal (type *scribeProcessorLog) as type thrift.TProcessorFunction in assignment:
*scribeProcessorLog does not implement thrift.TProcessorFunction (wrong type for Process method)
have Process(int32, thrift.TProtocol, thrift.TProtocol) (bool, thrift.TException)
want Process(context.Context, int32, thrift.TProtocol, thrift.TProtocol) (bool, thrift.TException)

vendor/github.com/openzipkin/zipkin-go-opentracing/_thrift/gen-go/scribe/scribe.go:157:27: not enough arguments in call to processor.Process
have (int32, thrift.TProtocol, thrift.TProtocol)
want (context.Context, int32, thrift.TProtocol, thrift.TProtocol)

etcd options

Add configurable options to connect to etcd

AMQP options

Add configurable options to connect to AMQP

Kafka transport