Spring Tips: Spring Statemachine

Speaker: Josh Long

Hi Spring fans! In this installment we'll look at how to extricate process state - valuable for coordinating long running or mutli-actor processes - from business logic with Spring Statemachine.

[Temofey]

A good approach to think about.
Thanks for the video, Josh.

[amarpathak]

Amazing video. it is really helpful to start using spring state machine. Loved the explanation. Thanks you Josh !

[viorelcasapu]

GREAT introduction in spring statemachine! Thanks!

[donwald]

Thank you! This is a good starting point.

[yongqiangli]

Thanks a lot! Pretty good explanation about using Spring Boot state machine and very helpful!

[eirikbremnes]

Awesome video! Thanks!! Keep up the good work!!!

[BrijeshPatelEngineer]

Great video. I would recommend start with flow diagram at start which sets the visuals on the state changes happening.
Overall nice video. I will try to implement it and link it in my video soon.

[liuckan]

The ID of the state machines is null every time (56:04), although you're passing the orderId, because of the "doWithAllRegions->reset" bits. The SM are different on every step of the workflow, because of the factory, but the question is how fast each instance is stopped and discarded? Let's say you wanna transition from SI -> A -> B states - what is happening is basically SI to A - get new SM, do 1 node transition, stop the SM; A to B -> get new SM, do 1 node transition, stop the SM; What conditions needs to be satisfied for the SM1 to stop, having in mind A is not a final state? Should it be stopped manually after the transition is done?

[elijahtang]

thank u very much . it solved my question！

[NehaGupta]

Really nice and helpful video. However, I have a question Josh:
If I deploy my state machine on different clusters and supposedly one of the clusters goes down, then how will the states be restored in memory again?

[mutasemjubran]

Hi Thanx for this tutorial. Do you know how to persist using JPA?

[prateekashtikar]

Can you please create tutorial on Saga - considering Orchestration ?

[Parames]

Hi.... Is this code available anywhere on the web or anyone has this code working open to share..

[YidingHe]

It scares me how complex it is. Can't we just pass order id, state and event and get a next state and persist it outside the state machine instead of using an interceptor?

[Third_Eyeee]

Thanks for the amazing video, this is a great reference for me.
but i have some doubts on initial state, parent state, sub states etc. and i also don't know that is it possible to create nested state machine(machine in side a machine)

please give me some suggestion and reference(book name, blogs,docs) from where i can clear my all doubts.
please create 5-10 mint video for some states listeners, states mathods and it's use in multithreading environment(distributed system) if it is possible.

[martinsefcik]

I would like to see such example together with @Transactional
For example if paymentConfirmationNumber is attribute of Order entity and I want to set this attribute to order entity on PAID state entry action and also have it saved together with order state within the same transaction.
And the second case would be to have some post PAID state change action which will be executed immediately after PAID status is changed, but in the new transaction.
So state is changed saved and committed in one transaction, such transaction ends and then post state change action will be executed in new transaction.
What is the best approach for such scenarios? I cannot find such examples in spring state machine docs and also anywhere on internet.

[Ajayhanand]

what if the prestatechange method succeeeds and start change fails?

[CloudAndCode]

Why boot application always exits after the operation is completed. How do keep the application running?

[kennethcarvalho]

Nice but you could have started with a good slide on State machines during your intro instead of a dark screen

[gennadijdegterjow]

Good information about state mashine, but wrong usage of logging framework. Using String.format or string concatenation you kill all benefits. With ERROR log level you will simple burn CPU and produce garbage. Use placeholders {} to format your log entries