♻️ Investigate on Migrating to Bot Framework SDK

[jimmidier]

Cc: @adamcogan @pierssinclairssw @DavidAbraham082

Pain

Migrating from Bot Framework Composer to Bot Framework SDK has pros and cons. Now we have received lots of feedback, it's time to review them and make the decision.

Tasks

• [ ] Review feedback
• [x] List pros and cons
• [ ] Make decision

Thanks!

[duanxinhuan]

Hi @adamcogan @jimmidier @ravidhaduk,

I have done an investigation on Bot SDK Framework and find some pros and cons.

Pros:

1. It will make the flow reusable.
2. Since the flow is reusable, then when we try to sell the BotFramework out, we can give them a relatively low quote.
3. Using Bot SDK will increace the maintainability, the flow chart is a pain to maintain
4. We can have a dialogue fully stateful with Bot SDK
5. Manage multiple dialogue effectively

cons:

1. Personally, I think the documentation is not that good
2. The Learning curve for SDK is steep, we need a good architecture for it
3. We will need to redo some work

Suggestion:

In my opinion, If we want to keep BotFrame work for inner use, we can keep what we have for now.But if we want commercial use, we need to change to SDK, because it allows us to reuse the flow efficiently and effectively.

Let's just make an simple architecture and test the concept while fixing the issue #500 and the issue #193. So we can have something to refer to when we actually sell SophieBot to a client.