go-localstack VS go-txdb

Compare go-localstack vs go-txdb and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
go-localstack go-txdb
- 2
75 618
- 1.9%
8.6 6.7
5 days ago 23 days ago
Go Go
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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-localstack

Posts with mentions or reviews of go-localstack. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning go-localstack yet.
Tracking mentions began in Dec 2020.

go-txdb

Posts with mentions or reviews of go-txdb. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-03-29.
  • Integration Tests with Postgres
    2 projects | /r/golang | 29 Mar 2023
    3 years ago I created a internal library where I worked to setup the testing with the db's. One param was the schema directory and the other one was the path of the data insertion file. It worked really well but was a little slow. It was a little bit weird to configure the container to run the tests. As I would have to give access to go container that ran the unit tests access to docker. But back then I was running boot2docker and made things very cumbersome. I think with a local docker things would be way simpler. I ended up using and normal DB from the CI/CD and https://github.com/DATA-DOG/go-txdb If I had to do it again I might do an hybrid in-between the two solutions
  • Unit Testing a Grom Application With a Real DB Server
    3 projects | /r/golang | 27 Jul 2022
    The first one is TestMain, which could improve the lifecycle management of the container. The second one is DATA-DOG/go-txdb, this allows you to open a new db connection running in a transaction, so each test could have its own isolated DB connection.

What are some alternatives?

When comparing go-localstack and go-txdb you can also consider the following projects:

S3Mock - A simple mock implementation of the AWS S3 API startable as Docker image, TestContainer, JUnit 4 rule, JUnit Jupiter extension or TestNG listener

go-sqlmock - Sql mock driver for golang to test database interactions

gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽

hoverfly - Lightweight service virtualization/ API simulation / API mocking tool for developers and testers

mockhttp - Mock object for Go http.ResponseWriter

Mmock - Mmock is an HTTP mocking application for testing and fast prototyping

Fake - Fake data generator for Go (Golang)

ddns-route53 - Dynamic DNS for Amazon Route 53 on a time-based schedule

gomock - GoMock is a mocking framework for the Go programming language.

monkey - Monkey patching in Go