Timeline for Microservice Architecture in Azure - Ideas for improving performance
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2020 at 21:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 16, 2020 at 21:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 17, 2019 at 20:34 | answer | added | Martin K | timeline score: 1 | |
| Dec 17, 2019 at 17:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 1, 2019 at 3:00 | history | tweeted | twitter.com/StackSoftEng/status/1178867135835181056 | ||
| Aug 19, 2019 at 17:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 21, 2019 at 17:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 22, 2019 at 17:00 | answer | added | tubakaya | timeline score: 1 | |
| Mar 15, 2019 at 21:42 | comment | added | Andre Laskawy | Maybe container indeed is the better choice. I had the same question in mind. We use durable functions just to make the communication between the functions possible. Alternatively the functions could communicate via HTTPTrigger, but i doubt this would be any faster at all. But you mentioned some good points, there is indeed the fact of the latency to bring the functions up we need do consider. | |
| Mar 15, 2019 at 21:20 | comment | added | JimmyJames | A couple points: you might want to look at containers again. They can also be managed in terms of scaling and infrastructure. I'm not saying they are a better here but you may have rejected them prematurely. Having said that, the second part of my question is why durable functions versus normal ones. It seems the cost is the same but I'm wondering if there's additional startup time given the persistence component. | |
| Mar 15, 2019 at 21:13 | comment | added | Andre Laskawy | The main argument was that no there is no need of any infrastructure work, because the functions are scaled automaticaly and dont need to be hosted inside a VM or Container. All infrastructure work will be done by azure. | |
| Mar 15, 2019 at 20:57 | comment | added | JimmyJames | These tend to be tradeoffs but I'll ask a couple more questions. I'm not very familiar with durable functions but, as I understand it, the main cost benefit of serverless functions is that you don't pay for them when they are not being used. The tradeoff for that has been that there is some latency to bring them up when requests are made. So are you expecting these to be idle and why did you decide on durable functions over stateless functions? Is it for fan-out, fan-in? | |
| Mar 15, 2019 at 20:31 | comment | added | Andre Laskawy | Well the typical answer: all of it! - Latency should be acceptable (a request made by a user should be answered directly). - The idea is to have high throughput caused by huge amount of users. Stream analysis, calculations made on user input, etc. - Cost should be low of course, that is one of the reason we choose azure functions. | |
| Mar 15, 2019 at 20:20 | comment | added | JimmyJames | Asynchronous designs tend to be more appropriate for optimizing throughput and/or handling handling uneven demand with a fixed amount of resources. What is your performance goal here? Are your trying to improve throughput, latency, or something else like cost per transaction? | |
| Mar 15, 2019 at 20:01 | comment | added | Andre Laskawy | Not very much, we still could change everything, what exactly would you suggest, or where do you see the problems? | |
| Mar 15, 2019 at 19:51 | comment | added | JimmyJames | It seems to me that almost every design choice here adds latency. How married are you to this design? | |
| Mar 15, 2019 at 19:39 | history | edited | Robert Harvey | CC BY-SA 4.0 |
edited title
|
| Mar 15, 2019 at 19:09 | history | reopened |
BobDalgleish Robert Harvey |
||
| Mar 15, 2019 at 16:38 | history | edited | Andre Laskawy | CC BY-SA 4.0 |
added 26 characters in body
|
| Mar 15, 2019 at 16:05 | review | Reopen votes | |||
| Mar 15, 2019 at 19:10 | |||||
| Mar 15, 2019 at 15:48 | history | edited | Andre Laskawy | CC BY-SA 4.0 |
added 130 characters in body
|
| Mar 15, 2019 at 15:00 | history | closed |
gnat Robert Harvey |
Needs details or clarity | |
| Mar 15, 2019 at 15:00 | review | Close votes | |||
| S Mar 15, 2019 at 15:05 | |||||
| Mar 15, 2019 at 14:45 | review | First posts | |||
| S Mar 15, 2019 at 15:05 | |||||
| Mar 15, 2019 at 14:43 | history | asked | Andre Laskawy | CC BY-SA 4.0 |