You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Abstract
Build/Suggest me a stack works on the principle of asking user basic questions on what they wish to do and what are some of basic tech requirements. The h2h engine can then use data from various tech products to suggest a suitable stack for the user.
The Build me a stack can further go on the deploy a bare minimum setup based on suggested technologies on the users account and provide them with end points to interact with
Proposed Framework
I am tinkering with the idea of using workflows for this feature. Based on an entry point(say a static 'no clue what you want' node') the user is given questions. Each question is embedded with hints on what the target tech and filters would correspond to, also keeping in mind previous answers. This would then lead the user down one of the paths of the workflow and ultimately providing the required stack
Example
Do you wish to use NoSql | Yes/No
If yes:
[options] : Couch/Mongo/Cassandra/etc?
[Next - question ] Would you require attribute level filtering capabilities | Yes/No
if yes:
[options] couch/mongo
else:
[options] cassandra
else:
[options] mysql, oracle, postgres
The evaluator would pick hints to provide the next possible path.
It also will allow easily adding new flows into the system as the product matures
@rahulmamgain @heckdevice Let me know if this makes sense and I can then try to build a framework with some norms on the same
The text was updated successfully, but these errors were encountered:
Giving this more thought I think I am missing a key point - how does the user interact
Does the h2h stack builder give static questions
"do you want to go with a private or public cloud?"
"Do you want a replicated DB"?
"Do you want to store JSON structures"?
There are infinite set of questions that could lead to a single choice of say DB or cloud platform?
I am not sure how this works
@rahulmamgain some comment in your spare time por favor
Abstract
Build/Suggest me a stack works on the principle of asking user basic questions on what they wish to do and what are some of basic tech requirements. The h2h engine can then use data from various tech products to suggest a suitable stack for the user.
The Build me a stack can further go on the deploy a bare minimum setup based on suggested technologies on the users account and provide them with end points to interact with
Proposed Framework
I am tinkering with the idea of using workflows for this feature. Based on an entry point(say a static 'no clue what you want' node') the user is given questions. Each question is embedded with hints on what the target tech and filters would correspond to, also keeping in mind previous answers. This would then lead the user down one of the paths of the workflow and ultimately providing the required stack
Example
The evaluator would pick hints to provide the next possible path.
It also will allow easily adding new flows into the system as the product matures
@rahulmamgain @heckdevice Let me know if this makes sense and I can then try to build a framework with some norms on the same
The text was updated successfully, but these errors were encountered: