scastie VS go-kit

From personal experience Scala also works. It's 100% possible to learn monads using https://scastie.scala-lang.org/ as a scratch pad.

Instead I typically use https://scastie.scala-lang.org, or an ammonite script, or just create a new file that extends App in my test directory. The thing that worksheets do better is that you can import things from your project (like the little app in the test dir) but they also show runtime values (like repl or scastie). However I've just never gotten them to actually work.

I strongly recommend you play around with the local Scala REPL. I have Scala 2.13 on my main dev computer and Scala 3 on my other computer. The local REPL will let you know when things are deprecated and give you hints as to what you should use instead. Scastie https://scastie.scala-lang.org/ can also be a big help.

Operationally, as you might expect from a language borne from academia, Scala tooling can be problematic and compilation can be slow--particularly if you are not yet using Scala 3, which only recently emerged and is very slowly percolating through the ecosystem (Remember the Python 2 to Python 3 transition?). But type inference, a vast standard library, and the time-tested reliability of the JVM make you very productive once you get the hang of them. Performance varies with the JVM you're running, but regardless you do have to contend with the size of compiled objects and the latency of garbage collection at runtime. When you want to experiment, you can skip the ceremony of writing a class or test and instead use a command-line REPL, an online REPL called Scastie you can share, or an outstanding third-party command-line REPL called Ammonite. Dependency management is achieved with SBT typically but also more general JVM build tools like Gradle and Maven.

I am using https://scastie.scala-lang.org/ which does compile server side in Scala. The UI is a bit hard to handle tho.

https://github.com/scalacenter/scastie#how-do-i-embed-scastie

https://github.com/go-kit/kit

. Web backend (with various frameworks available) . Web Assembly (one of them is vugu framework) . Microservices (some frameworks: Go Micro, Go Kit, Gizmo, Kite) . Fragments services (Term mentioned by @jeffotoni in a microservices discussion group) . Lambdas (FaaS example) . Client Server . Terminal applications (using the tview lib) . IoT (some frameworks) . Bots (some here) . Client Applications using Web technology . Desktop using Qt+QML, Native Win Lib (example Qt, Qt widgets, Qml) . Network Applications . Protocol applications . REST Applications . SOAP Applications . GraphQL Applications . RPC Applications . TCP Applications . gRPC Applications . WebSocket Applications . GopherJS (compiles Go to JavaScript)

To implement service discovery in our GoLang microservice we will use GoKit, a toolkit for microservices that provides support to auth, log, service discovery, tracing and more. For this starter code the mod already installed, you can skip this step

My company uses go-kit

For reference my company Go projects are built with (go-kit)[https://gokit.io/] design patterns.

5. kit. The kit framework is a programming toolkit for building robust, reliable, and maintainable microservices in Golang. It is a collection of packages and best practices that offer businesses of all sizes a thorough, reliable, and trustworthy way to create microservices. Go is a fantastic general-purpose language, but microservices need some specialized assistance. As a result, the kit framework offers infrastructure integration, system observability, and Remote Procedure Call (RPC) safety. Golang is a first-class language for creating microservices in any organization thanks to its composition of numerous closely related packages that together form an opinionated framework for building substantial Service-Oriented Architectures (SOAs).It was created with interoperability in mind, and developers are free to select the platforms, databases, components, and architectural styles that best suit their needs. The disadvantage of using go-kit is that it has a high overhead for adding API to the service because of how heavily it relies on interfaces. Documentation Link: https://github.com/go-kit/kit

At first I was confused but this GitHub user/org is completely different from the massively popular go-kit/kit https://github.com/go-kit/kit

https://github.com/go-kit/kit#related-projects

go-micro seems like it does a bit too much, like service discovery and balancing within the framework when that's likely better handled by an Envoy/Istio.

I think the more interesting aspect of this is the framework being used: https://github.com/micro/micro

I haven't dug into it at all yet, but at a glance it looks like it's aiming to do something similar to what Go kit (https://gokit.io/) or Finagle (https://twitter.github.io/finagle/) does, where it gives you a nice abstraction for defining your "service" and then handles all the supplementary aspects (service discovery, serialization, retry/circuit breaker logic, rate limiting, hooks for logging, tracing, and metrics, etc) so you don't have to build those from scratch every time.

I don't know if any of those other frameworks could really be considered very "successful" outside the original organizations they were built for (it seems like the industry has bet more on service meshes and API gateway products), but I'd probably be more inclined to start with one of them than making a new framework.