Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Azure] Figure out if to use serverless or load blalancer #421

Closed
alonttal opened this issue May 15, 2018 · 5 comments
Closed

[Azure] Figure out if to use serverless or load blalancer #421

alonttal opened this issue May 15, 2018 · 5 comments

Comments

@alonttal
Copy link
Collaborator

alonttal commented May 15, 2018

estimated time: 8 hours

@alonttal alonttal added this to the End of Semester Demo milestone May 15, 2018
@alonttal alonttal added this to Backlog in Roommates via automation May 15, 2018
@alonttal alonttal moved this from Backlog to To do (planned for this week but not started) in Roommates May 15, 2018
@OrAbramovich OrAbramovich moved this from To do (planned for this week but not started) to Backlog in Roommates May 22, 2018
@OrAbramovich
Copy link
Collaborator

Time estimation: 4 hours.
Due date: 26.05

@OrAbramovich OrAbramovich moved this from Backlog to To do (planned for this week but not started) in Roommates May 22, 2018
@OrAbramovich
Copy link
Collaborator

Hi @Danielohayon ,

What is the status? Due date was yesterday.

@omrihuller omrihuller moved this from To do (planned for this week but not started) to In progress (started and working on it this week) in Roommates May 29, 2018
@omrihuller omrihuller moved this from In progress (started and working on it this week) to Backlog in Roommates May 29, 2018
@omrihuller
Copy link
Collaborator

the strategy for using azure

@omrihuller
Copy link
Collaborator

estimate: 0.5 hours

@omrihuller omrihuller moved this from Backlog to To do (planned for this week but not started) in Roommates May 29, 2018
@Danielohayon Danielohayon moved this from To do (planned for this week but not started) to In progress (started and working on it this week) in Roommates Jun 4, 2018
@Danielohayon
Copy link
Collaborator

Conclusion

After a lot of consideration we have concluded that the best way to go is with load balancing. This is because using serverless computing with Azure functions has it's drawbacks. Such as a need the change our server to be completely stateless which it is not right now, (One example is saving a token for the current connected user). In addition it's mentioned that the latency is a bit higher, while also not having a lot of documentation and support relatively to load balancing.
In addition as for load balancing it is much more suitable for our current situation. For example, the source IP address of the clients can be seen in the logs of the server which makes it easy to differentiate each of the clients that are connecting to the server. And it automatically deploys server in accordance with our current needs.

sources:

Azure Functions documentation
Azure Load Balancing documentation
Serverless computing pros and cons
Load Balancing pros and cons

Time Took:
4 hours.

Roommates automation moved this from In progress (started and working on it this week) to Done Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roommates
  
Done
Development

No branches or pull requests

5 participants