v0.9.2

Full Changelog: v0.9.1...v0.9.2

v0.9.1

Full Changelog: v0.9.0...v0.9.1

v0.9.0

Restate 0.9.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. This release focuses on improving the developer experience and we highly recommend looking at our new documentation and new examples.

Enjoy the release and give us feedback on discord to further improve Restate!

Notable improvements

• Restate is now configured using the TOML format and allowing hot reloads to change Restate's behavior w/o restarting it. Check out the configuration documentation for more details.
• Restate now exposes many more metrics telling you what is going on under the hood.
• Restate's internals have been reworked to support a distributed execution very soon.

Breaking changes

The new release contains a few breaking changes that require you to start the server with a clean storage directory.

What's Changed

• Move admin and meta component into cluster controller role by @tillrohrmann in #1180
• Eks pod identity implementation by @jackkleeman in #1197
• Task Center init by @AhmedSoliman in #1181
• TaskCenter all the things by @AhmedSoliman in #1194
• Typo fix by @AhmedSoliman in #1195
• Move Rocksdb back to upstream by @AhmedSoliman in #1196
• Rename cluster controller role into admin role by @tillrohrmann in #1198
• Unify metadata version type and remove nodes config singleton by @AhmedSoliman in #1200
• MetadataManager init by @AhmedSoliman in #1202
• Consolidate Services by @AhmedSoliman in #1203
• Let PartitionProcessor and Consensus module use restate_wal_protocol::Envelope by @tillrohrmann in #1204
• Move common to node-services by @AhmedSoliman in #1211
• move restate-task-center to restate-core by @AhmedSoliman in #1212
• Move metadata to restate-core by @AhmedSoliman in #1213
• metadata() for global metadata access by @AhmedSoliman in #1214
• Send ingress responses directly to ingress by @tillrohrmann in #1215
• Support adding tracing metadata via env var by @jackkleeman in #1206
• Split invocation status in invocation status/service status, Change keying of journal to invocation id by @slinkydeveloper in #1169
• Bump service protocol repo by @slinkydeveloper in #1238
• Update pinned tikv-jemallocator to fix CI by @jackkleeman in #1234
• Introduce new API to resolve ComponentMetadata by @slinkydeveloper in #1229
• New Ingress by @slinkydeveloper in #1236
• Support the new Component data model in the schema registry by @slinkydeveloper in #1241
• Propagate key in StartMessage by @slinkydeveloper in #1247
• Add tokio feature to hyper-util by @slinkydeveloper in #1252
• [2/n] Introduce node-protocol by @AhmedSoliman in #1242
• [3/n] Stub networking and network sender by @AhmedSoliman in #1243
• [4/n] TestCoreEnv helper for testing with restate-core by @AhmedSoliman in #1244
• [5/n] Streaming node-to-node networking infrastructure by @AhmedSoliman in #1245
• Add PartitionTable metadata by @AhmedSoliman in #1256
• Replaces the consensus module with Bifrost by @tillrohrmann in #1253
• Add helm chart by @jackkleeman in #1267
• Helm chart should use 0.8.1 image by @jackkleeman in #1270
• Add charts to dockerignore by @jackkleeman in #1271
• Interface refactor by @slinkydeveloper in #1248
• TestEnv support for mock networking by @AhmedSoliman in #1264
• Networking metrics by @AhmedSoliman in #1268
• Ingress dispatcher is concurrent and integrated with bifrost by @AhmedSoliman in #1269
• Add jitter to retries by @AhmedSoliman in #1274
• Cleanup Protobuf bits of schema registry by @slinkydeveloper in #1273
• More terminology changes in tables by @slinkydeveloper in #1283
• Remove Virtual journal by @slinkydeveloper in #1287
• Simplify Input and output entries by @slinkydeveloper in #1282
• Headers passthrough by @slinkydeveloper in #1286
• Fix Response error code data model by @slinkydeveloper in #1290
• Initial metadata store trait specification by @tillrohrmann in #1288
• Replace target with restate-data as the default storage directory by @tillrohrmann in #1277
• Update links in errors wrt new documentation structure by @tillrohrmann in #1293
• Improve Admin API by @slinkydeveloper in #1289
• Misc Improvements by @AhmedSoliman in #1301
• Add single node MetadataStore implementation by @tillrohrmann in #1291
• Initial local loglet implementation by @AhmedSoliman in #1302
• Integrate local metadata store into the Node by @tillrohrmann in #1307
• Fetch or insert fixed partition table by @tillrohrmann in #1309
• Move scheduling of delayed ServiceInvocations from caller PP to callee PP. by @slinkydeveloper in #1306
• Enables toml configs by @AhmedSoliman in #1320
• [1/n] Use snake_case for all configuration enums by @AhmedSoliman in #1321
• [2/n] Bifrost provider configuration improvements pt1 by @AhmedSoliman in #1322
• [3/n][Config] Flatten top-level options into CommonOptions by @AhmedSoliman in #1325
• [4/n] Partial refactor of worker and admin role configs by @AhmedSoliman in #1328
• Remove FullInvocationId as dependency to send invocation responses by @slinkydeveloper in #1331
• Remove built in service registration by @slinkydeveloper in #1304
• Add IdempotencyTable and modify InvocationStatus table by @slinkydeveloper in #1326
• Send output on InvokerEffectKind::End by @slinkydeveloper in #1335
• Merge worker-api with worker crate by @AhmedSoliman in #1330
• SIGUSR1 dumps the current config to logs by @AhmedSoliman in #1346
• Remove serde feature from restate-types by @tillrohrmann in #1340
• Store logs configuration in metadata store by @tillrohrmann in #1338
• Add EpochTable and integrate with existing code by @tillrohrmann in #1332
• New config types in restate-types by @AhmedSoliman in #1350
• A new config loader that can monitor config changes by @AhmedSoliman in #1351
• Invoker StatusReader now uses a different channel for status propagation by @slinkydeveloper in #1360
• Request identity v1 implementation by @jackkleeman in #1349
• task_center now owns the runtime and uses new config by @AhmedSoliman in #1352
• Tracing using new configuration with filter hot-reload support by @AhmedSoliman in #1353
• Bifrost to hold on to metadata by @AhmedSoliman in #1356
• arc-util non-blanket impl by @AhmedSoliman in #1358
• migrate bifrost to new config by @AhmedSoliman in #1359
• Migration to the new configuration by @AhmedSoliman in #1362
• InvocationStatus::Inboxed by @slinkydeveloper in #1334
• Update AWS dependencies by @j...

