Can I use Akka's stubbornness when the actor’s condition only increases?

Question

I play with akka persistence, trying to implement a service where my condition is potentially a very large (well, let it be said that this will not fit in RAM) list of some objects. Suppose a user wants the whole story to be accessible to all entities. Can I do it with the stubbornness of an aka?

Now my state of the actor looks like this.

case class System(var processes: Map[Long, Process] = Map()) {

  def updated(event: Event): System = event match {
    case ProcessDetectedEvent(time, activitySets, id, processType) =>
      val process = Process(activitySets.coordinates, time, activitySets.channels, id, processType, false)
      copy(processes = processes + (id -> process))

    case ProcessMovedEvent(id, activitySets, time) =>
      val process = Process(activitySets.coordinates, time, activitySets.channels, id, processes(id).processType, false)
      copy(processes = processes + (id -> process))

    case ProcessClosedEvent(time, id) =>
      val currentProcess = processes(id)
      val process = Process(currentProcess.coordinates, time, currentProcess.channels, id, currentProcess.processType, true)
      copy(processes = processes + (id -> process))
    case _ => this
  }

}

As you can see, the process map is stored in memory, so the application can end without memory if the number of processes is large.

Answer 1

Akka , , , JVM . /JVM OutOfMemory . , . , . , , , .

, . , .

• JVM JVM OutOfMemory.
• , , .

, , , .

Answer 2

, , , . , , , . , , - , - Spark.

Answer 3

, ( , ) - .

.

, , , , . , , ( ), ()... ... .

. , ... , .

I did not look too closely, but Akka could have this concept of creating images embedded in it. If not, there is a learning curve and a lot of trial and error on the road ahead, when you start to hit all these roads, less traveling in ideal approaches, but the real world throws at you.