# FAQ

Q: What problem does Journey solve?

Building reliable and scalable business logic takes time and effort. Journey simplifies the "reliable and scalable" part, so you can focus on the "business logic" part.

In the past, to make your application work across crashes, restarts, failures, and replicas... you would either have to do the hard (and, let's be honest, often unappreciated) work yourself OR manage separate, complex infrastructure or use dedicated paid cloud services (e.g. Temporal or AWS Step Functions).

Instead, Journey provides Durable Workflow functionality as a package. The executions of your application's workflows are persisted to PostgreSQL, and they seamlessly continue across outages, failures, restarts, redeployments, and scaling events.

With complex plumbing taken care of, you can spend your time and attention on your application's actual logic. No cloud services to buy or subscribe to, no additional infrastructure to deploy.

Q: Is Journey used in production?

A: Yes. I am currently using Journey in a few production systems.

While those systems are closed-source, I created JourDash – an open-source Journey-based "food delivery" example, so you can play with it and see how it works in practice. You can find the link to JourDash source code and a running instance (among other things) in the /docs (opens in a new window) section.

If you are using Journey in production, just playing with it, or have questions / comments / suggestions, I'd love to hear from you!

Q: This is neat. Do you have a Rust (Python, ...) version of this?

A: Journey is currently only available in Elixir, but if you are interested in a different language, please let me know.

Q: Who built Journey?

A: I did! I'm Mark (opens in a new window) , a software engineer in Seattle, WA.