v0.15.0

Please ensure to terminate all running workers prior to upgrading to version 0.15.0. This is crucial because prior versions earlier than 0.15.0, are unable to deserialize messages produced by the new version 0.15.0.

🚀 New Features

• Add support for JsonView
• Workers can now be created from a YAML String, through the fromConfigYaml static method
• All configuration objects (PulsarConfig, MySQLConfig, RedisConfig, PostgresConfig, CaffeineConfig...) can now be manually created through builders.
• serviceDefault, workflowDefault, defaultStorage can now be manually registered in Workers

🚨 Breaking Changes

• Serialization:

  • Both serialization of arguments and deserialization are now conducted in accordance with the types defined in the interfaces. This contrasts with our prior implementation, which performed these operations based on the actual type of objects involved.
  • The revamped approach broadens applicability, aptly resolving the concerns cited in issue #80. Nonetheless, when faced with situations involving polymorphism, the responsibility now lies with the user to furnish deserializers with adequate information.

• Worker: configuration file:

  • The configuration parameters, brokerServiceUrl and webServiceUrl, must now be explicitly specified in PulsarConfig. Previously, the system would default to the settings of a local Pulsar cluster when these values were not provided. Despite its convenience in local development, this implicit default behavior could potentially lead to complications while deploying the project in a production environment.
  • In the configurations for workflows and workflowDefault, we have revised the property name workflowEngine to stateEngine. We believe this new terminology more accurately reflects the function of this property.
  • The configuration for cache now needs to be nested within the storage configuration. This update aligns logically with the intended usage, as the cache is exclusively utilized for storage-related functions.
  • The execution policy for tasks has been revised: by default, failed tasks will no longer be subject to automatic retries. To implement retry functionality, users are required to explicitly configure a retry policy. We believe this change will help alleviate potential confusion for new users, who may be perplexed by tasks appearing to fail after 10 minutes due to the previously implicit retry mechanism.
  • Renaming all config files by putting a Config suffix on them.

• Worker: manual registration of Service and Workflow:

  • registerService method is now registerServiceExecutor for consistency
  • registerWorkflowExecutor now uses a factory as parameter instead of a class name

• Workflows behavior: the use of Deferred objects in workflow properties or arguments is now prohibited. Should a Deferred object appear in these contexts, an explicit exception will be thrown. This measure was put into place due to some issues identified in certain edge cases of the previous implementation. More importantly, allowing the transmission of Deferred objects to other workflows seems wrong.

🔬 Improvements

• Add compression info to logging at worker start
• Add log message for existing workflow with same customId tag
• Improve performance by adding a cache to Method and Class introspection that occurs at each task and workflow processing
• Add more test to ensure that backward compatibility

🪲 Bug Fixes

• Fix #254 An exception raised directly in the workflow does not appear in logs
• Fix #242 serviceDefault is not used for manually registered services
• Fix #248 Ignore annotation can not be used in Java
• Fix #80 Can not return a list, map, set from tasks and workflows

v0.14.1

🚀 New Features

• Users can now update the object mapper for fine-grained control of serialization.
• Fix #233 - Introduced keySetTable and keyValueTable settings for storage configuration, allowing custom names for storage tables.

🚨 Breaking Changes

• Renamed Task.set to Task.setContext.
• workflowId, workflowName, methodId, methodName, tags, and meta are now static properties of the Workflow class.

🔬 Improvements

• Enhanced the and operator for Deferred.

🪲 Bug Fixes

• Fix #239

v0.14.0

🚀 New Features

• Added PostgreSQL support for storage (tested on PG 16).
• Expanded storage options for MySQL with the following HikariConfig properties: minimumIdle, idleTimeout, connectionTimeout, and maxLifetime.

🚨 Breaking Changes

• In storage configuration, the maxPoolSize option has been replaced by maximumPoolSize to ensure consistency with HikariConfig properties.

🔬 Improvements

• To improve the detection of configuration issues, a warning is now emitted the first time a message is produced on a topic without a consumer.

• Resources are now properly closed when worker initialization fails.

• MySQL tests are now done on version 8.3

• Updated the versions of the following dependencies:

  • Avro (1.10.0 to 1.10.1)

v0.13.3

🔬 Improvements

