Viewing profile — mfateev

That sounds like an excellent use for narrow boring company tunnels.

I don't believe in visual programming ever replacing code for general programming. However, many examples exist when visual programs work for narrow domain-specific applications. T…

Do you know about the Temporal startup program? It gives enough credits to offset support fees for 2 years. https://temporal.io/startup

Every step of the workflow is durably recorded. So you have the full information about the exact state of each workflow. To troubleshoot, you can even download the event history an…

temporal.io just released .NET SDK. The observability and scalability of the platform is really good. Disclaimer: I'm one of the founders of the project.

Check out temporal.io. It has support for schedules as well.

Check out temporal.io that fully abstract this. Disclaimer, I'm one of the founders.

State machines are useful when the same input/event requires different handling based on the current state. There are not that many applications when this is true. Most of the time…

Yes, Temporal workflows are as dynamic as needed. The other useful pattern is always running workflows that can be used to model lifecycle of various entities. For example you can …

The main difference is that workflows are written as code in a general purpose programming language. Java, Go, Javascript/Typescript and PHP are already supported. Python and .NET …

Look at the temporal.io. It is essentially a BPM system that uses Go (as well as Java/PHP/Typescript) to specify business process. And a queue + DB is never simpler for such scenar…

I think we are in agreement here. Temporal does exactly what you described. It uses queues to transporting tasks to processes. But it completely hides them from the business proces…

I think queues are the wrong abstraction to model business processes. That's why a trivial issue like a non recoverable failure during processing a message becomes such a headache.…

temporal.io provides much higher level abstraction for building asynchronous microservices. It allows one to model async invocations as synchronous blocking calls of any duration (…

A lot of startups these days support early exercise or extend the post termination exercise period from 90 days to much longer period like 10 years. So there is no need to stay wit…

Temporal takes much simpler approach to updating code while a program is running. For any code update, it keeps both old and the new version of the code. Then it uses the old code …

Google is mimicking perforce command line. The backend is 100% proprietary. Microsoft is based on Git, but with a lot of engineering on top of it: https://devblogs.microsoft.com/bh…

AWS DynamoDB is multi-AZ and is strongly consistent (at least for a single key update). I believe you confused it with a Dynamo DB described in a paper Amazon published long ago. A…

> I also used to use Microsoft's Windows Workflow Foundation to do similar things. Essentially you're sketching a workflow process skeleton and then managing the state atomically b…

I'm one of the original creators of temporal.io open source project. Long time ago I worked with an internal Amazon workflow engine that was based on Petri nets. It worked, but I l…

temporal.io

Great, show me a single product (besides AWS SWF and Azure durable Task Framework) that has the programming model of Temporal. For example, which product allows to write production…

temporal.io supports task heartbeating. An application specific data can be attached to each heartbeat. The data is accessible from outside to display the progress in the UI for ex…

Did you click on temporal.io? It is hard to describe as it is a new way to build distributed applications that doesn't have a commonly agreed name yet.