scala - Event based design - Futures, Promises vs Akka Persistence -



scala - Event based design - Futures, Promises vs Akka Persistence -

i have multiple utilize cases require predefined events fired based on user actions.

e.g. let's when newuser created in application, it'll have phone call createuserinworkflowsystem , fireemailtotheuser asynchronously. there many other business cases of nature events predefined based on usecase. can utilize promises/futures model these events below

if 'newuser' phone call `createuserinworkflowsystem` (which future based api) phone call `fireemailtotheuser` (which future based api) if 'fileimport' phone call `api3` (which future based call) phone call `api4` (which future based call)

all future calls have log failures somewhere failed calls can retried etc. note newuser phone call won't waiting futures (events per say) complete.

that using plain futures/promises apis. thinking akka persistence appropriate fit here , blocking calls can still run futures. akka persistence, handling failure easy provides out of box etc. understand akka persistence still in experimental stage doesn't seem big concern typesafe keeps these new frameworks experimental state before promoting future release etc. (same true macros). given these requirements think futures/promises or akka persistence improve fit here?

this opinion based question - not best type inquire on so. anyway, trying answer.

it depends more comfortable , requirements are. need scale scheme later beyond single jvm - utilize akka. want maintain more simple - utilize futures.

if utilize futures can store state , actions execute in job queue/db. it's quite reasonable.

if utilize akka persistence help persistence. akka help perform supervison, recovery , retries easier. if createuserinworkflowsystem action fails result propagated supervising actor restarts failed actor , makes retry n times. if supervising actor fails supervisor right thing, or whole app crash good. futures have implement mechanism , create sure application can crash when needed.

if have independent actions futures , actors sound same. if have chain actions , compose them, using futures more natural thing do: for comprehensions, etc. in akka have wait message , based on type of message perform next action.

try mock simple implementation using both , compare like/dislike given particular application requirements. overall, both choices good, i'm leaning towards actors in case.

scala akka akka-persistence

Comments

Post a Comment

Popular posts from this blog

php - Android app custom user registration and login with cookie using facebook sdk -

php - Android app custom user registration and login with cookie using facebook sdk - i developing android application in users need register , log in using facebook. approximately, flow. open app first time, authenticate facebook, data, send info server create them business relationship in application, start session new business relationship in server, cookie perform later interactions. so far good. what need know wich info have send server, can able identify users when log in seccond time. because need start session in server , send cookie android app farther interactions. i'm using php server side language. i thinking getting getaccesstoken() in android facebook sdk, pass server on business relationship creation , storing in android app. but can't manage how login users on sec time utilize app. any suggestions ? in advance ! to uniquely identify user within app, should create request /me , user's id. guaranteed unique , remain con...
Read more

c# - Create a Notification Object (Email or Page) At Run Time -- Dependency Injection or Factory -

c# - Create a Notification Object (Email or Page) At Run Time -- Dependency Injection or Factory - i have code emails me notification when happens. trying add together page , also remove dependency on email. for reference; have name of notification want send stored string in database. @ runtime have list of people , string representation of want receive. i thought dependency injection ninject, kernel bindings got big , seemed hacking together. then thought simple factory, activator.createinstance(email/page) inotifcation, don't know how handle differing constructor parameters (unless utilize common, complex property, employee, has info need). so far have this: public interface inotification { void sendmessage(); } public class email: inotification { private readonly string _toemailaddress; private string body { { homecoming "email"; } } private static string smtphost { ...
Read more

Set Up Of Common Name Of SSL Certificate To Protect Plesk Panel -

Set Up Of Common Name Of SSL Certificate To Protect Plesk Panel - a pci compliance scanner balking self signed ssl certificate protecting secure access plesk panel contains name mismatch between location of plesk panel , name on certificate, namely self-signed cert's name "parallels" , domain reach plesk 'ip address:8443'. so figured go ahead , free ssl certificate seek fiddle error. when generated certificate used server domain name site name when generated certificate. if visit 'domain name:8443' fine, no ssl warning. if visit 'ip address:8443' (which believe scanner does) certificate name mismatch error, digicert's ssl checker says certificate name should ip address. can generate certificate mutual name ip address? tempted should pci scanner accepts, right mutual name use? run issue before? you can seek subject alternative name extension ip address. also, can maintain "parallels" mutual name, , add together ...
Read more