Question 1

Two languages, two paid Postgres databases - is the Python example just a port of the TypeScript one?

Accepted Answer

The README says each example deploys its own web service, workflow and paid Postgres database, and that the two share the 3D frontend and the game rules. So the split sits entirely on the backend. What it does not say is which TypeSafe primitive or model each backend uses, or whether the two implementations are otherwise equivalent; the per-language READMEs are where that would live.

Question 2

What does Jev actually decide in this game - the shot, the keeper, or the physics?

Accepted Answer

Undocumented. The README describes a penalty shootout where turns alternate between shooting and keeping goal, one workflow task owning the match and Postgres storing scores. It never states whether the model chooses a shot target, a dive direction, or something else entirely, nor how many alternatives it is offered. That framing detail would have to come from the TypeScript or Python README or from docs/architecture.md.

Question 3

What happens if a workflow run dies halfway through a match - is the score recoverable?

Accepted Answer

The README does not cover failure handling. There is no mention of retries, idempotency, run timeouts, or what state a half-finished match leaves in Postgres, and no recovery path is documented for the user-facing game. The only persistence story given is that scores are saved in Render Postgres.

Question 4

Is there a cheaper way to try this than deploying two production stacks?

Accepted Answer

Nothing in the README suggests one. It describes each example as deploying its own web service, workflow and paid Postgres database, and gives no local-only instructions, no docker-compose path and no cost estimate. The shared frontend is the only part described as common, so scoping a fork down to one language would be your own decision rather than a documented option.

Question 5

What infrastructure does each Beat Jev example deploy?

Accepted Answer

Each language example deploys its own web service, a Render Workflows task, and a paid Postgres database, so running both examples costs more than running one. A single workflow task owns a match and the score is kept in Render Postgres.

Question 6

What is shared between the TypeScript and Python examples?

Accepted Answer

They share the 3D frontend and the game rules, so only the backend differs. The README links a docs/architecture.md for the flow and a related Route Lab demo.

Question 7

Does the README document how Jev decides a shot or a save?

Accepted Answer

No. It names the infrastructure but not which Jev primitive is called, which model version is used, how the prompt frames a shot or a save, or whether any physics is computed in code, so that part is undocumented.

Beat Jev

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev guides

From the Jev community