wire
aws-sdk-go
Our great sponsors
wire | aws-sdk-go | |
---|---|---|
29 | 34 | |
12,291 | 8,549 | |
2.3% | 0.4% | |
2.7 | 9.4 | |
about 2 months ago | 2 days ago | |
Go | Go | |
Apache License 2.0 | 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.
wire
- Injeção de dependência em Go
-
Question about dependency initialization
We use https://github.com/google/wire for every bigger project, take a look at it, it beautifully solves initialisation and also gives you a guideline on how to do it.
-
As a Go programmer, what design pattern, programming techniques have you actually used, implemented regularly in your workplace which made your life much easier?
Im by no means a "purist" in such things, I love my magic and QoL-features/libs, but havent seen something that is so easy to use in go, that I immediately wanted to add it. And to be fair, I only looked closely at https://github.com/google/wire , others I have just skipped - and I will be looking into uber-fx as mentioned in the other comment.
-
Config for production and mocking (db connections, http parsers etc)
If you have such a complex and deep dependency graph, and you don't want to manually maintain it, you could use some DI library to handle that for you. Something like https://github.com/google/wire for small-medium size stuff, or https://github.com/uber-go/fx for larger scale, more enterprise projects.
- Is it just me or does nobody really know what idiomatic Go is.
-
What's the best dependency injection framework / methodology for Golang for the enterprise?
Try https://github.com/google/wire. Compile time generated like dagger 2 in java.
-
Modern API design with Golang, PostgreSQL and Docker.
Most people probably do it by hand (I do). But otherwise, probably https://github.com/google/wire is the most popular, maybe followed by https://github.com/uber-go/fx.
-
Google's internal Go style guide
For larger object graphs do you roll everything by hand or encourage something like https://github.com/google/wire
-
godi a New Dependency Injection library - feedback welcome
The other thing is that I'm lazy, so I don't construct all dependencies in main.go manually but use wire to generate the construction of my dependency tree.
-
Go on AWS Lambda with API Gateway and AWS SAM
This guy fucks. Modular monoliths is the way. The service initialization/wiring part could be simplified (given a bigger project ofc) using something like https://github.com/google/wire. But everything else... *chef kiss* beautiful.
aws-sdk-go
- my first go project, a CLI application to store IP addresses
-
Go 1.21 will (probably) download newer toolchains on demand by default
I'm... really not sure I agree with this, from a philosophical point of view. It feels like this is making "eh, we'll just upgrade our Go version next quarter" too easy; ultimately some responsibility toward updating your application's Go version to work with what new dependencies require should fall on Us, the application developers. Sure, we're bad at it. Everyone's lived through running years-old versions of some toolchain. But I think this just makes the problem worse, not better.
Its compounded by the problem that, when you're setting up a new library, the `go` directive in the mod file defaults to your current toolchain; most likely a very current one. It would take a not-insignificant effort on the library author's part to change that to assert the true-minimum version of Go required, based on libraries and language features and such. That's an effort most devs won't take on.
I'd also guess that many developers, up-to this point if not indefinitely because education is hard, interpreted that `go` directive to mean more-of "the version of go this was built with"; not necessarily "the version of go minimally required". There are really major libraries (kubernetes/client-go [1]) which assert a minimum go version of 1.20; the latest version (see, for comparison, the aws-sdk, which specifies a more reasonable go1.11 [2]). I haven't, you know, fully audited these libraries, but 1.20 wasn't exactly a major release with huge language and library changes; do they really need 1.20? If devs haven't traditionally operated in this world where keeping this value super-current results in actually significant downstream costs in network bandwidth (go1.20 is 100mb!) and CI runtime, do we have confidence that the community will adapt? There's millions of Go packages out there.
Or, will a future version of Go patch a security update, not backport it more than one version or so, and libraries have to specify the newest `go` directive version, because manifest security scanning and policy and whatever? Like, yeah, I get the rosy worldview of "your minimum version encodes required language and library features", but its not obvious to me that this is how this field is, or even will be, used.
Just a LOT of tertiary costs to this change which I hope the team has thought through.
[1] https://github.com/kubernetes/client-go/blob/master/go.mod#L...
[2] https://github.com/aws/aws-sdk-go/blob/main/go.mod
- How to get better on golang
-
Send an Email through AWS SES with GoLang
This email was sent with " + "Amazon SES using the " + "AWS SDK for Go.
-
Looking for library recommendations: Django -> Golang port
I figured I'd ask the community for some recommendations for the following capabilities that Django + python stack is giving me at the moment: 1. Amazon SES Mailing (considering - aws-sdk-go) 2. Django Admin (considering go-admin 3. Django Signals (considering syncsignals 4. Celery (No contenders here)
-
S3 upload with progress
I've been trying to implement some logging of progress when uploading objects to S3. My code is building on this example and can be found here.
-
Background process in Lambda using SQS
Now that you have everything you need, let’s install the AWS SDK for Go library.
- Node.js 18 support in Lambda added to Go SDK
- Node.js 18 Runtime support added to Golang SDK
-
AWS and its complicated shit needs to die
Counterpoint 2: Amazon is bad and should feel bad for making this an internal and embedding it in the Credentials struct.
What are some alternatives?
fx - A dependency injection based application framework for Go.
minio-go - MinIO Go client SDK for S3 compatible object storage
dig - A reflection based dependency injection toolkit for Go.
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
gomock - GoMock is a mocking framework for the Go programming language.
botocore - The low-level, core functionality of boto3 and the AWS CLI.
do - ⚙️ A dependency injection toolkit based on Go 1.18+ Generics.
twitter-scraper - Scrape the Twitter frontend API without authentication with Golang.
container - A lightweight yet powerful IoC dependency injection container for the Go programming language
cachet - Go(lang) client library for Cachet (open source status page system).
goioc/di - Simple and yet powerful Dependency Injection for Go
goamz