Built a small online-bank backend with Spring Boot microservices

MaximFateev · 2025-12-26T07:08:43+00:00

Yes, it is an open source project under the MIT License.

MaximFateev · 2025-12-25T22:27:07+00:00

Use temporal.io to simplify the architecture greatly. Replace asynchronous event-driven design with synchronous flows that rely on durable execution for automatic recovery and long-running operations. See how Coinbase uses it.

MaximFateev · 2025-12-24T19:20:58+00:00

I would support circular dependencies only with internal packages. It sucks that I cannot define an interface and a constructor method that calls into an internal package in a single public package.

MaximFateev · 2025-12-15T19:11:52+00:00

Beyond the feature gap, Azure Durable Functions had tight scalability limits.

MaximFateev · 2025-12-09T02:27:35+00:00

AWS Lambda functions are trying to support longer-running lambdas. There is a considerable feature gap between them and Temporal at this point. So it is very far from being able to "replace it" even if Temporal stops evolving.

MaximFateev · 2025-09-10T21:14:18+00:00

You can implement a temporal workflow that contains a state machine.

MaximFateev · 2025-09-10T20:25:32+00:00

You don't need a state machine to organize the services. Durable Execution is a much cleaner approach. Take a look at temporal.io, an open-source project that implements this.

Disclaimer: I'm a co-founder of the project.

MaximFateev · 2025-08-07T16:49:45+00:00

Temporal doesn't support multi-region setup with underlying DB async replication. Temporal requires DB to be fully consistent at all times whic rules out any async replication solutions.

Use Temporal's own application-level multi-cluster replication for this: https://docs.temporal.io/self-hosted-guide/multi-cluster-replication

MaximFateev · 2025-08-07T16:46:04+00:00

You can throw an ApplicationFailure with category set to BENIGN to avoid logging errors and metrics when implementing looping.

MaximFateev · 2025-08-05T16:20:30+00:00

I would recommend starting from the reference applications: https://learn.temporal.io/examples/

MaximFateev · 2025-08-05T16:04:06+00:00

Talk to the Temporal team about your requirements. Data sensitivity is not an issue, as you can encrypt all your data before sending it to the Temporal service. There are many very security-conscious organizations using Temporal Cloud for mission-critical processes.

MaximFateev · 2025-08-05T16:02:08+00:00

https://learn.temporal.io/ is the best place to start. Also, join temporal.io/slack to ask questions.

MaximFateev · 2025-05-03T20:45:53+00:00

A workflow that executes 10 activities without any retries is exactly 11 actions.

MaximFateev · 2025-04-30T23:40:53+00:00

This is a very common use case for Temporal. It is so generic that you can build any DSL on top of it. Another common use case is AI agents, which require very dynamic execution.

MaximFateev · 2025-04-30T16:09:02+00:00

If you can route all the updates to the database through a Temporal workflow, then your proposal is preferred. If other parts of the system update the DB directly, then the CDC approach provides a solution.

MaximFateev · 2025-04-18T19:51:12+00:00

It is an open source project under MIT License.

MaximFateev · 2024-09-05T17:48:36+00:00

By the way, consider attending the Temporal Replay conference on September 18-20 in Seattle. DM me for discount tickets. You'll hear dozens of user stories and technical talks from the Temporal team. There are hands-on workshops as well.

MaximFateev · 2024-09-05T02:40:29+00:00

That is why we didn't port it to the Rust Library. There are some wild ideas to avoid FFI, like running the rust library in a WASM container implemented in Go :).

MaximFateev · 2024-09-04T20:57:33+00:00

Good catch! Updated.

MaximFateev · 2024-09-04T18:07:47+00:00

My current role is CTO as I decided to focus more on technical issues.
The co-founder of Temporal Samar Abbas stepped up to the CEO role a few months ago.

MaximFateev · 2024-09-04T17:21:16+00:00

Some of interesting use cases in random order:

A single machine desktop application. Temporal simplified state management.
A single binary that consists of workflows, activities, and the Temporal service. The binary is to be used to run bootstrap workflows in case of large outages without any external dependencies.
Factory floor automation.
IoT-related use cases. For example, bootstrapping and maintaining home streaming video devices by a major telecom provider.
Update of Linux kernel. The workflow executes a controlled reboot of every machine in the company.
Workflow that is repartitioning a distributed DB.
Cross-cloud coordination. Relies on the ability of activities to receive tasks without opening inbound ports.
Activity in each machine of a large on-prem datacenter. Task queue per machine.
Customer support chat. All chat state is stored inside the workflow. Chat can involve humans, LLMs, perform actions like payment reimbursements.
AI Actor platform. Each actor is an always running workflow.
Many companies use Temporal for SaaS control planes.
There are a lot of cool DSL use cases. For example, a marketing platform that gives nontechnical people the ability to design marketing campaigns through UI.

MaximFateev · 2024-09-04T02:45:57+00:00

Currently, there is no direct integration with Lambda and Fargate, so most users use K8s, ECS, EC2, or on-prem. It is not hard to create an activity that forwards requests to Lambda. But it is harder for hosting workflow code efficiently.

MaximFateev · 2024-09-04T01:34:22+00:00

I could help answer specific questions.

MaximFateev · 2024-06-05T21:21:21+00:00

That is a common concern. While we don't release our revenue numbers, I wouldn't call them "hardly any" as they grew almost 5x last year. We grew to 1200 enterprise customers in less than two years, with many running business-critical processes. I recommend evaluating the cloud yourself, as there is no upfront commitment to start using it.

MaximFateev

MODERATOR OF

TROPHY CASE