go-sqlmock
Centrifugo
go-sqlmock | Centrifugo | |
---|---|---|
19 | 31 | |
5,837 | 7,924 | |
0.9% | 1.4% | |
5.4 | 8.9 | |
27 days ago | 2 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
go-sqlmock
- How do you unit-test code that reaches out to the db, without introducing interfaces everywhere?
-
Creating an API using Go and sqlc
For that, I used the lib go-sqlmock. So, for example, the following snippet is part of the person/service_test.go file:
-
Using SQLC in project how do I mock database Calls with it for unit testing?
It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.
- What is the coolest Go open source projects you have seen?
- How to mock database calls
-
Can you set expectations for SQL transaction using Testify?
I use Sqlmock for that purpose
- Mocking database queries - ask for opinion
- SQL mock driver for Golang to test database interactions
- Can't get a specifc SQL query with pgx to work
-
[HELP] how to test this piece of code?
There is a good lib for db tests https://github.com/DATA-DOG/go-sqlmock
Centrifugo
-
WebSockets vs. Server-Sent-Events vs. Long-Polling vs. WebRTC vs. WebTransport
Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.
What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.
Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.
If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.
- Centrifugo v5.1.0 released, with new powers for real-time messaging tasks, now with proxy GRPC subscription streams – similar to WebSocketd but over the network
-
Integrating websockets into my current app
Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.
- Millions of Active WebSockets with Node.js
-
Show HN: DriftDB is an open source WebSocket back end for real-time apps
https://github.com/centrifugal/centrifugo
It's a complete solution, including server, admin panel and client library.
We're an European company and use OVH, Hetzner and others.
-
Laravel Websockets vs Soketi vs Laravel Echo Server
Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:
-
Is Python a good option to implement Websockets?
Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.
- Centrifugo – real-time messaging server (WebSocket, etc.) which scales well and integrates with any backend. SDKs for browser and mobile development included
-
What is the coolest Go open source projects you have seen?
Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo
- Golang updating the front-end with almost real-time events from the backend server
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
Socket.io - Realtime application framework (Node.JS server)
go-txdb - Immutable transaction isolated sql driver for golang
NATS - Golang client for NATS, the cloud native messaging system.
mockery - A mock code autogenerator for Go
Confluent Kafka Golang Client - Confluent's Apache Kafka Golang client
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
Mercure - 🪽 An open, easy, fast, reliable and battery-efficient solution for real-time communications
minimock - Powerful mock generation tool for Go programming language
laravel-websockets - Websockets for Laravel. Done right.
gotests - Automatically generate Go test boilerplate from your source code.
soketi - Next-gen, Pusher-compatible, open-source WebSockets server. Simple, fast, and resilient. 📣