Karthik Raveendran

GoLand was preferred over VS Code. GoLang plugin for VS code suffers from inconsistent behavior, auto completion issues. Support for packaging modules like dep/go modules is better in GoLang. Debugger integration is pretty poort in VS Code for GoLang

Was chosen over HiveMQ due to HiveMQ's proprietary nature and the pricing model. The platform was initially built with HiveMQ as the channel to publish sensor events over MQTT. VerneMQ was analyzed but we needed a shared subscription model to client side load balancing for for a host of Kafka MQTT consumers. VerneMQ didn't support this feature when we started building the platform. We later migrated to VerneMQ when they started supporting shared subscriptions from version 5.0

The platform deals with time series data from sensors aggregated against things( event data that originates at periodic intervals). We use Cassandra as our distributed database to store time series data. Aggregated data insights from Cassandra is delivered as web API for consumption from other applications. Presto as a distributed sql querying engine, can provide a faster execution time provided the queries are tuned for proper distribution across the cluster. Another objective that we had was to combine Cassandra table data with other business data from RDBMS or other big data systems where presto through its connector architecture would have opened up a whole lot of options for us.