dn8-modular-monolith
weaver
| dn8-modular-monolith | weaver | |
|---|---|---|
| 1 | 13 | |
| 36 | 4,564 | |
| - | 1.6% | |
| 5.7 | 9.2 | |
| 4 months ago | 9 days ago | |
| C# | Go | |
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dn8-modular-monolith
-
Towards Modern Development of Cloud Applications
I built a simple example using Postgres and .NET as a runtime: https://github.com/CharlieDigital/dn8-modular-monolith
I don't think it would be very difficult to replace the poll on the database table with a pull from SQS instead.
weaver
-
Ask HN: Would you use a Low-effort Microservice Builder?
I think a lot of people have tried to "low code" this problem. The issue is that everyone has their preferred tech stack and low-code typically only has one choice. Using a DSL for logic (conditionals in yaml strings), or a bespoke language (like DarkLang or WaspLang), is a difficult sell. Developers want to use their language of choice with real programming constructs.
The most interesting approach, the sort of holy grail if you will, is to write your code as a single application, and then the system figures out how to distribute it if/when needed. ServiceWeaver is this concept in Go
https://serviceweaver.dev/
- Service Weaver: a framework for writing and deploying cloud applications
-
Towards Modern Development of Cloud Applications
> trying to hide distribution
The paper unfortunately hides that in reality you have to pass a context object in your RPC calls, hence there is no ambiguity whether you are calling a potentially remote object.
It's in the example on the project home page: https://serviceweaver.dev/
// The "RPC" handler - Service Weaver
-
Service Weaver workshops
Service Weaver is an open source programming framework from Google that allows you to write a Go application as a modular binary and deploy it as a set of connected microservices.
-
Boneless: a CLI to create your apps with Go
Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.
-
Where Is the Spring Framework for Go?
I assume you’re already aware of https://serviceweaver.dev/ Someone’s got to do it, so let that be Google.
- Programming framework for writing and deploying cloud applications
- Service Weaver is a programming framework for writing and deploying cloud apps
What are some alternatives?
Deli - Deli is an easy-to-use Dependency Injection(DI).
pilgrim - Dependency injection for Swift (iOS, OSX, Linux). Strongly typed, pure Swift successor to Typhoon.
gotaskr - A generic task runner for Go
Needle - Compile-time safe Swift dependency injection framework
Swinject - Dependency injection framework for Swift with iOS/macOS/Linux
goyek - Task automation Go library
Cleanse - Lightweight Swift Dependency Injection Framework
Locatable - A micro-framework that leverages Swift Property Wrappers to implement the Service Locator pattern
DITranquillity - Dependency injection for iOS (Swift)
Task - A task runner / simpler Make alternative written in Go
StoryboardBuilder - Simple dependency injection for generating views from storyboard.
Fiber - ⚡️ Express inspired web framework written in Go