Question 1

Is go-marathon stable enough for production use?

Accepted Answer

No, the README notes it's under active development with frequent, possibly breaking API changes. It's best for development or projects that can handle updates, not mission-critical systems requiring stability.

Question 2

How do I connect go-marathon to a Marathon cluster with multiple endpoints?

Accepted Answer

Specify a comma-separated list of URLs in the configuration. The library uses the first available endpoint and automatically fails over if it goes offline, with background pinging to detect recovery, as shown in the client creation example.

Question 3

What's the difference between SSE and callback events in go-marathon?

Accepted Answer

SSE events use Server-Sent Events and work with Marathon >= 0.9.0 without extra setup. Callback events require starting a built-in web server for Marathon to push events to, adding configuration complexity for interface and port settings.

Question 4

go-marathon vs writing my own Marathon client in Go – which is better?

Accepted Answer

Go-marathon saves time with a comprehensive, tested API abstraction, HA support, and event handling. Rolling your own client might be simpler for minimal needs, but you'll miss out on these features and the included fake implementation for testing.

Question 5

How do I create and scale applications using go-marathon?

Accepted Answer

Use the DSL methods like `NewDockerApplication()` to define apps and `ScaleApplicationInstances()` to scale them, with helper functions like `WaitOnApplication`. The README has code snippets showing deployment from definition to scaling.

Question 6

Does go-marathon support Marathon's pod feature?

Accepted Answer

Yes, it fully supports pods with methods for creation, scaling, and deletion using an idiomatic Go API. Examples are in the `examples/pods` directory and summarized in the README with snippets for pod management.

Question 7

How can I mock Marathon API responses in tests with go-marathon?

Accepted Answer

Use the included fake Marathon implementation, which relies on YML-encoded response messages. You can define static or indexed responses and scopes to simulate API behaviors, as detailed in the Development section of the README.

go-marathon

What is go-marathon?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions