Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
stsffap
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
stsffap
3y ago
We are still sorting out which SDK to implement next. Your preference for Go and Ruby is noted. The best way to stay up to date with the next developments is the GitHub issues at the moment. Creating a public product roadmap is a good idea.
32.
▲
by
stsffap
3y ago
The 0.8 release of Restate ships many new API improvements such as deterministic promise combinators, operation timeouts, better state management, and much more. Restate now supports patching service state in case you need to repair a servi
33.
▲
Release announcement: Restate 0.8 has arrived
(restate.dev)
4 points
by
stsffap
3y ago
|
3 comments
34.
▲
by
stsffap
3y ago
Yes, Restate supports registering different versions of your handler code. Restate requires that the code is still available for as long as there is an in-flight invocation of your handler for a given version. Breaking your handler/lon
35.
▲
Code that sleeps for a month: Solving durable execution's immutability problem
(restate.dev)
13 points
by
stsffap
3y ago
|
9 comments
36.
▲
by
stsffap
3y ago
Durable Execution maintains program state in a journal, and this can lead to complications when updating service code in such a way that the journal no longer makes sense. Limiting the duration that handlers run makes this immutability prob
37.
▲
by
stsffap
3y ago
Every Lambda you deploy to AWS Lambda gets a version assigned. The corresponding arn would look like `arn:aws:lambda:my-region:123456789101:function:my-function:my-version`. Once you have deployed the Lambda, you register it with Restate by
38.
▲
by
stsffap
3y ago
We are currently gathering feedback on which SDKs to prioritize next. Python has been asked for a couple of times already. Once we decide on the next SDK, we'll let you know.
39.
▲
by
stsffap
3y ago
The hardest problem in durable execution, as in many areas of infrastructure, is safe updates.
40.
▲
Solving durable execution's immutability problem
(restate.dev)
52 points
by
stsffap
3y ago
|
28 comments
41.
▲
Graceful cancellations: How to keep your application/workflow state consistent
(restate.dev)
2 points
by
stsffap
3y ago
|
1 comments
42.
▲
by
stsffap
3y ago
With graceful cancellations, it is now possible to stop service invocations and workflows while keeping the overall application state consistent.
43.
▲
Restate 0.7 Is Here
(restate.dev)
3 points
by
stsffap
3y ago
|
1 comments
44.
▲
by
stsffap
3y ago
The 0.7 release of Restate ships great new features such as the Restate CLI, one-click project templates, invocation cancellations, one-click cloud deployment, new ways to install Restate, and much more.
45.
▲
by
stsffap
4y ago
Sorry to hijack this discussion thread. I've come across your comments on https://news.ycombinator.com/item?id=28425379 and I think you have brought up some really good points what modern DBs should support. Especially
46.
▲
Stateful Functions v3.2.0: New JavaScript SDK for distributed applications
(flink.apache.org)
2 points
by
stsffap
5y ago
|
0 comments
47.
▲
by
stsffap
5y ago
Flink supports the distributed execution of code and, thus, also ML algorithms that are written like this.
48.
▲
Apache Flink ML 2.0 is released: ML for streaming data
(flink.apache.org)
22 points
by
stsffap
5y ago
|
2 comments
49.
▲
External shuffle service for Apache Flink: Speeding up batch jobs and recovery
(github.com)
1 points
by
stsffap
5y ago
|
0 comments
50.
▲
Merging Blink into Apache Flink: Unifying Batch and Stream Processing
(flink.apache.org)
4 points
by
stsffap
8y ago
|
0 comments
51.
▲
Apache Flink 1.6.0 released
(flink.apache.org)
8 points
by
stsffap
8y ago
|
3 comments
52.
▲
The Curious Case of the Broken Benchmark: Apache Flink vs. Databricks Runtime
(data-artisans.com)
14 points
by
stsffap
9y ago
|
0 comments
53.
▲
Apache Flink 1.4.0 Release Announcement
(flink.apache.org)
12 points
by
stsffap
9y ago
|
0 comments
54.
▲
Looking Ahead to Apache Flink 1.4.0 and 1.5.0
(flink.apache.org)
7 points
by
stsffap
9y ago
|
0 comments
55.
▲
Running Apache Flink Everywhere: Flink on DC/OS and Apache Mesos
(data-artisans.com)
5 points
by
stsffap
10y ago
|
0 comments
56.
▲
Apache Flink 1.2.0 Released
(flink.apache.org)
11 points
by
stsffap
10y ago
|
0 comments
57.
▲
by
stsffap
10y ago
data Artisans | ONSITE (Berlin, Germany) and REMOTE Hiring Process: Application, Phone interview, and On-site interview What: Data processing, Big Data data Artisans is building the next-generation platform for programming data-intensive ap
58.
▲
RBEA: Scalable Real-Time Analytics at King with Apache Flink
(data-artisans.com)
12 points
by
stsffap
10y ago
|
0 comments
59.
▲
by
stsffap
11y ago
As input you can basically use any Flink DataStream<T>. There are multiple ways to ingest this data into your Flink program. The most common way is to use a Flink connector for Kafka or RabbitMQ. Or you can also write your own Flink s
60.
▲
Introducing Complex Event Processing (CEP) with Apache Flink
(flink.apache.org)
150 points
by
stsffap
11y ago
|
15 comments
More ›