Click here to Skip to main content
15,885,216 members
Home / Discussions / Design and Architecture
   

Design and Architecture

 
QuestionFile Sharing App Proposed Architecture Pin
Kevin Marois10-Feb-16 11:20
professionalKevin Marois10-Feb-16 11:20 
AnswerRe: File Sharing App Proposed Architecture Pin
Richard Deeming11-Feb-16 0:38
mveRichard Deeming11-Feb-16 0:38 
GeneralRe: File Sharing App Proposed Architecture Pin
Kevin Marois11-Feb-16 3:39
professionalKevin Marois11-Feb-16 3:39 
QuestionArchitecture - handling consecutive updates - Azure Pin
Rajeshjoseph9-Feb-16 5:13
Rajeshjoseph9-Feb-16 5:13 
AnswerRe: Architecture - handling consecutive updates - Azure Pin
Eddy Vluggen9-Feb-16 6:45
professionalEddy Vluggen9-Feb-16 6:45 
AnswerRe: Architecture - handling consecutive updates - Azure Pin
Gerry Schmitz9-Feb-16 17:40
mveGerry Schmitz9-Feb-16 17:40 
AnswerRe: Architecture - handling consecutive updates - Azure Pin
jschell12-Feb-16 12:21
jschell12-Feb-16 12:21 
GeneralRe: Architecture - handling consecutive updates - Azure Pin
Rajeshjoseph16-Feb-16 4:55
Rajeshjoseph16-Feb-16 4:55 
The architecture was proposed this way due to the following reasons:
1. There are multiple channels through which the core backend systems (system of records) will get updated - Web, Mobile App etc. To have these updated records always reflecting in the cloud, we are bringing the data from backend to cloud if a record gets updated. Web always reads the data from the cloud.
2. Since we are decoupling the core backend systems from the system of access for web, we are building a data repository in cloud for the web to access which will not have direct communication to the core backend systems (asynchronous in nature).
3. Since the backend updates will be asynchronous (it can vary from near to real-time to 1 hour depending upon various factors), it may not be fair to display the customer a message "you request will be processed later" when the customer updates his/her profile information or similar (no customer would love to see his name change to reflect after xx minutes). For this reason, the update will be directly saved to the DB in the cloud and will be read from the there by the web.
4. I was trying to work out a solution for a scenario where a customer updates his "First Name" twice in the interval of say 5 minutes - in this scenario - with the planned architecture - the second update will be displayed on the web as soon as it is done, while the first update will be in transit, making it's way to the core database asynchronously and as I mentioned in step 1, the core backend systems will send the record to the web again if they are updated (the update can happen from multiple channels) and will update the cloud DB which will re-write the second update for this record in cloud. After few minutes, the second record also will complete the round trip and will reach the cloud. But, during the time between the second update saved in the cloud, and completes the round trip - there is a possibility that the customer notices the first update getting displayed for few minutes.
Hope this explains!
GeneralRe: Architecture - handling consecutive updates - Azure Pin
Wayne Stewart_16-Feb-16 13:11
Wayne Stewart_16-Feb-16 13:11 
GeneralRe: Architecture - handling consecutive updates - Azure Pin
jschell19-Feb-16 12:55
jschell19-Feb-16 12:55 
AnswerRe: window application form work in KIOSK Pin
Eddy Vluggen9-Feb-16 6:46
professionalEddy Vluggen9-Feb-16 6:46 
GeneralRe: window application form work in KIOSK Pin
Richard MacCutchan9-Feb-16 7:24
mveRichard MacCutchan9-Feb-16 7:24 
GeneralRe: window application form work in KIOSK Pin
Eddy Vluggen9-Feb-16 7:40
professionalEddy Vluggen9-Feb-16 7:40 
GeneralRe: window application form work in KIOSK Pin
tracie.macmoon8-Mar-16 22:29
tracie.macmoon8-Mar-16 22:29 
AnswerRe: window application form work in KIOSK Pin
ZurdoDev9-Feb-16 8:38
professionalZurdoDev9-Feb-16 8:38 
GeneralRe: window application form work in KIOSK Pin
Gerry Schmitz9-Feb-16 18:01
mveGerry Schmitz9-Feb-16 18:01 
Questionflyweight design pattern - need some explanation Pin
D4rkTrick7-Feb-16 12:03
professionalD4rkTrick7-Feb-16 12:03 
AnswerRe: flyweight design pattern - need some explanation Pin
Gerry Schmitz8-Feb-16 6:46
mveGerry Schmitz8-Feb-16 6:46 
Generalmisleading example Pin
D4rkTrick8-Feb-16 9:06
professionalD4rkTrick8-Feb-16 9:06 
GeneralRe: misleading example Pin
Gerry Schmitz8-Feb-16 13:10
mveGerry Schmitz8-Feb-16 13:10 
Praisethanks Pin
D4rkTrick11-Feb-16 1:22
professionalD4rkTrick11-Feb-16 1:22 
GeneralHow to design the accessibility problem Pin
SSETH7-Feb-16 5:21
SSETH7-Feb-16 5:21 
SuggestionRe: How to design the accessibility problem Pin
Sascha Lefèvre7-Feb-16 5:44
professionalSascha Lefèvre7-Feb-16 5:44 
GeneralRe: How to design the accessibility problem Pin
SSETH7-Feb-16 7:29
SSETH7-Feb-16 7:29 
GeneralRe: How to design the accessibility problem Pin
Richard MacCutchan7-Feb-16 21:05
mveRichard MacCutchan7-Feb-16 21:05 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.