You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2026-01-13-cadence-in-2025/2026-01-13-cadence-in-2025.md
+36-14Lines changed: 36 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,15 +10,15 @@ date: 2026-01-13T16:00
10
10
11
11
# Cadence OSS Update: 2025 Lookback
12
12
13
-
Hi Cadence Community,
13
+
Hi Cadence Community,
14
14
15
-
At the beginning of every year, we share about what happened in the last year. Here’s a look-back to our 2025 improvements, explaining what’s new, and how you can use them. 2025 was one of the most exciting years for the Cadence project and we hope this will only get better in the future. Here are some highlights:
15
+
At the beginning of every year, we share about what happened in the last year. Here’s a lookback at our 2025 improvements, explaining what’s new, and how you can use them. 2025 was one of the most exciting years for the Cadence project and we hope this will only get better in the future. Here are some highlights:
As a sign of our open source commitment, [the Cadence project joined Cloud Native Computing Foundation](https://cadenceworkflow.io/blog/2025/10/06/cadence-joins-cncf-cloud-native-computing-foundation) under Linux Foundation. This is a very exciting moment for the entire project where we are moving to an entirely new plane. Similarly, we opened [our governance](https://cadenceworkflow.io/community/governance) to our users who would like to be a part of the journey.
21
+
As a sign of our open source commitment, [the Cadence project joined the Cloud Native Computing Foundation](https://cadenceworkflow.io/blog/2025/10/06/cadence-joins-cncf-cloud-native-computing-foundation) under the Linux Foundation. This is a very exciting moment for the entire project where we are moving to an entirely new plane. Similarly, we opened [our governance](https://cadenceworkflow.io/community/governance) to our users who would like to be a part of the journey.
22
22
23
23
Our ambition is to help everyone build complex distributed systems as easily as possible and cover as many overheads in such processes as possible so engineers can get maximum value out of the Cadence project. While there’s still a lot to do to achieve that, this milestone brings us one big step closer.
24
24
@@ -31,16 +31,16 @@ We are aware that platforms like Cadence aren't the cheapest option for some use
31
31
32
32
Similar studies were [published](https://www.instaclustr.com/blog/cadence-vs-temporal-understanding-workflow-orchestration-and-temporal-cloud-pricing/) by our partners at Instaclustr by NetApp®, selling managed Cadence as a solution.
33
33
34
-
We planned several more improvements in 2026 which might come with similar savings on top of the savings from this year. Stay tuned\!
34
+
We have many more improvements planned for 2026, which we expect to bring similar savings. Stay Tuned!
Tasklists are queues where workflow tasks are dispatched to user workers. They are hosted in our matching service. By default a single tasklist lives in a single matching host. However, if a tasklist's traffic is large enough, our users used to define how many partitions they would need to have. Upon their changing traffic, they needed to keep adjusting their partitions as well.
39
+
TaskLists are a FIFO queue used to dispatch tasks to Workers. They are hosted in our matching service. By default a single tasklist lives in a single matching host. However, if a tasklist's traffic is large enough, our users used to define how many partitions they would need to have. Upon their changing traffic, they needed to keep adjusting their partitions as well.
40
40
41
-
As it reads, that’s not the most efficient way to manage thousands of domains. Even with a single domain, this model required Cadence users to learn internal limits about Cadence services and came with unpleasant operational load. Even when this is well-established, manual tuning was almost guaranteed to be suboptimal: you’d either be under utilized or you would accumulate tasks due to not being able to keep up with them.
41
+
As it reads, that’s not the most efficient way to manage thousands of domains. Even with a single domain, this model required Cadence users to learn internal limits about Cadence services and came with unpleasant operational load. Even when this is well-established, manual tuning was almost guaranteed to be suboptimal: you’d either be underutilized or you would accumulate tasks due to not being able to keep up with them.
42
42
43
-
Therefore, we made our partitioning logic completely adaptive where \# tasklist partitions automatically grow and shrink based on incoming traffic, providing the perfect scale. In a similar approach, we plan to make as many configurations as possible adaptive soon.
43
+
Therefore, we made our partitioning logic completely adaptive where the number of TaskList partitions automatically grow and shrink based on incoming traffic, providing the perfect scale. We want Cadence to be as adaptive and easy to operate as possible.
44
44
45
45
## History Queues v2
46
46
@@ -62,7 +62,7 @@ Cadence domains have been running in active-passive mode for years, which has be
62
62
63
63
The best part of this feature is that switching to active-active mode won’t require any migration. All domains will support active-active by default and without breaking existing behavior. While users setting “cluster attributes” while starting their workflows will be able to benefit from active-active processing; leaving these parameters empty will retain the old active-passive behavior.
64
64
65
-
This feature is currently implemented for Cassandra and the support for other DBs will come in Q1. We will also release a blog explaining how this improved related use cases, a wiki explaining how to use it and a code lab to help you try out.
65
+
This feature is currently implemented for Cassandra and the support for other DBs will come in Q1. We will also release a blog explaining how this improved related use cases, a wiki explaining how to use it and a codelab to help you try out.
66
66
67
67
## Cadence Python SDK
68
68
@@ -91,10 +91,32 @@ Given that replication is a continuous process between Cadence regions, we imple
Another area we have been focusing on was user education. This is needed for both Cadence basics or new features. For every major new feature, we are now releasing Blogs explaining the impact of the feature, wikis explaining how to use, codelabs going over instructions and videos showing our developer advocate going over the codelab so you won’t get confused or stuck at a certain step.
Earlier in the year, we released [cadence-web v2](https://cadenceworkflow.io/blog/2025/04/11/2025-04-11-announcing-cadence-web-v4/announcing-cadence-web-v4). It was a complete rewrite from the previous version. We migrated from Vue.js to React, completely redesigned the UI, added multi environment support, and improved the performance significantly.
99
+
100
+
With the new changes, extending cadence-web became much simpler as you can see with the changes mentioned below.
101
+
102
+
## New History Page
103
+
104
+

105
+
Meet the new Workflow History page in the Cadence UI! It offers significant enhancements in performance, visibility, and navigation. Key improvements include much faster loading, color-coded events, and a new navigation bar, making it much simpler to locate workflow failures and stuck activities.
106
+
94
107
## Workflow Actions in Cadence-Web
95
108
96
109

97
-
Cadence-Web is our web component which provides a user interface to view and manage Cadence workflows. One of the many features we added to cadence-web in 2025 was the ability to directly start or signal workflows from UI. This especially helped with running the initial start command for the cron workflows or internal tools waiting for user inputs.
110
+
Cadence-Web is our web component which provides a user interface to view and manage Cadence workflows. One of the many features we added to cadence-web in 2025 was the ability to directly start or signal workflows from UI. This especially helped with running the initial start command for the cron workflows or internal tools waiting for user inputs.
One of the top question categories in our support channels is about diagnosing workflow failures. Most of the issues are repeating patterns that can be easily identified by experienced Cadence users. However, this may not be that obvious to new users.
116
+
117
+
In 2025, we decided to proactively show issues about workflows in the workflow summary tab where users can click details to learn more. This both reduced the number of support questions we were receiving and also helped our users self-resolve their issues a lot faster.
118
+
119
+
There’s a codelab and the tutorial video available for this feature if you’d like to try!
98
120
99
121
## Advanced Queries with Auto-complete
100
122
@@ -103,19 +125,19 @@ Cadence provides a simple SQL language to filter and list workflows. However, it
103
125
104
126
## What's Coming in 2026?
105
127
106
-
Thanks to past investments in building a solid foundation for Cadence, we are switching our focus to following areas:
128
+
Thanks to past investments in building a solid foundation for Cadence, we are switching our focus to the following areas:
107
129
108
130
### Investing in Community
109
131
110
-
Our community has been growing faster recently and we are receiving regular contribution requests. We are aware that investing in our community will be the only way scale and build the features that our community asks. Both for users and contributors, we will have more channels and easier ways to collaborate.
132
+
Our community has been growing faster recently and we are receiving regular contribution requests. We are aware that investing in our community will be the only way to scale and build the features that our community asks. Both for users and contributors, we will have more channels and easier ways to collaborate.
111
133
112
134
### Adapting Popular Features
113
135
114
-
Are you a Cadence user but you wish a specific feature was supported? Are you considering to use Cadence but not having a specific feature is a deal-breaker? Please let us know. Our goal is to have Cadence to handle all the overheads regarding orchestration and distributed systems. Especially if this problem is already solved in somewhere else, we are happy to build and adapt them in Cadence.
136
+
Are you a Cadence user but you wish a specific feature was supported? Are you considering using Cadence but not having a specific feature is a deal-breaker? Please let us know. Our goal is to have Cadence to handle all the overheads regarding orchestration and distributed systems. Especially if this problem is already solved somewhere else, we are happy to build and adapt them in Cadence.
115
137
116
138
### Driving Innovation and Modernization
117
139
118
-
We are aiming to address the changing needs of our industry, including but not limited to areas such as agent orchestration. Some already existing features need upgrades to improve its usability, flexibility and overall experience, which will also be a part of this focus.
140
+
We are aiming to address the changing needs of our industry, including but not limited to areas such as agent orchestration. Some already existing features need upgrades to improve their usability, flexibility and overall experience, which will also be a part of this focus.
0 commit comments