v0.8.1

What's Changed

• Patch google/protobuf/descriptor.proto and dev/restate/ext.proto by @tillrohrmann in #1263

Full Changelog: v0.8.0...v0.8.1

v0.8.0

Restate 0.8.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. Enjoy the release and give us feedback on discord to further improve Restate!

Notable improvements

• Introducing versioning information to our IDs and our stored data to support forward-compatible migrations in the future.
• Faster discoveries by distinguishing between retryable and non-retryable errors
• Support for grpc.reflection.v1.ServerReflection which is used by newer grpcurl versions.
• Usage of jemalloc to prevent heap fragmentation.

Breaking changes

The new release contains a few breaking changes which require you to start the server with a clean storage directory.

• Introducing a new format for our IDs which makes it future-proof for changes.q

Full Changelog: v0.7.1...v0.8.0

v0.7.1

Fixes

• Backported #1112 to v0.7.0. This resolves an issue where arm64 musl binaries would occasionally panic

v0.7.0

Restate 0.7.0 is here 🎉

The latest Restate release comes with a ton of new useful features for you. Enjoy the release and give us feedback on discord to further improve Restate!

New features

• The Restate CLI is here. It provides a much simpler interaction with a running Restate server and advanced introspection and observability of what is happening.
• We are now offering project templates with which you can get a Restate project bootstrapped with a single command via the CLI: restate examples typescript-hello-world-lambda.
• Stopping running invocations which are no longer of interest or stuck is now possible with invocation cancelations and invocation killings. Cancelations even allow to keep your system state consistent by running compensations.
• Deploying Restate to the cloud with one click via restate-cdk. Learn more about Restate's CDK support.

Notable improvements

• We are now offering new ways to install Restate's CLI and server:
  • CLI
    • via Homebrew: brew install restatedev/tap/restate
    • via npx: npx @restatedev/restate
  • Server
    • via Homebrew: brew install restatedev/tap/restate-server
    • via npx: npx @restatedev/restate-server
  • Check out our new download page for more information.
• We started improving Restate's performance which lead to noticeable throughput improvements.

Breaking changes

The new release contains a few breaking changes which require you to start the server with a clean storage directory.

• Extending the Restate protocol to make it support future use cases
• Fixing a problem in the timer keys which lead to wrong binary orderings
• Renaming service endpoints to service deployments which led to new REST paths

Full Changelog: v0.6.0...v0.7.0

v0.6.0

Breaking changes

• Due to some breaking changes to the metadata storage format, we recommend existing users to start with a new cluster and wipe all existing state.
• We have restricted the service key format for keyed services to only string keys. If you have any feedback about this change, let us know here #955

New features

• We now have a Java SDK to build Restate applications: https://docs.restate.dev/quickstart
• We now expose the table of the enqueued invocations in the sql introspection interface as sys_inbox
• We're publishing the container images on https://hub.docker.com/r/restatedev/restate

Notable changes

• Now the Admin API expose more metadata about service endpoints.
• Improved DELETE /invocations/:id command

We've also included some bug fixes and small improvements.

Enjoy!

Full Changelog: v0.5.1...v0.6.0

v0.5.1

Fixes

• Enable the strictest sync mode for RocksDB's WAL.
• Extend sys_status and sys_invocation_state with endpoint_id to make tables more expressive

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Breaking changes

• Due to some breaking changes to the metadata storage format, we recommend existing users to start with a new cluster and wipe all existing state.

New features

• You can now invoke Lambdas directly by providing an ARN during discovery; an API gateway is no longer needed. See https://docs.restate.dev/services/deployment/lambda to see how!

We've also included some bug fixes and small improvements.

Enjoy!

Full Changelog: v0.4.0...v0.5.0