Add Weaviate

[kcm]

Please check if what you want to add to awesome-go list meets quality standards before sending pull request. Thanks!

Please provide package links to:

• repo link (github.com, gitlab.com, etc): https://github.com/weaviate/weaviate
• pkg.go.dev: https://pkg.go.dev/github.com/weaviate/weaviate
• goreportcard.com: https://goreportcard.com/report/github.com/weaviate/weaviate
• coverage service link (codecov, coveralls, etc.): https://app.codecov.io/gh/weaviate/weaviate

Note: that new categories can be added only when there are 3 packages or more.

Make sure that you've checked the boxes below that apply before you submit PR. Not every repository (project) will require every option, but most projects should. Check the Contribution Guidelines for details.

• [x] The package has been added to the list in alphabetical order.
• [x] The package has an appropriate description with correct grammar.
• [x] As far as I know, the package has not been listed here before.
• [x] The repo documentation has a pkg.go.dev link.
• [x] The repo documentation has a coverage service link.
• [x] The repo documentation has a goreportcard link.
• [x] The repo has a version-numbered release and a go.mod file.
• [X] I have read the Contribution Guidelines, Maintainers Note and Quality Standards.
• [x] The repo has a continuous integration process that automatically runs tests that must pass before new pull requests are merged.
• [x] The authors of the project do not commit directly to the repo, but rather use pull requests that run the continuous-integration process.

Thanks for your PR, you're awesome! :+1:

[avelino]

Thank you for contributing with awesome-go, we will revise your contribution as soon as possible.

Automation body links content check:

• godoc.org or pkg.go.dev: True
• goreportcard.com: True
• coverage: True

your project is about to be approved, it's under revision, it may take a few days

[etiennedi]

Since the Contribution Guidelines mention that tests will be reviewed as well, let me also drop a link to Weaviate's stress test pipeline repo. The idea behind this repo is to stress-test Weaviate in scenarios that run too long for typical acceptance tests.

For example, let's imagine there was a rare bug that corrupts files only after importing a specific amount, e.g. 1M, objects into Weaviate. This would be a great scenario to add a new stress test pipeline to this repo. In fact, most of the existing pipelines are there to prevent a regression on a bug that's already fixed. Right now there are 16 such pipelines in addition to the regular test pyramid of unit, integration & component, and e2e tests.

I thought it might be worth mentioning those tests, since they don't show up in coverage numbers, but provide tremendous value to guarantee the stability of the database.

[kcm]

@avelino just a ping! looking forward to participating.

[kcm]

@avelino anything we can help with here? Thanks!