# FAQ

Q: Who built Journey?

A: I'm Mark (opens in a new window) , a software engineer living in Seattle, WA. I love the productivity of the Elixir ecosystem, and the power of computation graphs. I was inspired by how Uber Cadence (opens in a new window) and Temporal (opens in a new window) open source systems help engineers build resilient, scalable applications. I wondered if I could have a simple, lightweight Elixir package that would make it easy for me to build resilient, scalable applications, with persistence, but with no cloud services to buy or additional infrastructure to deploy. So I wrote Journey.

Q: Is Journey used in production?

A: Yes! Just talking about my own experience, I used Journey in a few production applications. Journey made it so easy to build and run applications, I felt I shouldn't be the only one to enjoy this power. ; )

Of course, I'm very interested in hearing your stories of building things with Journey. Tell me! ; )

Q: I like the idea of letting Journey worry about the flow of things, and scalability and persistence, but my application just doesn't look like a graph.

A: Some applications don't lend themselves to the graph model! That said, I was surprised at how many do. Who would have thought that Useless Machine (opens in a new window) and Credit Card Application (opens in a new window) would be readily modeled as graphs?

It takes a bit of a mental shift to start thinking of your problem as a graph, whose nodes are data points that your application collects (e.g. customer's name) or computes (e.g. credit score). But once you have constructed that mental model, you find yourself in a world teeming with persisted, self-computing graphs. ;)

Q: This is super-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: I have more questions, or a suggestion, or I need help with Journey. How do I contact you?

A: Send me a message here!