Should I build inside ThingWorx or outside of ThingWorx?
Devices – usually outside ThingWorx
Applications, UI, services – usually inside ThingWorx
- If your system needs real-time connectivity to or from the ThingWorx platform.
- If your system only pushes data into a ThingWorx platform.
- If you have an existing application and want to leverage ThingWorx functionality.
Pros: Your integration uses hardened and ThingWorx supported toolkits or APIs. Changes to your system such as adding a new sensor, automatically propagates to the ThingWorx Platform.
Cons: May require modifications to each system instance instead of one modification to the ThingWorx Platform. For applications, may limit the ThingWorx functionality available to your users.
If you want to learn more about technologies for building content outside of ThingWorx, click here.
- If your system has a web API that is accessible from a ThingWorx platform, you can create Marketplace content that a ThingWorx developer can use to access your API
- If your system has an API or firmware that cannot be changed then the only option is to build inside ThingWorx
- If your system is a reusable UI component.
Pros: ThingWorx users can get the integration from the ThingWorx Marketplace themselves and install it in their system hassle free. You system can be combined with other Marketplace content to quickly create a full solution.
Cons: May not be able to pull data into ThingWorx or contact your system in real-time. Changes to your system such as adding a new sensor, do not automatically propagate to the ThingWorx Platform.
If you want to learn more about technologies for building content inside of ThingWorx, click here.
Note: It is possible to create Marketplace content by making changes to both your system and ThingWorx if necessary