go-clean-arch VS elastic

I'm working on a project that makes use of Hexagonal Architecture to keep things loosely coupled and I learned golang recently. So, I would recommend you to check out Go clean arch, I think you can a learn a lot from it.

Try this

It will be good to have a look at the Go (Golang) Clean Architecture based on Uncle Bob's Clean Architecture https://github.com/bxcodec/go-clean-arch

Has anyone come across any Golang repo like go-clean-arch which uses elasticsearch? As I am a beginner and wanted to have a bit of practice of building microservice using Go with Elasticsearch.

Thanks, everyone. I am able to understand a few things using go-elasticsearch. Though Olivere/elastic is simpler, it is not future-proof. I just wanted a repository similar to cleanarchitecture which uses elasticsearch, on the top of which I can practice. Please provide a link here if anyone has come across such a repo.

View on GitHub

https://threedots.tech/post/introducing-clean-architecture/ https://github.com/bxcodec/go-clean-arch

i am trying to generate the following query using github.com/olivere/elastic/v7

I think that https://olivere.github.io/elastic/ is a lot better as an API client

For Go available two good libraries for elasticsearch, the official Elasticsearch client and another one from community olivere elastic, both is good, but at this moment only the official client supports 8 version of elasticsearch and for serious production think it's the choice.

You are using the Query DSL, which is documented here, and has examples for boolean combination queries, so if you want it built up in a more strongly-typed fashion, check the documentation for it: https://github.com/olivere/elastic/wiki/QueryDSL

ElasticSearch repository implementation uses go-elasticsearch official library, another good one is olivere elastic but here it's not support 8 version which used for this project.

In this project we have microservice working with EventStoreDB using oficial go client, for [projections (https://zimarev.com/blog/event-sourcing/projections/) used MongoDB and Elasticsearch for search, and communicate by gRPC and REST. Did not implement here any interesting business logic and didn't cover tests, because don't have enough time, the events list is very simple: create a new order, update shopping cart, pay, submit, cancel, change the delivery address, complete order, and of course in real-world better use more concrete and meaningfully events, but the target here is to show the idea and how it works. Event Sourcing can be implemented in different ways, used here EventStoreDB, but we can do it with PostgreSQL and Kafka for example. After trying both approaches, found EventStoreDB is a better solution because all required features are implemented out of the box, it is optimized and really very good engineers developing it.

Relevant Discussion from the maintainer

I have only used the olivere library and I think it is as good as a Go library gets.