Aaronontheweb

akka {
          loggers = ["Akka.Logger.Serilog.SerilogLogger, Akka.Logger.Serilog"]
          stdout-loglevel = DEBUG
          loglevel = DEBUG
          log-config-on-start = off
          suppress-json-serializer-warning = on
          
          actor {
            #serialize-messages = on
            provider = "Akka.Cluster.ClusterActorRefProvider,Akka.Cluster" # turns Akka.Cluster on

Aaronontheweb

Original ActorPath Benchmark Values

BenchmarkDotNet=v0.12.0, OS=Windows 10.0.18362
Intel Core i7-3630QM CPU 2.40GHz (Ivy Bridge), 1 CPU, 8 logical and 4 physical cores
.NET Core SDK=3.0.100
  [Host]     : .NET Core 2.1.13 (CoreCLR 4.6.28008.01, CoreFX 4.6.28008.01), X64 RyuJIT
  DefaultJob : .NET Core 2.1.13 (CoreCLR 4.6.28008.01, CoreFX 4.6.28008.01), X64 RyuJIT

Aaronontheweb

public class AkkaMongoReader
{
    public ActorSystem Sys { get; }
    private readonly Akka.Serialization.Serialization _serialization;

    public AkkaMongoReader(ActorSystem sys)
    {
        Sys = sys;
        _serialization = Sys.Serialization;
    }

Aaronontheweb

Akka.NET QA Proposed Changes and Updates

Goals

1. Radically reduce the per-pull request build time

   1. Eliminate agent "spin up" time
   2. Don't waste resources executing tests for things that don't need testing, such as documentation updates and README fixes.
   3. Don't compile the entire project for each step in the build process.
   4. If possible, only execute dependent tests - not all tests (incremental testing.)

2. Reduce unit test flakiness

Aaronontheweb

using System;
using System.IO;
using System.Collections.Generic;
using System.Linq;
using Akka.Actor;
using Akka.Event;
using Akka.Routing;

namespace AkkaTest
{

Aaronontheweb

Avoiding Microservice Pains with Distributed Actors and Akka.NET

Microservices promised development teams a brand new world when it comes to developing, deploying, and distributing software. We could code services in any language, deploy them independently, enjoy partial failure instead of total, and straight-forwardly partition our teams along the same boundaries as some of our services.

But with these benefits came more expense and unanticipated costs. We now need multiple layers of routing and load-balancing. API gateways. Service discovery. Message brokers. Kafka. Laser manifolds. gRPC++ MQTT quantum tunneling. And so on.

In this talk we present a more refined, standardized, and simplified approach to building highly available, responsive, and distributed systems: distributed actors via Akka.NET. With this approach, we can eliminate most of the third party infrastructure needed to build effective applications, improve response times, and decrease human costs associated with building highly available s

Aaronontheweb

docker run --rm -it -v ${PWD}:/data -e DOTNET_FRAMEWORKS="net452,netcoreapp1.0" akkadotnet/mono-base /bin/bash

Aaronontheweb

public class HomeController : Controller
    {
        private readonly Cluster _cluster;

        public HomeController()
        {
            _cluster = Cluster.Get(SystemActors.ActorSystem);
        }

        public IActionResult Index()

Aaronontheweb

---

layout: post title: "Akka.NET 2017 Roadmap Update" subtitle: ".NET Standard, Akka.Persistence RTM, and More" published: True comments: true categories: ["Akka.NET", "Releases"] author: Aaron Stannard permalink: /blog/akkadotnet-2017-roadmap/ author_url: http://twitter.com/Aaronontheweb

Aaronontheweb

docker run --name akka-postgres -p 5432:5432 -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres -e POSTGRES_DB=akka_persistence_tests -d postgres

docker run -ti --rm --name akka-pg-mono --link akka-postgres:postgres akkadotnet/mono-base