Any good comparison on FSM of Flink vs Akka?

[Rohit R]

Hello, 

To solve the following use case, What will be the best option between Flink or Flink Stateful Functions or Akka FSM?  

Use Case:

Can I get the analysis, pros, and cons of each? For example, why choosing Flink Stateful function will better option.

Thank You

[Till Rohrmann]

Hi Rohit,

image attachments are filtered out and not visible to others. Hence, I
would suggest that you upload the image and then share the link.

Maybe you can share a bit more details about the use case and your current
analysis of the problem.

Cheers,
Till

On Wed, Jun 17, 2020 at 12:15 PM Rohit R <[hidden email]> wrote:

> Hello,
>
> To solve the following use case, What will be the best option between
> Flink or Flink Stateful Functions or Akka FSM?
>
> Use Case:
> [image: image.png]
>
> Can I get the analysis, pros, and cons of each? For example, why choosing
> Flink Stateful function will better option.
>
> Thank You
>

[Rohit R]

Hi Till Rohrmann,

Consider any Finite State Machine which involves many states and need
timers (wait for this much time and then timeout) or for example, consider
the Movie Booking ticketing system
http://thatgamesguy.co.uk/articles/modular-finite-state-machine-in-unity/
or these images:
https://imgur.com/a/MV62BlO

The current use case is based on FSM, but in future can consider HFSM as
well: https://web.stanford.edu/class/cs123/lectures/CS123_lec08_HFSM_BT.pdf

Thank You

On Wed, Jun 17, 2020 at 5:20 PM Till Rohrmann <[hidden email]> wrote:

> Hi Rohit,
>
> image attachments are filtered out and not visible to others. Hence, I
> would suggest that you upload the image and then share the link.
>
> Maybe you can share a bit more details about the use case and your current
> analysis of the problem.
>
> Cheers,
> Till
>
> On Wed, Jun 17, 2020 at 12:15 PM Rohit R <[hidden email]> wrote:
>
> > Hello,
> >
> > To solve the following use case, What will be the best option between
> > Flink or Flink Stateful Functions or Akka FSM?
> >
> > Use Case:
> > [image: image.png]
> >
> > Can I get the analysis, pros, and cons of each? For example, why choosing
> > Flink Stateful function will better option.
> >
> > Thank You
> >
>

[Igal Shilman]

Hi Rohit,

Stateful functions fit well into domains that require many (billions) state
machines that are able to communicate with each other by message passing.
In stateful functions world, a state machine can be represented by a
stateful function - a uniquely addressable entity, that can keep state and
be invoked with
messages.

Here is a summary of some of the capabilities of stateful functions:

- built on a scalable battle tested, stateful stream processor
- scales to many millions state machines per node (bounded by disk size)
idle state machines do not occupy any RAM.
- exactly once processing of the messages and state modifications across
all of the state machines
- Globally consists of point in time snapshots to durable storage, like S3
or HDFS.
- interop with FaaS via remote functions - being able to seamlessly scale
the compute part when needed.
- no need for service discovery and complex failure-recovery logic around
message sending, de-duping, retrying etc'

I would encourage you to visit [1] for more information, and take a look at
some of the recording of the previous Flink forward conferences to
understand more
about what kind of applications you can build with that.

[1] https://flink.apache.org/stateful-functions.html

Good luck,
Igal.


On Wed, Jun 17, 2020 at 3:18 PM Rohit R <[hidden email]> wrote:

