Skip to content

Releases: akkadotnet/Akka.Persistence.MongoDB

Release list

Akka.Persistence.MongoDB v1.5.70

Akka.Persistence.MongoDB v1.5.70 Latest
Latest

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 31 Jul 21:22
1.5.70
73a9426
This commit was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
SSH Key Fingerprint: iVjh5SZ5YkjfqFYRwG3QRFmN/cQ2eeH8d9Sv1ASS7cU
Verified
Learn about vigilant mode.

1.5.70 July 29th 2026

Bug Fix: EventsByTag now returns all tags stored with the event

Previously, EventsByTag and CurrentEventsByTag queries populated EventEnvelope.Tags with only the tag used to execute the query, losing any other tags stored alongside the event. The returned metadata now correctly includes the complete JournalEntry.Tags collection, making it independent of which tag was queried.

Changes:

  • 73a9426 docs: add PR #477 EventsByTag tag preservation fix to 1.5.70 release notes
  • 48a1c4b Add Offset.FromEnd support to MongoDB queries (#478)
  • 6cadf61 Preserve all tags in EventsByTag envelopes (#477)
  • b089c56 Bump Microsoft.NET.Test.Sdk from 17.8.0 to 18.8.1 (#473)
  • 9dc8a87 Clean up FluentAssertions remnants (#476)
  • e83e95b Bump Microsoft.SourceLink.GitHub from 8.0.0 to 10.0.301 (#474)
  • 7d41979 fix: remove FluentAssertions dependency (#465)
  • 69d7c92 fix: deterministic timeouts for 128 MB GridFS snapshot tests on Windows (#464) [ #415 ]
  • c568b09 Bump Akka.Persistence.TCK from 1.5.68 to 1.5.69 (#460)
  • 075d9d7 Bump Akka.Hosting.TestKit and Microsoft.Extensions.Hosting (#458)
See More
  • 8a90c55 Bump Akka.Persistence.TCK from 1.5.67 to 1.5.68 (#455)

This list of changes was auto generated.

Assets 4
Loading

Akka.Persistence.MongoDB v1.5.67

Akka.Persistence.MongoDB v1.5.67

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 28 Apr 20:35
1.5.67
de47dfc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.67 April 28th 2026

Changes:

  • de47dfc Update RELEASE_NOTES.md for 1.5.67 release (#445)
  • f0feb2d Bump AkkaVersion and AkkaHostingVersion from 1.5.60 to 1.5.67 (#444)
  • c13fa16 Extract only latest release block for GitHub release body (#433)

This list of changes was auto generated.

Loading

Akka.Persistence.MongoDB v1.5.60

Akka.Persistence.MongoDB v1.5.60

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 10 Feb 22:17
1.5.60
This tag was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
GPG key ID: 7DAAC25384116DD4
Verified
Learn about vigilant mode.
0a8b7ae
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.59 January 26th 2026

Performance Fix: Reduced BSON Serializer Lock Contention

Fixed a critical performance issue where concurrent persistence operations would cause high CPU usage due to lock contention in the BSON serializer. Previously, FullTypeNameObjectSerializer would repeatedly register discriminators for types that were already registered, acquiring write locks unnecessarily.

Changes:

  • Added tracking of already-registered types to skip redundant registration
  • Made FullTypeNameObjectSerializer public with a static RegisterNewTypesToDiscriminator() method for pre-registration at startup

1.5.55.1 October 29th 2025

Improved API

This release introduces the simplified Akka.Hosting 1.5.55.1 API for connectivity health checks, eliminating redundant parameter passing:

New Simplified API (Recommended):

journalBuilder: journal =>
{
    journal.WithConnectivityCheck(); // Options automatically accessed from builder
}

Previous API (Still Supported):

journalBuilder: journal =>
{
    journal.WithConnectivityCheck(journalOptions); // Explicit parameter passing
}

The new API automatically accesses options from builder.Options, making the code cleaner and less error-prone. The previous API is marked as [Obsolete] but remains functional for backward compatibility.

  • Update WithConnectivityCheck() extension methods to use simplified Akka.Hosting 1.5.55.1 API pattern
  • Upgraded to Akka.Hosting 1.5.55.1

1.5.55 October 26th 2025

Adds new WithConnectivityCheck() methods for proactive MongoDB connectivity verification with customizable tags.

1.5.53 October 16th 2025

New Feature: Health Check Support for Akka.Persistence.MongoDb.Hosting

This release adds built-in health check support for MongoDB journal and snapshot stores, integrated with Microsoft.Extensions.Diagnostics.HealthChecks. This enables monitoring and observability for your MongoDB persistence plugins.

Key capabilities:

  • Automatic health reporting for MongoDB journal and snapshot stores
  • Integration with ASP.NET Core health check endpoints
  • Configurable health status reporting (Healthy, Degraded, Unhealthy)
  • Tagged health checks for easy filtering (akka, persistence, mongodb)

Example usage:

services.AddHealthChecks(); // Add health check service

services.AddAkka("MyActorSystem", (builder, provider) =>
{
    builder
        .WithMongoDbPersistence(
            connectionString: "mongodb://localhost:27017/akka",
            journalBuilder: journal => journal.WithHealthCheck(HealthStatus.Degraded),
            snapshotBuilder: snapshot => snapshot.WithHealthCheck(HealthStatus.Degraded));
});

For complete documentation, see the Akka.Persistence.MongoDb.Hosting README and the main README.

1.5.42 May 22nd 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.40 March 27th 2025

1.5.37 January 24th 2025

1.5.32 December 23rd 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

Driver Behavior Change And Workaround

There is a behavior change in MongoDb.Driver v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.

Example:

  • Server address used in connection string: "host.docker.internal:27017"
  • Actual server address being used in MongoDb connection: "127.0.0.1:27017"

The workaround is to add "directConnection=true" in your connection string.

MongoDb.Driver Upgrade Advisories

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.32-beta1 December 5th 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.31 December 4th 2024

Version Notice

Due to breaking changes in MongoDb.Driver v3.0.0, This release will be the last Akka.Persistence.MongoDb that will support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision [here](https://www.mongodb.com/commu...

Read more
Loading

Akka.Persistence.MongoDB v1.5.59

Akka.Persistence.MongoDB v1.5.59

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 27 Jan 13:27
1.5.59
This tag was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
GPG key ID: 7DAAC25384116DD4
Verified
Learn about vigilant mode.
729db07
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.59 January 26th 2026

Performance Fix: Reduced BSON Serializer Lock Contention

Fixed a critical performance issue where concurrent persistence operations would cause high CPU usage due to lock contention in the BSON serializer. Previously, FullTypeNameObjectSerializer would repeatedly register discriminators for types that were already registered, acquiring write locks unnecessarily.

Changes:

  • Added tracking of already-registered types to skip redundant registration
  • Made FullTypeNameObjectSerializer public with a static RegisterNewTypesToDiscriminator() method for pre-registration at startup

Changes:

  • 729db07 Fix: Use windows-2022 explicitly instead of windows-latest (#431)
  • b7f42c1 Update 1.5.59 release notes to include PR #428 bug fix (#430)
  • bc149a9 Bump Akka.NET to 1.5.59 (#429)
  • 5d23e94 Avoid re-registering FullTypeNameDiscriminatorConvention (#428)

This list of changes was auto generated.

Loading

Akka.Persistence.MongoDB v1.5.30.1

Akka.Persistence.MongoDB v1.5.30.1

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 27 Jan 14:55
1.5.30.1
This tag was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
GPG key ID: 7DAAC25384116DD4
Verified
Learn about vigilant mode.
277ada7
This commit was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
GPG key ID: 7DAAC25384116DD4
Verified
Learn about vigilant mode.

1.5.30.1 January 27th 2026

Performance Fix: Reduced BSON Serializer Lock Contention

Fixed a critical performance issue where concurrent persistence operations would cause high CPU usage due to lock contention in the BSON serializer. Previously, FullTypeNameObjectSerializer would repeatedly register discriminators for types that were already registered, acquiring write locks unnecessarily.

Changes:

  • Added tracking of already-registered types to skip redundant registration
  • Made FullTypeNameObjectSerializer public with a static RegisterNewTypesToDiscriminator() method for pre-registration at startup

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.29 October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.28 September 11th 2024

Support For Large (Greater Than 16 Megabytes) Snapshot Store

Note

GridFS is considered as an advanced feature, it will not be supported by Akka.Hosting.

We added a new SnapshotStore that supports GridFS. To use it, you will need to set it through manual HOCON setting.

akka.persistence.snapshot-store.mongodb.class = "Akka.Persistence.MongoDb.Snapshot.MongoDbGridFsSnapshotStore, Akka.Persistence.MongoDb"

1.5.26 July 15th 2024

1.5.12.1 September 15 2023

Breaking Behavior Change

In this version, we're turning transaction on by default. If you're more concerned with database write and read performance compared to data consistency and correctness, you can move back to the old behavior by setting this flag in the HOCON configuration:

akka.persistence.journal.mongodb.use-write-transaction = off
akka.persistence.snapshot-store.mongodb.use-write-transaction = off

Or by setting them inside the hosting options:

var journalOptions = new MongoDbJournalOptions(true) 
    {
        UseWriteTransaction = false
    };
var snapshotOptions = new MongoDbSnapshotOptions(true)
    {
        UseWriteTransaction = false
    };

1.5.12 August 10 2023

1.5.8 June 30 2023

1.5.7 May 31 2023

1.5.1.1 March 24 2023

1.5.1 March 21 2023

1.5.0 March 03 2023

1.4.48 January 24 2023

1.4.40 July 27 2022

1.4.40-RC1 July 1 2022

1.4.39 June 6 2022

1.4.38-beta2 May 27 2022

1.4.38-beta1 April 15 2022

1.4.37 April 15 2022

1.4.31 December 21 2021

1.4.25 September 9 2021

1.4.21 July 07 2021

Read more
Loading

Akka.Persistence.MongoDB v1.5.55.1

Akka.Persistence.MongoDB v1.5.55.1

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 29 Oct 19:05
1.5.55.1
3062fd6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.55.1 October 29th 2025

Improved API

This release introduces the simplified Akka.Hosting 1.5.55.1 API for connectivity health checks, eliminating redundant parameter passing:

New Simplified API (Recommended):

journalBuilder: journal =>
{
    journal.WithConnectivityCheck(); // Options automatically accessed from builder
}

Previous API (Still Supported):

journalBuilder: journal =>
{
    journal.WithConnectivityCheck(journalOptions); // Explicit parameter passing
}

The new API automatically accesses options from builder.Options, making the code cleaner and less error-prone. The previous API is marked as [Obsolete] but remains functional for backward compatibility.

  • Update WithConnectivityCheck() extension methods to use simplified Akka.Hosting 1.5.55.1 API pattern
  • Upgraded to Akka.Hosting 1.5.55.1

1.5.55 October 26th 2025

Adds new WithConnectivityCheck() methods for proactive MongoDB connectivity verification with customizable tags.

1.5.53 October 16th 2025

New Feature: Health Check Support for Akka.Persistence.MongoDb.Hosting

This release adds built-in health check support for MongoDB journal and snapshot stores, integrated with Microsoft.Extensions.Diagnostics.HealthChecks. This enables monitoring and observability for your MongoDB persistence plugins.

Key capabilities:

  • Automatic health reporting for MongoDB journal and snapshot stores
  • Integration with ASP.NET Core health check endpoints
  • Configurable health status reporting (Healthy, Degraded, Unhealthy)
  • Tagged health checks for easy filtering (akka, persistence, mongodb)

Example usage:

services.AddHealthChecks(); // Add health check service

services.AddAkka("MyActorSystem", (builder, provider) =>
{
    builder
        .WithMongoDbPersistence(
            connectionString: "mongodb://localhost:27017/akka",
            journalBuilder: journal => journal.WithHealthCheck(HealthStatus.Degraded),
            snapshotBuilder: snapshot => snapshot.WithHealthCheck(HealthStatus.Degraded));
});

For complete documentation, see the Akka.Persistence.MongoDb.Hosting README and the main README.

1.5.42 May 22nd 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.40 March 27th 2025

1.5.37 January 24th 2025

1.5.32 December 23rd 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

Driver Behavior Change And Workaround

There is a behavior change in MongoDb.Driver v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.

Example:

  • Server address used in connection string: "host.docker.internal:27017"
  • Actual server address being used in MongoDb connection: "127.0.0.1:27017"

The workaround is to add "directConnection=true" in your connection string.

MongoDb.Driver Upgrade Advisories

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.32-beta1 December 5th 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.31 December 4th 2024

Version Notice

Due to breaking changes in MongoDb.Driver v3.0.0, This release will be the last Akka.Persistence.MongoDb that will support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.29 October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.28 September 11th 2024

Read more
Loading

Akka.Persistence.MongoDB v1.5.55

Akka.Persistence.MongoDB v1.5.55

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 27 Oct 02:14
1.5.55
This tag was signed with the committer’s verified signature.
Aaronontheweb Aaron Stannard
GPG key ID: 7DAAC25384116DD4
Verified
Learn about vigilant mode.
b1622d0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.55 October 26th 2025

Adds new WithConnectivityCheck() methods for proactive MongoDB connectivity verification with customizable tags.

1.5.53 October 16th 2025

New Feature: Health Check Support for Akka.Persistence.MongoDb.Hosting

This release adds built-in health check support for MongoDB journal and snapshot stores, integrated with Microsoft.Extensions.Diagnostics.HealthChecks. This enables monitoring and observability for your MongoDB persistence plugins.

Key capabilities:

  • Automatic health reporting for MongoDB journal and snapshot stores
  • Integration with ASP.NET Core health check endpoints
  • Configurable health status reporting (Healthy, Degraded, Unhealthy)
  • Tagged health checks for easy filtering (akka, persistence, mongodb)

Example usage:

services.AddHealthChecks(); // Add health check service

services.AddAkka("MyActorSystem", (builder, provider) =>
{
    builder
        .WithMongoDbPersistence(
            connectionString: "mongodb://localhost:27017/akka",
            journalBuilder: journal => journal.WithHealthCheck(HealthStatus.Degraded),
            snapshotBuilder: snapshot => snapshot.WithHealthCheck(HealthStatus.Degraded));
});

For complete documentation, see the Akka.Persistence.MongoDb.Hosting README and the main README.

1.5.42 May 22nd 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.40 March 27th 2025

1.5.37 January 24th 2025

1.5.32 December 23rd 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

Driver Behavior Change And Workaround

There is a behavior change in MongoDb.Driver v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.

Example:

  • Server address used in connection string: "host.docker.internal:27017"
  • Actual server address being used in MongoDb connection: "127.0.0.1:27017"

The workaround is to add "directConnection=true" in your connection string.

MongoDb.Driver Upgrade Advisories

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.32-beta1 December 5th 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.31 December 4th 2024

Version Notice

Due to breaking changes in MongoDb.Driver v3.0.0, This release will be the last Akka.Persistence.MongoDb that will support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.29 October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.28 September 11th 2024

Support For Large (Greater Than 16 Megabytes) Snapshot Store

Note

GridFS is considered as an advanced feature, it will not be supported by Akka.Hosting.

We added a new SnapshotStore that supports GridFS. To use it, you will need to set it through manual HOCON setting.

akka.persistence.snapshot-store.mongodb.class = "Akka.Persistence.MongoDb.Snapshot.MongoDbGridFsSnapshotStore, Akka.Persistence.MongoDb"

1.5.26 July 15th 2024

Read more
Loading

Akka.Persistence.MongoDB v1.5.53

Akka.Persistence.MongoDB v1.5.53

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 15 Oct 17:20
1.5.53
e6a979c

1.5.53 October 16th 2025

New Feature: Health Check Support for Akka.Persistence.MongoDb.Hosting

This release adds built-in health check support for MongoDB journal and snapshot stores, integrated with Microsoft.Extensions.Diagnostics.HealthChecks. This enables monitoring and observability for your MongoDB persistence plugins.

Key capabilities:

  • Automatic health reporting for MongoDB journal and snapshot stores
  • Integration with ASP.NET Core health check endpoints
  • Configurable health status reporting (Healthy, Degraded, Unhealthy)
  • Tagged health checks for easy filtering (akka, persistence, mongodb)

Example usage:

services.AddHealthChecks(); // Add health check service

services.AddAkka("MyActorSystem", (builder, provider) =>
{
    builder
        .WithMongoDbPersistence(
            connectionString: "mongodb://localhost:27017/akka",
            journalBuilder: journal => journal.WithHealthCheck(HealthStatus.Degraded),
            snapshotBuilder: snapshot => snapshot.WithHealthCheck(HealthStatus.Degraded));
});

For complete documentation, see the Akka.Persistence.MongoDb.Hosting README and the main README.

1.5.42 May 22nd 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.40 March 27th 2025

1.5.37 January 24th 2025

1.5.32 December 23rd 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

Driver Behavior Change And Workaround

There is a behavior change in MongoDb.Driver v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.

Example:

  • Server address used in connection string: "host.docker.internal:27017"
  • Actual server address being used in MongoDb connection: "127.0.0.1:27017"

The workaround is to add "directConnection=true" in your connection string.

MongoDb.Driver Upgrade Advisories

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.32-beta1 December 5th 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.31 December 4th 2024

Version Notice

Due to breaking changes in MongoDb.Driver v3.0.0, This release will be the last Akka.Persistence.MongoDb that will support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.29 October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.28 September 11th 2024

Support For Large (Greater Than 16 Megabytes) Snapshot Store

Note

GridFS is considered as an advanced feature, it will not be supported by Akka.Hosting.

We added a new SnapshotStore that supports GridFS. To use it, you will need to set it through manual HOCON setting.

akka.persistence.snapshot-store.mongodb.class = "Akka.Persistence.MongoDb.Snapshot.MongoDbGridFsSnapshotStore, Akka.Persistence.MongoDb"

1.5.26 July 15th 2024

1.5.12.1 September 15 2023

Read more
Loading

Akka.Persistence.MongoDB v1.5.42

Akka.Persistence.MongoDB v1.5.42

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 22 May 13:54
1.5.42
03d5db4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.42 May 22nd 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

1.5.40 March 27th 2025

1.5.37 January 24th 2025

1.5.32 December 23rd 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

Driver Behavior Change And Workaround

There is a behavior change in MongoDb.Driver v3.0.0 where it would use the DNS resolved server host address when it actually tries to connect to the server. This is problematic if your application lives inside a container and hard code your MongoDb server address inside the connection string.

Example:

  • Server address used in connection string: "host.docker.internal:27017"
  • Actual server address being used in MongoDb connection: "127.0.0.1:27017"

The workaround is to add "directConnection=true" in your connection string.

MongoDb.Driver Upgrade Advisories

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.32-beta1 December 5th 2024

Breaking Change Notice

Due to breaking changes in MongoDb.Driver v3.0.0, from this point forward, Akka.Persistence.MongoDb releases WILL NOT support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

MongoDb.Driver 3.0.0 release note: https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.0.0

MongoDb.Driver 3.0.0 Upgrade advisory: https://www.mongodb.com/docs/drivers/csharp/v3.0/upgrade/v3/

1.5.31 December 4th 2024

Version Notice

Due to breaking changes in MongoDb.Driver v3.0.0, This release will be the last Akka.Persistence.MongoDb that will support:

  • MongoDb server v3.6 and earlier
  • Projects that targets .NET Core 2.x and lower
  • Projects that targets .NET Framework 2.7.1 and lower
  • LINQ2 provider
  • TLS 1.0 and 1.1

1.5.30 October 3rd 2024

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.29 October 1st 2024

Note

Deprecated

Deprecated due to Akka.NET 1.5.29 deprecation. Please use 1.5.30 instead.

Breaking Change Notice

The MongoDb driver 2.28.0 is now strongly-named which may affect your project(s). You can read more about this decision here.

1.5.28 September 11th 2024

Support For Large (Greater Than 16 Megabytes) Snapshot Store

Note

GridFS is considered as an advanced feature, it will not be supported by Akka.Hosting.

We added a new SnapshotStore that supports GridFS. To use it, you will need to set it through manual HOCON setting.

akka.persistence.snapshot-store.mongodb.class = "Akka.Persistence.MongoDb.Snapshot.MongoDbGridFsSnapshotStore, Akka.Persistence.MongoDb"

1.5.26 July 15th 2024

1.5.12.1 September 15 2023

Breaking Behavior Change

In this version, we're turning transaction on by default. If you're more concerned with database write and read performance compared to data consistency and correctness, you can move back to the old behavior by setting this flag in the HOCON configuration:

akka.persistence.journal.mongodb.use-write-transaction = off
akka.persistence.snapshot-store.mongodb.use-write-transaction = off

Or by setting them inside the hosting options:

var journalOptions = new MongoDbJournalOptions(true) 
    {
        UseWriteTransaction = false
    };
var snapshotOptions = new MongoDbSnapshotOptions(true)
    {
        UseWriteTransaction = false
    };

1.5.12 August 10 2023

Read more
Loading

Akka.Persistence.MongoDB v1.5.41-beta1

Akka.Persistence.MongoDB v1.5.41-beta1 Pre-release
Pre-release

Choose a tag to compare

View all tags
@Aaronontheweb Aaronontheweb released this 04 Apr 18:04
1.5.41-beta1
ce57da7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

1.5.41-beta1 April 4th 2025

We're optimizing how write transaction is being done. Following the MongoDb documentation that all single document writes are atomic, we're not using transaction for single document writes anymore.

Changes:

  • ce57da7 Update RELEASE_NOTES.md for 1.5.41-beta1 (#414)
  • 437db02 Update build pipeline to use global.json (#413)
  • 10df968 Update RELEASE_NOTES.md for 1.5.40.1-beta1 release (#412)
  • ecf590d Fix journal and snapshot write atomicity (#410)

This list of changes was auto generated.

Loading