You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

BellaDati IoT Data Collector is a Java based application with micro-services architecture. It is available as a cloud-based service or can be deployed on your own hardware in your infrastructure.

This page describes the supported platforms and system requirements for version 0.6+.

Server

Hardware

In an on-premise environment, a Collector installation consists of multiple distributed modules. These can run on the same computer or on different machines. For evaluation purposes, it is usually sufficient to run all modules on the same computer, e.g. a developer workstation.

Collector hardware requirements mainly depend on the amount of data being processed and the number of concurrent requests during peak minutes. To ensure optimal performance under any circumstances, we group our hardware requirements in 3 tiers depending on usage characteristics. Please note that even so, these configurations can only be guidelines and actual requirements and performance can heavily depend on your usage pattern.

We would appreciate if you could let us know what hardware configuration works in your environment. Please create a ticket in our support system, describing your hardware configuration as well as the number of sensors and data records in your Collector installation.


Minimal Configuration

This configuration is recommended for a less than 100 sensors where each sensor is sending up to 60 requests every minute. We strongly suggest using this kind of configuration for basic demo purposes only. Please verify that target machine meets following minimal configuration, because Collector needs sufficient resources (free RAM, CPU, free disk space) to run correctly.

Deployment modeOne machine for all modules

Count of Audit modules

1

Count of Receiver/Sender modules

1-4

Machine

CPU

1x 2 GHz 32/64-bit Intel Xeon or comparable

RAM

1 GB

Disk

1 GB

Network

3G


Medium-load Configuration

This configuration is recommended for up to 1.000 sensors where each sensor is sending up to 60 requests every minute. We recommend running the modules on different machines for this configuration. For HA requirements please double count of modules/machines.

Deployment modeDistributed

Count of Audit modules

1

Count of Receiver/Sender modules

1-10

Machine for Audit module

CPU

1x 2 GHz 64-bit Intel Xeon or comparable

RAM

2 GB

Disk

20 GB, 10,000 rpm, IDE / SCSI

Network

100 Mbps

Machine for Receivers and Senders (linked and running together)

CPU

2x 2 GHz 64-bit Intel Xeon or comparable

RAM

2 GB

Disk

20 GB, 10,000 rpm, IDE / SCSI

Network

100 Mbps

It's possible to run medium load configuration on one, more powerful server, e.g. 4xCPU cores, 4GB RAM, 40GB HDD.

High-load Configuration

This configuration is recommended for a 1.000 - 1.000.000 sensors where each sensor is sending up to 60 requests every minute. It is necessary to run modules on different machines for this configuration. For HA requirements please double count of modules/machines.

Deployment modeDistributed

Count of Audit modules

1

Count of Receiver/Sender modules

count of sensors / 1000

Machine for one Audit module

CPU*

32x 2 GHz 64-bit Intel Xeon or comparable

RAM*

60 GB

Disk*

300 GB, 10,000 rpm, SSD

Network*

10 Gbps

*Depends on actual count of sensors and size of one sensor request. Provided value is for 1.000.000 sensors and request size 150 bytes.

Machine for Receivers and Senders (linked and running together)

CPU

2x 2 GHz 64-bit Intel Xeon or comparable

RAM

4 GB

Disk

20 GB, 10,000 rpm, SSD

Network

500 Mbps


Operating System

Collector can run on any operating system for which a supported Java 8+ is available. Such operating systems include:

  • Microsoft Windows Server 2012
  • Microsoft Windows 10
  • Microsoft Windows 8
  • Microsoft Windows 7 (manual only)
  • Linux distributions (SuSE Linux, RedHat, CentOS, Ubuntu)
  • Solaris
  • Mac OS X

 

Collector officially supports Oracle Java and IBM Java distributions.

  • No labels