In 2014, Pact created an entire engineering discipline. Consumer-driven contract testing — the idea that the API consumer, not the provider, should define what compatibility means — was a genuine breakthrough. It solved problems that integration testing couldn't, with mathematical certainty, in CI. The Pact Foundation's specification has been ported to twelve languages. PactFlow, the commercial parent, was... - Source: dev.to / 2 months ago

The Pact Broker is a central registry where contracts are published and versioned. PactFlow offers a hosted version; self-hosting is also available. - Source: dev.to / 4 months ago

You can self-host the open-source Pact Broker or use the managed PactFlow service. - Source: dev.to / 4 months ago

Wow a full post about contract testing without mentioning pact https://pactflow.io/. - Source: Hacker News / 8 months ago

Another type of integration tests are called contract tests. These are the ones that verify cross-system integration. You should have lots of them and they are also essential! I can highly recommend https://pactflow.io/. Source: over 3 years ago

Anecdotal, but I have built from scratch a fairly large OpenAPI-compliant service using the Goa dsl (https://goa.design) and a coding agent and I've suspected for a while that the reason I've been as productive as I have with few blind alleys is that Goa kept the mistake surface pretty constrained. I also like not having the model generate boilerplate, as Goa's tooling does all that so much more cheaply. YMMV. - Source: Hacker News / about 1 month ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / over 2 years ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 2 years ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 3 years ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 3 years ago