• Can use immutable metadata when dispatching tasks

• Use Kotlin 2.0.0

• bump libraries version

  • kotlinx-coroutines from 1.8.0 to 1.8.1
  • fasterxml.jackson from 2.17.0 to 2.17.1
  • kotest from 5.8.1 to 5.9.0
  • testcontainers from 1.19.7 to 1.19.8bump
  • mockk from 1.13.10 to 1.13.11
  • avro4k from 1.10.0 to 1.10.1
  • slf4j from 2.0.12 to 2.0.13
  • kotlin-logging-jvm from 6.03 to 6.0.9

• target Java version 17

Full Changelog: v0.13.2...v0.13.3

v0.13.2

🪲 Bug fixes

• Fix #227

Full Changelog: v0.13.1...v0.13.2

v0.13.1

🚨 Breaking changes

• The new default setting for cache is no cache
• Workflow and Service names are now escaped in topic's name - it's a breaking change only in the unlikely situation where you have special characters in those names

🔬 Improvements

• Pulsar version is now 3.0.4 (from 2.11.2)
• Workflow Tasks are processed on a key-shared subscription. This allows new workflow versions to be deployed continuously.
• Improve test coverage for tags
• Improve test coverage for infinitic-transport-pulsar module
• Client's topics are now deleted when clients are interrupted.
• Client's topics are not recreated by producers if already deleted
• Bump version of dependencies:
  • CloudEvents (2.5.0 to 3.0.0)
  • Jackson (2.15.3 to 2.17.0)
  • java-uuid-generator (4.3.0 to 5.0.0)
  • Kotest (5.8.0 to 5.8.1)
  • TestContainers (1.19.5 to 1.19.7)
  • Mockk (1.13.8 to 1.13.10).
  • commons-compress (1.25.0 to 1.26.1)

🪲 Bug fixes

• Fix backward compatibility with 0.12.3 (in 0.13.0, some messages were wrongly discarded, leading to stuck workflows)
• Fix a bug introduced in 0.13.0 that led to the possible creation of multiple workflow instance with the same customId tag
• "none" cache setting now correctly means no cache, previously if was the default cache

Full Changelog: v0.13.0...v0.13.1

v0.13.0

DO NOT UPGRADE

This version includes a backward compatibility fixed in version 0.13.1.
We recommend upgrading directly to version 0.13.1 from 0.12.3 or below.

🚀 New features

• CloudEvents (beta): Infinitic now expose its events in CloudEvents json format. This allow users to build their own dashboards, logs, or even add hooks to some specific events.

  Examples of events exposed are:

  • for methods of workflows: startMethod, cancelMethod, methodCanceled, methodcompleted, methodFailed, methodTimedOut
  • for tasks within workflows: taskDispatched, taskCompleted, taskFailed,taskCanceled, taskTimedOut
  • for workflows within workflows: remoteMethodDispatched,remoteMethodCompleted,remoteMethodFailed,remoteMethodCanceled,remoteMethodTimedOut.
  • for the workflow executor itself (also called WorkflowTask) executorDispatched, executorCompleted, executorFailed

  Each event is accompanied by relevant data, such as the error details for a taskFailed event or the arguments for a remoteMethodDispatched event.

  This feature is currently in beta and may be refined based on user feedback.

• Delegated Tasks: In certain cases, tasks cannot be processed directly by a worker, and instead, the task invokes another system for processing, typically through an HTTP call. If the external system can process the task synchronously and return the output (or report a failure), the process works smoothly. However, if the external system cannot provide a synchronous response, the situation becomes ambiguous, leaving Infinitic without a clear indication of whether the task has been completed or failed, nor an ability to retrieve the result. Starting with version 0.13.0, Infinitic introduces a "delegated task" feature. This feature, enabled through an annotation on the task, informs Infinitic that the method's completion does not signify the task's completion and that it should await asynchronous notification of the task's outcome. To support this functionality, a new completeDelegatedTask method has been added to the InfiniticClient.

• InfiniticWorker now offers new methods that allow for the programmatic registration of services and workflows, bypassing the need for configuration files. While initially used for internal testing, this feature can also be beneficial in scenarios where using configuration files is impractical.

🚨 Breaking changes

• The context property of the Task singleton, which was accessible during task execution, has been removed due to its redundancy with other properties.

