System design: Server driven flow for “DMV” type application
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I would like to create an app that would be shipped to a user and be updated once in few months. This app will include an "application" flow, similar to the one a person would fill out DMV. The app will communicate with the backend server (that I would host) via JSON payloads.
Requirements:
- Business logic to live in the backend server (where I would have more control)
- The app will be driven by the backend server, ie the backend server will tell the app exactly what to do.
- I would like to like collect information if users start "application" and where they are in the process.
- "Application" pages must be completed in specific order (order should be defined in the backend server)
The current approach I am thinking is as follows:
Design the app as a template renderer. It would be shipped with bunch of templates for each page of the "application". As soon as user clicks starts "application" within app, the backend server will tell the app which template to render.
For example, user clicks "start application", app will send a request to backend server to create new "application", backend server will create application in the database, and tell the app that the next step is to "Collect User's Address". This step would correspond to the template in the app, which app will render to a user, collect user's home address and send data back to the backend server (along with "application" id) and so on until the application will be complete by the user. (in the backend, application will have state machine that will ensure that application is completed in order)
I feel like there are pros and cons of such approach.
What are some design patterns for solving such problems?
I also read on hypermedia approach and I like it but the problem with that is each page in the app would be a webpage, which I don't necessarily like.
client-server system-design
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
add a comment |
I would like to create an app that would be shipped to a user and be updated once in few months. This app will include an "application" flow, similar to the one a person would fill out DMV. The app will communicate with the backend server (that I would host) via JSON payloads.
Requirements:
- Business logic to live in the backend server (where I would have more control)
- The app will be driven by the backend server, ie the backend server will tell the app exactly what to do.
- I would like to like collect information if users start "application" and where they are in the process.
- "Application" pages must be completed in specific order (order should be defined in the backend server)
The current approach I am thinking is as follows:
Design the app as a template renderer. It would be shipped with bunch of templates for each page of the "application". As soon as user clicks starts "application" within app, the backend server will tell the app which template to render.
For example, user clicks "start application", app will send a request to backend server to create new "application", backend server will create application in the database, and tell the app that the next step is to "Collect User's Address". This step would correspond to the template in the app, which app will render to a user, collect user's home address and send data back to the backend server (along with "application" id) and so on until the application will be complete by the user. (in the backend, application will have state machine that will ensure that application is completed in order)
I feel like there are pros and cons of such approach.
What are some design patterns for solving such problems?
I also read on hypermedia approach and I like it but the problem with that is each page in the app would be a webpage, which I don't necessarily like.
client-server system-design
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
add a comment |
I would like to create an app that would be shipped to a user and be updated once in few months. This app will include an "application" flow, similar to the one a person would fill out DMV. The app will communicate with the backend server (that I would host) via JSON payloads.
Requirements:
- Business logic to live in the backend server (where I would have more control)
- The app will be driven by the backend server, ie the backend server will tell the app exactly what to do.
- I would like to like collect information if users start "application" and where they are in the process.
- "Application" pages must be completed in specific order (order should be defined in the backend server)
The current approach I am thinking is as follows:
Design the app as a template renderer. It would be shipped with bunch of templates for each page of the "application". As soon as user clicks starts "application" within app, the backend server will tell the app which template to render.
For example, user clicks "start application", app will send a request to backend server to create new "application", backend server will create application in the database, and tell the app that the next step is to "Collect User's Address". This step would correspond to the template in the app, which app will render to a user, collect user's home address and send data back to the backend server (along with "application" id) and so on until the application will be complete by the user. (in the backend, application will have state machine that will ensure that application is completed in order)
I feel like there are pros and cons of such approach.
What are some design patterns for solving such problems?
I also read on hypermedia approach and I like it but the problem with that is each page in the app would be a webpage, which I don't necessarily like.
client-server system-design
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
I would like to create an app that would be shipped to a user and be updated once in few months. This app will include an "application" flow, similar to the one a person would fill out DMV. The app will communicate with the backend server (that I would host) via JSON payloads.
Requirements:
- Business logic to live in the backend server (where I would have more control)
- The app will be driven by the backend server, ie the backend server will tell the app exactly what to do.
- I would like to like collect information if users start "application" and where they are in the process.
- "Application" pages must be completed in specific order (order should be defined in the backend server)
The current approach I am thinking is as follows:
Design the app as a template renderer. It would be shipped with bunch of templates for each page of the "application". As soon as user clicks starts "application" within app, the backend server will tell the app which template to render.
For example, user clicks "start application", app will send a request to backend server to create new "application", backend server will create application in the database, and tell the app that the next step is to "Collect User's Address". This step would correspond to the template in the app, which app will render to a user, collect user's home address and send data back to the backend server (along with "application" id) and so on until the application will be complete by the user. (in the backend, application will have state machine that will ensure that application is completed in order)
I feel like there are pros and cons of such approach.
What are some design patterns for solving such problems?
I also read on hypermedia approach and I like it but the problem with that is each page in the app would be a webpage, which I don't necessarily like.
client-server system-design
client-server system-design
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
asked Nov 14 '18 at 4:01
Sargis Plus PlusSargis Plus Plus
25110
25110
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293016%2fsystem-design-server-driven-flow-for-dmv-type-application%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293016%2fsystem-design-server-driven-flow-for-dmv-type-application%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
