mongo-go-driver
Redis
Our great sponsors
mongo-go-driver | Redis | |
---|---|---|
15 | 32 | |
7,882 | 19,090 | |
0.9% | 2.3% | |
9.1 | 8.9 | |
7 days ago | 7 days ago | |
Go | Go | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
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.
mongo-go-driver
-
Uploading and Serving Images from MongoDB in Golang
MongoDB, a document-oriented NoSQL database, will be our data powerhouse. We'll utilize the mongo-driver library to seamlessly connect our Golang application to MongoDB. This section will cover essential database interactions, including creating collections, storing metadata, and efficiently querying for image-related data. Understanding these fundamentals is crucial for building a robust image storage and retrieval system.
-
Build a Golang Todo App Backend: A Step-by-Step Guide
mongodb.org/mongo-driver: The MongoDB supported driver for Go.
- How to decode the mongo wire message in golang
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
Go EventSourcing and CQRS with PostgreSQL, Kafka, MongoDB and ElasticSearch πβ¨π«
PostgeSQL as event store database Kafka as messages broker gRPC Go implementation of gRPC Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB MongoDB database Elasticsearch Elasticsearch client for Go. Echo web framework Kibana Kibana is data visualization dashboard software for Elasticsearch Migrate for migrations
-
Golang future web frameworks!
mongodb/mongo-go-driver 6.6k Stars, Used by -
-
Go EventSourcing and CQRS microservice using EventStoreDB πβ‘οΈπ«
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.
-
How to Build REST API using Go Fiber and MongoDB Driver
For that same reason I decided to create a simple REST API using my favorite Go framework, Fiber and this time I decided to use the MongoDB Driver.
-
Migrating from PHP to Go
Mgo has been unmaintained for years. Use the official https://github.com/mongodb/mongo-go-driver
-
Go, Kafka and gRPC clean architecture CQRS microservices with Jaeger tracing ππ§βπ»
In this article let's try to create closer to real world CQRS microservices with tracing and monitoring using: π Kafka as messages broker gRPC Go implementation of gRPC PostgreSQL as database Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus MongoDB Web and API based SMTP testing Redis Type-safe Redis client for Golang swag Swagger for Go Echo web framework
Redis
-
Using IAM authentication for Redis on AWS
MemoryDB documentation has an example for a Java application with the Lettuce client. The process is similar for other languages, but you still need to implement it. So, let's learn how to do it for a Go application with the widely used go-redis client.
-
Building RESTful API with Hexagonal Architecture in Go
For building the RESTful Point of Sale service API, I've considered and selected a combination of technologies that would work seamlessly together. For handling HTTP requests and responses, using the Gin HTTP web framework would make sense because I think it seems complete and popular among Go community too. To ensure data integrity and persistence, I'm using PostgreSQL database with pgx as the database driver, the reason I choose PostgreSQL because it is the most popular relational database to use in production and offers efficient Go integration. I'm also implementing caching using Redis with go-redis client library, which provides powerful in-memory data storage capabilities.
-
Authentication system using Golang and Sveltekit - Initialization and setup
Following the completion of the series β Secure and performant full-stack authentication system using rust (actix-web) and sveltekit and Secure and performant full-stack authentication system using Python (Django) and SvelteKit β I felt I should keep the streak by building an equivalent system in PURE go with very minimal external dependencies. We won't use any fancy web framework apart from httprouter and other basic dependencies including a database driver (pq), and redis client. As usual, we'll be using SvelteKit at the front end, favouring JSDoc instead of TypeScript. The combination is ecstatic!
- Go linter and helper for the OpenTelemetry SDK
- Redis with golang
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
Should I reuse the connection on Redis or close it after every use?
Asynq uses https://github.com/go-redis/redis in order to connect to Redis. Whenever you create a client using go-redis, the client internally manages a connection pool, so when you need to execute a command in Redis the client just retrieves a connection from the pool and uses it. After using it, the connection is released and it goes back to the pool (no need to say that the Redis client is thread-safe).
-
a tool for quickly creating web and microservice code
Caching component go-redis ristretto
-
Using Redis for CachingΒ (2022)
Go-redis
-
What is the coolest Go open source projects you have seen?
Sorry, wrong link, I meant Go client for redis. Corrected.
What are some alternatives?
redigo - Go client for Redis
riot - Go Open Source, Distributed, Simple and efficient Search Engine; Warning: This is V1 and beta version, because of big memory consume, and the V2 will be rewrite all code.
mgm - Mongo Go Models (mgm) is a fast and simple MongoDB ODM for Go (based on official Mongo Go Driver)
Hiredis - Minimalistic C client for Redis >= 1.2
mgo - Go Doc Dot Org
GORM - The fantastic ORM library for Golang, aims to be developer friendly
Go-NATS-Streaming-gRPC-PostgreSQL - Go Nats Streaming gRPC PostgerSQL emails microservice
cayley - An open-source graph database
aerospike-client-go - Aerospike Client Go
gomemcache - Go Memcached client library #golang
qmgo - Qmgo - The Go driver for MongoDB. Itβs based on official mongo-go-driver but easier to use like Mgo.