eventuate | scale event sourcing and event collaboration | Microservice library

I’m a reliability engineer (definitely not an experienced Python programmer) seeking to run a discrete-use system simulation in Python, and I’m having some trouble simulating failure mode first occurrence test failures. A discrete-use system is one that typically has its usage measured in terms of demands, for example, a missile system. The system is in standby most of the time, and when required, we ‘demand’ the system. The system then has two possible demand outcomes – success (our missile fires) or failure (our missile doesn’t).

Let’s say our system has failure mode rates of occurrence represented by f_rate.

I now want to simulate the ‘First Occurrence on Test’ of each failure mode by randomly drawing from a geometric distribution related to that particular failure mode rate which is represented by FOT.

This is what a sample looks like:

EDITED:

I want to make my question more simple

check the code

In an eventuate program, getting below error, I doubt some dependency is missing or version issue.

Actually I followed https://github.com/eventuate-examples/eventuate-examples-java-spring-todo-list and tried to build the project using maven, but it doesn't work.

Or if you guys have a sample eventuate 'event driven' based project, please share it to me.

Error:

I'm currently using Scala and Eventuate, but I think this question applies to any event sourced environment:

Let’s say you have the following event: case class UserAdded(user: User), and User is case class User(username:String, birthday: Date).

Your app has been running for a while and now you need to collect the Users' phone number. So now we would need to change User to case class User(username:String, birthday: Date, phoneNumber: String).

When the events are replayed, it will throw errors because past events didn't have a phoneNumber. How do you usually address this problem in a event-sourced application?

My first thought was to set a default value for all the events in the event store, but I understand events are immutable when you do event sourcing, so I decided to hear from more experienced users on the matter.

Any input is much appreciated!

I'm trying to test Eventuate (framework JAVA that implement event sourcing) But I have a huge feature with eclipse, when I imported the project eclipse display the same files a lot of time.

For information the project is a spring-boot project using gradle.

This is a screen shot:

Would do you have an idea why this happens ?