Key factors IoT developers should keep in mind when selecting the right database
Data collection is a top concern for IoT developers. When selecting the right database, it’s important to keep a few factors in mind. We talked to Fred de Haro, CEO & co-founder of Pycom about the key factors and concerns, the challenges IoT developers face when bringing their projects to the market and more.
JAXenter: What are the challenges IoT developers face when bringing their projects to the market?
Fred de Haro: Getting an idea to market before anyone else, and in many cases before running out of cash, can be a hurdle. Most developers can only afford to keep projects going for a few months before requiring significant funding, making it difficult for SME’s to fund large production volumes, and finding the right manufacturing partner can be a long process and full of risk.
JAXenter: What is the solution? How can we tackle those challenges?
Fred de Haro: The solution for this challenge is for developers to collaborate with companies that not only help them with end-to-end development of their IoT projects, but assist them in the manufacturing process to ensure their ideas are brought to market before funding runs out, and doing so without charging extortionate amounts of money.
To produce good IoT products developers need to cover a full IoT stack including hardware, wireless networking and cloud-based software such as middleware and visualisation platforms.
JAXenter: What are the trends that IoT developers should follow this year?
Fred de Haro: The trends that are top of mind for me right now are: the rise in IoT consumer wearables. Over the years, IoT wearables have become more personalized than ever before. It’s already a growing market and it will be interesting to see how this trend evolves over the next few years.
JAXenter: What are the most popular tools IoT developers should include in their toolkit?
Fred de Haro: IoT development is multidisciplinary. To produce good IoT products developers need to cover a full IoT stack including hardware, wireless networking and cloud-based software such as middleware and visualisation platforms. That’s a mixture of both software or hardware so they need, first of all, a powerful laptop with a long-lasting battery.
Then, for the microcontroller hardware part, our developers use multimeters, signal analyzers, programmers and debuggers of various sorts. They also need access to more basic things such as tweezers, a soldering iron, hot-glue gun, breadboards, drilling machine, DC power supply, lots of resistors, capacitors, transistors, LEDs and diodes.
For software, we recommend that developers set up a GitHub or GitLab repo, have access to a solid IDE (the application that enables microcontroller programming). There are various options and what is considered top notch is dependent on the type of hardware platform the developer is using. Development of IoT products also requires access to a middleware platform that enables device and telemetry data management and visualisation.
Not all brands of elements in the stack are compatible so developers should make sure all components work together.
- Laptop + IDE
- Microcontroller Hardware and sensors
- Middleware/visualisation platform
JAXenter: What database technologies should developers use for their IoT solutions?
Fred de Haro: Data collection is a top concern for IoT developers. When selecting the right database, it’s important to keep a few factors in mind including the ability to unlock powerful IoT insights, successful integration with existing IT systems as well as end-to-end compatibility and lifecycle solution management. The most popular database technologies used by Pycom developers is the Riak time series (TS) noSQL database, which is open-source and optimised for IoT.
JAXenter: What are the key IoT concerns right now?
Fred de Haro: The key IoT concerns right now are hardware integration and connectivity. At Pycom, we help power over 250,000 developers, enterprises and education establishments and ensure their projects remain reliably connected.