[akka-user] Re: Recommendations on a PoC for system migration from VB.NET to Scala/Akka stack
DId you see my note ? On Monday, January 29, 2018 at 12:22:01 AM UTC+5:30, Damian Blazejewski wrote: > > Generally, it sounds good. > > i. -> you don't say anything about the deployment but I would think about > Akka Cluster from the beginning. > iv. -> what data do you persist? You can do it asynchronously without > blocking the rest api using Kafka. Or maybe Akka Persistence would work for > you? > > On Thursday, January 25, 2018 at 3:56:37 PM UTC+1, Som Shankar > Bhattacharyya wrote: >> >> I want some suggestions/recommendations on the following. >> >> >> Today we have a legacy .NET system that gathers information from >> customers environment and reports back to our backend. >> >> Now this system is built the following way, >> >> The client is a VB.Net application.(Usually running outside our network) >> >> The back end is a combination of REST services and traditional web >> services. All in ASP. These services have their database calls etc. >> >> >> *Motivations:* >> >> >> i. Migrating the legacy framework is essential simply because of >> maintainace cost. >> >> ii.Our services are going to be hit very heavily this coming year with a >> big increase in clients and reducing intervals of time between client polls >> and i want to showcase how the Scala/Akka stack can provide better >> performance in this regard. >> >> Now i want to demo advantages of having this work done in the Scala/Akka >> framework. >> >> I am wondering what approach should i take to best highlight the >> advantages of adopting this stack. >> >> I already have a small REST service implemented that does a connect to a >> database and get/set some data. I have implemented that as a Akka HTTP REST >> service. >> >> But i haven’t mimicked the client or the other web services in question. >> >> With my limited knowledge of this stack i might still be able to >> implement a client and a web service but i want to have a focused approach >> on what to highlight and how to do so. >> >> >> *Initial thoughts:* >> >> i.Write a Scala program with Akka actors. I need actors to abstract the >> different work the client needs to do in parallel. Today we do those using >> a few windows services. >> >> ii.Have the already implemented REST service on a separate machine. >> >> iii.I need to write at least another web service(will it be a better idea >> to write all services as REST ? ) >> >> iv.Figure out a way to save data to the database from the services at >> lightning speed. Today we have to write to the file system first and thena >> different service slurps it up and persists to the database. Maybe we can >> have some message broker here that can be used ? >> >> >> I need someone to discuss this with and come to a focussed work item. >> >> >> Much thanks ! >> >> -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: Recommendations on a PoC for system migration from VB.NET to Scala/Akka stack
The data we persist is table data. We receive serialized tables from the clients and save it to the file system. Then another set of services reads from files and persisists to the database. Yes i too think Kafka will be an excellent fit here. However i do not have much idea about deployments. Can you please suggest me , i. How to best showcase the advantages of this implementation ? ii. Example of a AKKA http application deployed in a web server ? Much thanks. On Thursday, January 25, 2018 at 8:26:37 PM UTC+5:30, Som Shankar Bhattacharyya wrote: > > I want some suggestions/recommendations on the following. > > > Today we have a legacy .NET system that gathers information from customers > environment and reports back to our backend. > > Now this system is built the following way, > > The client is a VB.Net application.(Usually running outside our network) > > The back end is a combination of REST services and traditional web > services. All in ASP. These services have their database calls etc. > > > *Motivations:* > > > i. Migrating the legacy framework is essential simply because of > maintainace cost. > > ii.Our services are going to be hit very heavily this coming year with a > big increase in clients and reducing intervals of time between client polls > and i want to showcase how the Scala/Akka stack can provide better > performance in this regard. > > Now i want to demo advantages of having this work done in the Scala/Akka > framework. > > I am wondering what approach should i take to best highlight the > advantages of adopting this stack. > > I already have a small REST service implemented that does a connect to a > database and get/set some data. I have implemented that as a Akka HTTP REST > service. > > But i haven’t mimicked the client or the other web services in question. > > With my limited knowledge of this stack i might still be able to implement > a client and a web service but i want to have a focused approach on what to > highlight and how to do so. > > > *Initial thoughts:* > > i.Write a Scala program with Akka actors. I need actors to abstract the > different work the client needs to do in parallel. Today we do those using > a few windows services. > > ii.Have the already implemented REST service on a separate machine. > > iii.I need to write at least another web service(will it be a better idea > to write all services as REST ? ) > > iv.Figure out a way to save data to the database from the services at > lightning speed. Today we have to write to the file system first and thena > different service slurps it up and persists to the database. Maybe we can > have some message broker here that can be used ? > > > I need someone to discuss this with and come to a focussed work item. > > > Much thanks ! > > -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
[akka-user] Re: Recommendations on a PoC for system migration from VB.NET to Scala/Akka stack
Generally, it sounds good. i. -> you don't say anything about the deployment but I would think about Akka Cluster from the beginning. iv. -> what data do you persist? You can do it asynchronously without blocking the rest api using Kafka. Or maybe Akka Persistence would work for you? On Thursday, January 25, 2018 at 3:56:37 PM UTC+1, Som Shankar Bhattacharyya wrote: > > I want some suggestions/recommendations on the following. > > > Today we have a legacy .NET system that gathers information from customers > environment and reports back to our backend. > > Now this system is built the following way, > > The client is a VB.Net application.(Usually running outside our network) > > The back end is a combination of REST services and traditional web > services. All in ASP. These services have their database calls etc. > > > *Motivations:* > > > i. Migrating the legacy framework is essential simply because of > maintainace cost. > > ii.Our services are going to be hit very heavily this coming year with a > big increase in clients and reducing intervals of time between client polls > and i want to showcase how the Scala/Akka stack can provide better > performance in this regard. > > Now i want to demo advantages of having this work done in the Scala/Akka > framework. > > I am wondering what approach should i take to best highlight the > advantages of adopting this stack. > > I already have a small REST service implemented that does a connect to a > database and get/set some data. I have implemented that as a Akka HTTP REST > service. > > But i haven’t mimicked the client or the other web services in question. > > With my limited knowledge of this stack i might still be able to implement > a client and a web service but i want to have a focused approach on what to > highlight and how to do so. > > > *Initial thoughts:* > > i.Write a Scala program with Akka actors. I need actors to abstract the > different work the client needs to do in parallel. Today we do those using > a few windows services. > > ii.Have the already implemented REST service on a separate machine. > > iii.I need to write at least another web service(will it be a better idea > to write all services as REST ? ) > > iv.Figure out a way to save data to the database from the services at > lightning speed. Today we have to write to the file system first and thena > different service slurps it up and persists to the database. Maybe we can > have some message broker here that can be used ? > > > I need someone to discuss this with and come to a focussed work item. > > > Much thanks ! > > -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
