re-org: protocol, user support libs, ... #61
Replies: 1 comment 3 replies
-
I think using user support library or sdk makes the same thing, both are interchangeable terms. I think in our documentation we should have a glossary of terms and that's where we would explain that both terms can be found and that they have the same meaning.
I agree. But I would like to rewrite these sdks so that it is easier to evolve in the future with no dependencies than what has been done in the past. We can even fork what exists, but we should create a new branch and work with a blank slate. Obviously it will be possible to bring in some of the existing code if necessary.
Agree. But there is an outstanding question about the question we asked Lightbend. This directly affects how we will do our own protocol. |
Beta Was this translation helpful? Give feedback.
-
I'd like to re-org certain things we inherit from Cloudstate. To get a container with all things Cloustate and Akkaserverless, I've already forked every repository that I found relevant into https://github.com/eigr-labs. My plan would be to stay in sync with their stuff and not having them in our main repo.
Next step would be to establish our own protocol and user support libraries within eigr. That would be a fork of the existing work we did with LB and then re-branded and re-named for our project.
I'm still not sure if I'd use eigr as the main name, and therefore the Go User Language Support lib is "eigr/go-support" or if we have something like "eigr/serverless-go-support" or "eigr/whatever-go-support". You might found out that eigr, like akka, is a mountain :). We don't have to hold that 1:1. I found eigr a nice name to contain certain stuff. So "eigr/protocol" is nice... or then eigr/perma for our state models. I'm not sure, lets find out.
Tasks I see:
Beta Was this translation helpful? Give feedback.
All reactions