Skip to content

Commit

Permalink
Fix port references in text and move tour to correct position (#169)
Browse files Browse the repository at this point in the history
  • Loading branch information
gvdongen authored Oct 24, 2023
1 parent 65aedc4 commit 50b238d
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 8 deletions.
2 changes: 1 addition & 1 deletion docs/examples.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Pick an example from the list below and follow the instructions in the README to
## Intermediate examples

- [Ticket reservation system](https://github.com/restatedev/examples/tree/main/typescript/ticket-reservation): a subset of a ticket booking system to illustrate how Restate's keyed-sharding and concurrency guarantees simplify microservice architectures.
- [Food ordering](https://github.com/restatedev/examples/tree/main/typescript/food-ordering): The order processing app of a fast food chain implemented with Awakeables and delayed calls.
- [Food ordering](https://github.com/restatedev/examples/tree/main/typescript/food-ordering): The (serverless) order processing app of a fast food chain implemented with awakeables.

## Advanced examples

Expand Down
4 changes: 2 additions & 2 deletions docs/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ Restate handles durability and recovery (including recovering partial handler ex

# Examples

* [**Stateful serverless applications**](https://github.com/restatedev/examples/tree/main/typescript/lambda-greeter): Create one (or a few) functions with statefule business logic and run them on any FaaS.
* **Low-latency workflows**: Like payments processing, inventory keeping, user management, billing, … Including cases where you probably like consistency, but hadn’t thought of workflows before, due to latency
* [**Stateful serverless applications**](https://github.com/restatedev/examples/tree/main/typescript/lambda-greeter): Create one (or a few) functions with stateful business logic and run them on any FaaS.
* **Low-latency workflows**: Like payments processing, inventory keeping, user management, billing, … Including cases where you want high consistency, but hadn’t thought of workflows before, due to latency
* [Keeping track of a shopping cart and ticket inventory](https://github.com/restatedev/examples/tree/main/typescript/ticket-reservation)
* [Consistent payment processing via Stripe-style concurrent API](https://github.com/restatedev/examples/tree/main/typescript/payment-api)
* [**Microservice orchestration**](https://github.com/restatedev/examples/tree/main/typescript/ecommerce-store): Writing orchestration functions as simple promise-based code where you previously needed to create complex state machines and handle state transitions durability.
Expand Down
10 changes: 5 additions & 5 deletions docs/tour.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
id: tour
sidebar_position: 1
sidebar_position: 3
title: "Tour of Restate"
description: "Discover Restate using the Typescript handler API."
---
Expand Down Expand Up @@ -92,8 +92,8 @@ Now, we need to tell Restate where the service runs.
<Tabs groupId="operating-systems">
<TabItem value="lin" label="Linux">

You do this by sending a request to the endpoint of the runtime at `http://localhost:8081/endpoints`
and providing it with the endpoint of the service `http://localhost:8080`.
You do this by sending a request to the endpoint of the runtime at `http://localhost:9070/endpoints`
and providing it with the endpoint of the service `http://localhost:9080`.

```shell
curl -X POST http://localhost:9070/endpoints -H 'content-type: application/json' -d '{"uri": "http://localhost:9080"}'
Expand All @@ -105,8 +105,8 @@ and knows how to invoke a specific service.
</TabItem>
<TabItem value="mac" label="macOS">

You do this by sending a request to the endpoint of the runtime at `http://localhost:8081/endpoints`
and providing it with the endpoint of the service `http://host.docker.internal:8080`.
You do this by sending a request to the endpoint of the runtime at `http://localhost:9070/endpoints`
and providing it with the endpoint of the service `http://host.docker.internal:9080`.

```shell
curl -X POST http://localhost:9070/endpoints -H 'content-type: application/json' -d '{"uri": "http://host.docker.internal:9080"}'
Expand Down

0 comments on commit 50b238d

Please sign in to comment.