Compare Microsoft Bot Framework with Howdy Botkit

I am looking to create a bot and run into the Microsoft Bot Framework (with LUIS or can use the C # SDK provided by API.AI) and Howdy.ai Botkit (with middleware support for LUIS and API.AI).

Can someone help me with comparing the two?

I am looking for the following things in my bot -

  • Support for multiple channels, including email.
  • Ask the bot to act both react (respond to some message from the user) and proactively (send messages to users once a day about something important for them or subsequent actions) Behavior.
  • Save and then retrieve user-provided data (manage state).
  • Support Rich Message.
  • Answer late.
  • Conversation history management.

Are there things that are available in one but not in the other?

+5
source share
1 answer

I tried to develop a bot in Botkit and MS Bot. I ended up going with the MS bot framework. Some of my reasons that might help in comparison are:

  • MSBotFramework supports skype, slack, telegram, Facebook and many other channels. BotKit, the last thing I checked, supported only Facebook and slack. I aimed at skype and telegram, and it was a deal interruption.
  • Botkit currently has a value of node.js. On the other hand, MSBotFramework has .Net, node.js, and even a REST API (which basically means that you can use it from any language you want). In addition, there are python shells available that use the REST API.
  • As a Microsoft product, integrating MSBotFramework with skype, azure, azure analytics, LUIS, and other Microsoft services is very simple. This may be required to develop, deploy, or integrate natural language support. Botkit supports LUIS integration, which is quite simple (perhaps as simple as MSBotFramework). The analytics (via botkit studio) (was) very simple, and MSBotFramework wins here.
  • I found the documentation for MSBotFramework more complete than Botkit, but both of them have the same amount of resources and documentation.

Some of the other questions you asked about:

  • Proactive messages depend on the channel for which you are developing. E.g. Facebook allows you to set the time to 24 hours from the last user message in which you can reply. While other platforms, such as skype and telegram, allow you to send a message at any time convenient for you.
  • State management should be handled by you. The Bot Framework provides some mechanism, but it is not strong enough for use in production. msdoc
  • Rich messages depend on the platform, but the bot structure is very well suited for most of them. So, how it works, you send a message to the bot frame in your own message format. It is converted to platform format. If you have only one or two platforms, you can develop accordingly.
  • Answer belatedly - you will have to implement it yourself, although the bot framework has many examples of this. github li>
  • Conversation management can be done easily if you use C # and the .NET platform as a whole. The documentation and the number of examples are very impressive. github repo for samples

In general, I would recommend the MS bot framework.

+5
source

Source: https://habr.com/ru/post/1260135/


All Articles