Add docker compose setup

[pavan4]

This PR adds:

• A docker compose setup to start everything up and register a sample endpoint
• Update the readme to reflect the changes

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[pavan4]

I have read the CLA Document and I hereby sign the CLA

[tillrohrmann]

cc @gvdongen

[joebowbeer]

For maximum utility, consider adding a .devcontainer instead or in addition:

https://devcontainers.github.io/

[gvdongen]

Hi! Thank you for your contribution.

The section in the Readme as well as the Docker compose file should move to the Typescript basics example, since it are instructions to run this specific example.

Besides that, I am not fully convinced that this is the right approach since it abstracts away so much that you don't really understand anymore what you did. Running the docker compose setup in detached mode makes you also not see the retries in the service logs. Unless you maybe add a docker logs command to the readme.

I am trying to figure out whether there is some nice middle ground where the user understands that there is a server running and a service and sees how the retries take place, while making it easier to run. What are your thoughts on this?

[gvdongen]

Suggested change

	- restate server
	- Restate Server

[gvdongen]

Suggested change

	- [typescript example-0](typescript/basics/src/0_durable_execution.ts)
	- [TypeScript basics Durable Execution example](typescript/basics/src/0_durable_execution.ts)

[gvdongen]

Suggested change

	- register the endpoint /service with restate
	- register the endpoint /service with Restate

[gvdongen]

I think this can be simplified to:

curl localhost:8080/SubscriptionService/add \
  -H 'idempotency-key: some-key-for-idempotency' \
  --json '{
    "userId": "Sam Beckett",
    "creditCard": "1234-5678-9012-3456",
    "subscriptions" : ["Netflix", "Disney+", "HBO Max"]
}'

[pavan4]

Thank you for the review. Happy to help.

The section in the Readme as well as the Docker compose file should move to the Typescript basics example, since it are instructions to run this specific example.

Yeah, happy to move all those to Typescript basics folder if needed.

Besides that, I am not fully convinced that this is the right approach since it abstracts away so much that you don't really understand anymore what you did. Running the docker compose setup in detached mode makes you also not see the retries in the service logs. Unless you maybe add a docker logs command to the readme.

I am trying to figure out whether there is some nice middle ground where the user understands that there is a server running and a service and sees how the retries take place, while making it easier to run. What are your thoughts on this?

For some context, this all came about from #161 I am just trying to follow up from there.

But my two cents - I personally used the compose file first ran everything to see it working and only then dug into how it works, including checking the logs etc., I just didn't want to install a bunch of things and try to setup everything line by line as a first step. Of course, once I understood, I then went into doing all that. I found more value in the ease of bringing everything up and seeing it working end to end than looking at retries and logs.