• In workers,

  • the method registerService has been replaced by 2 methods registerServiceExecutorand registerServiceTagEngine.
  • the method registerWorkflow has been replaced by 3 methods registerWorkflowExecutor, registerWorkflowTagEngine, and registerWorkflowStateEngine.

• The following libraries are no longer exposed by Infinitic. If you were using them, you must now add them to the dependencies of your project:

  • org.jetbrains.kotlinx:kotlinx-serialization-json
  • com.jayway.jsonpath:json-path
  • com.sksamuel.hoplite:hoplite-core

🔬 Improvements

• Infinitic has been updated to use UUID version 7. These are sortable UUIDs that include a timestamp, which is expected to enhance performance when used as primary keys in databases.
• Idempotency: In scenarios where hardware or network issues occur, there's a possibility that the same tasks may be processed multiple times. Ultimately, it falls upon the user to ensure tasks are designed to be idempotent as required. Starting from version 0.13.0, the taskId can be reliably used as an idempotent key. This is because Infinitic will generate the same value for taskId, even if the task creation process is executed repeatedly.
• Performance Improvement: Prior to version 0.13.0, initiating a workflow involved sending a message to the workflow engine, which would then create an entry to store its state in the database. Following this, it would send another message to commence the workflow execution in order to identify and dispatch the first task. This task information would be relayed back to the engine for dispatch. The drawback of this approach was evident during surges in workflow initiation (for example, 1 million starts), where Infinitic had to sequentially store 1 million state entries before beginning to process the first task. This could significantly delay the start of task processing in practical scenarios. Since the release of version 0.13.0, the execution process has been optimized. Now, the first task is processed immediately upon dispatch by all available workers, substantially reducing the "time to first execution."
• Worker Graceful Shutdown: Infinitic is designed to ensure no messages are lost and that workflow executions continue under any circumstances. However, prior to version 0.13.0, shutting down a worker could result in a significant number of duplicated messages or actions. This was because the worker could close while still sending multiple messages. With the introduction of version 0.13.0, workers now attempt to complete any ongoing executions before shutting down, with a default grace period of 30 seconds. This duration can be adjusted using the new shutdownGracePeriodInSeconds setting in the worker configuration.
• Worker Quicker Start: Upon startup, a worker verifies the existence of the tenant, namespace, and necessary topics for the services and workflows it utilizes, creating them if necessary. Previously, this setup was performed sequentially. Now, it is executed in parallel, significantly reducing startup time, especially in scenarios where a worker is responsible for managing a large number of tasks or workflows.

🪲 Bug fixes

• Fix false warning about topics being partitioned
• Fixed the behavior of getSecondsBeforeRetry, which defines the task retry strategy. When the value is less than or equal to 0, retries will now occur immediately. Previously, no retry would be attempted in this scenario.
• If the methodId is not specified when using CompleteTimers client method, all timers of the workflow will now be completed. Previously, only the timers on the main method were completed in the absence of a specified methodId.

v0.12.3

🚀 New features in worker's configuration file

• A new configuration option maxPoolSize has been introduced to the MySQL storage configuration. This option allows you to specify the maximum number of connections in the connection pool.
• The tagEngine setting can now be configured under serviceDefault.
• The tagEngine and workflowEngine settings can now be configured under workflowDefault.

🚨 Breaking changes

• The entries service and workflow in the worker configuration, which were used to establish default values for services and workflows, have been renamed. The updated names are serviceDefault and workflowDefault, respectively.

🔬 Improvements

• Not being able to check tenant / namespace does not trigger an error anymore.

v0.12.2

🔬 Improvements

• Restore config files as data classes instead of interfaces
• Restore fromConfig method for clients and workers
• Improve worker logging

Full Changelog: v0.12.1...v0.12.2

v0.12.1

🚀 New features

• WithTimeout interfaces on Workflows interfaces can now be used to define global timeouts

🪲 Bug fixes

• Fix Json Serialization of WorkflowTask parameters and return value for previous versions
• Fix GetIds on client for inMemory implementation

🔬 Improvements

• WorkflowTask parameters and return value are now serialized using avro with schema fingerprint - this will improve future backward compatibilities

Full Changelog: v0.12.0...v0.12.1