> Hi Till Rohrmann,
>
> Consider any Finite State Machine which involves many states and need
> timers (wait for this much time and then timeout) or for example, consider
> the Movie Booking ticketing system
> http://thatgamesguy.co.uk/articles/modular-finite-state-machine-in-unity/
> or these images:
> https://imgur.com/a/MV62BlO
>
> The current use case is based on FSM, but in future can consider HFSM as
> well:
> https://web.stanford.edu/class/cs123/lectures/CS123_lec08_HFSM_BT.pdf
>
> Thank You
>
> On Wed, Jun 17, 2020 at 5:20 PM Till Rohrmann <[hidden email]>
> wrote:
>
> > Hi Rohit,
> >
> > image attachments are filtered out and not visible to others. Hence, I
> > would suggest that you upload the image and then share the link.
> >
> > Maybe you can share a bit more details about the use case and your
> current
> > analysis of the problem.
> >
> > Cheers,
> > Till
> >
> > On Wed, Jun 17, 2020 at 12:15 PM Rohit R <[hidden email]>
> wrote:
> >
> > > Hello,
> > >
> > > To solve the following use case, What will be the best option between
> > > Flink or Flink Stateful Functions or Akka FSM?
> > >
> > > Use Case:
> > > [image: image.png]
> > >
> > > Can I get the analysis, pros, and cons of each? For example, why
> choosing
> > > Flink Stateful function will better option.
> > >
> > > Thank You
> > >
> >
>

[Rohit R]

Hi Igal,

I read that, To solve the following use case, What will be the best option
between Flink or Flink Stateful Functions or Akka FSM?
http://thatgamesguy.co.uk/articles/modular-finite-state-machine-in-unity/
or these images:
https://imgur.com/a/MV62BlO

Was looking for an in-depth comparison of Akka FSM vs Flink Stateful
Functions..

Thank You

On Wed, Jun 17, 2020 at 7:58 PM Igal Shilman <[hidden email]> wrote:

> Hi Rohit,
>
> Stateful functions fit well into domains that require many (billions) state
> machines that are able to communicate with each other by message passing.
> In stateful functions world, a state machine can be represented by a
> stateful function - a uniquely addressable entity, that can keep state and
> be invoked with
> messages.
>
> Here is a summary of some of the capabilities of stateful functions:
>
> - built on a scalable battle tested, stateful stream processor
> - scales to many millions state machines per node (bounded by disk size)
> idle state machines do not occupy any RAM.
> - exactly once processing of the messages and state modifications across
> all of the state machines
> - Globally consists of point in time snapshots to durable storage, like S3
> or HDFS.
> - interop with FaaS via remote functions - being able to seamlessly scale
> the compute part when needed.
> - no need for service discovery and complex failure-recovery logic around
> message sending, de-duping, retrying etc'
>
> I would encourage you to visit [1] for more information, and take a look at
> some of the recording of the previous Flink forward conferences to
> understand more
> about what kind of applications you can build with that.
>
> [1] https://flink.apache.org/stateful-functions.html
>
> Good luck,
> Igal.
>
>
> On Wed, Jun 17, 2020 at 3:18 PM Rohit R <[hidden email]> wrote:
>
> > Hi Till Rohrmann,
> >
> > Consider any Finite State Machine which involves many states and need
> > timers (wait for this much time and then timeout) or for example,
> consider
> > the Movie Booking ticketing system
> >
> http://thatgamesguy.co.uk/articles/modular-finite-state-machine-in-unity/
> > or these images:
> > https://imgur.com/a/MV62BlO
> >
> > The current use case is based on FSM, but in future can consider HFSM as
> > well:
> > https://web.stanford.edu/class/cs123/lectures/CS123_lec08_HFSM_BT.pdf
> >
> > Thank You
> >
> > On Wed, Jun 17, 2020 at 5:20 PM Till Rohrmann <[hidden email]>
> > wrote:
> >
> > > Hi Rohit,
> > >
> > > image attachments are filtered out and not visible to others. Hence, I
> > > would suggest that you upload the image and then share the link.
> > >
> > > Maybe you can share a bit more details about the use case and your
> > current
> > > analysis of the problem.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Wed, Jun 17, 2020 at 12:15 PM Rohit R <[hidden email]>
> > wrote:
> > >
> > > > Hello,
> > > >
> > > > To solve the following use case, What will be the best option between
> > > > Flink or Flink Stateful Functions or Akka FSM?
> > > >
> > > > Use Case:
> > > > [image: image.png]
> > > >
> > > > Can I get the analysis, pros, and cons of each? For example, why
> > choosing
> > > > Flink Stateful function will better option.
> > > >
> > > > Thank You
> > > >
> > >
> >
>