Closed gvdongen closed 1 year ago
Yes, but also which key use cases it solves (microservice orchestration, stateful serverless, workflows) and where Restate sits in the stack (vs service mesh, workflow orchestrator, message broker). At least that is the current thinking.
Should this overview page also be incorporated into our landing page given that we can succinctly describe the different use cases?
Idea from Stephan and Giselle: Having a figure which shows where Restate would sit in the tech stack wrt to other components.
We merged a variant of the overview page via https://github.com/restatedev/documentation/commit/85bd9bb2c132f43dc2e1c14552e5b62b743edb30
@tillrohrmann I guess we can close this issue then?
Yes, let's close it.
Do you have a concrete idea what should go onto the general overview page? The building blocks Restate offers to users (reliable messaging, state, durable execution)?