Executing commands

Configuration

Every micro service is listening on two RabbitMQ queues, one for data ingestion and second for command execution.

Command execution

You could ask why do we need commands at all? As we may be running more than just one instance of the individual micro services, or we might want to control the flow of the data (like batch processing with "flush" commands), we need to make sure only one micro service executes the following command.

In order to execute your desired command, simply send a valid JSON command over micro service's RabbitMQ commands queue, specified in your configuration file.

As an example you could take Billing micro service's invoice generation commands.

Develop your own

If you decide to implement your own command, first select which micro service should be executing it. Let's say you are designing an event processing command for your UDR micro service, then proceed by creating a new class that inherits from Commands parent class, has name that corresponds with _class JSON field, and Java class file is located in:

/core/udr/src/main/java/ch/icclab/cyclops/consume/command/model/

Now you can start developing your command and if you need to pass some arguments, simply register them in the Java class the same way as you would do it in a POJO class, where those object variables will be filled based on their corresponding JSON fields, or left as null/defaults.

InfluxDB

We will be providing couple of tools for you, one of which is standardised interface for time series data operations.

QueryBuilder

To access time series data you will need to create a query builder with measurement's name

QueryBuilder query = new QueryBuilder(name);

Because a builder pattern is utilised, you can continue and add another statements:

• select(String field);
• select(String ... fields);
• count(String field);
• where(String key, Object value);
• where(String key, String delimiter, Object value);
• and(String key, Object value);
• and(String key, String delimiter, Object value);
• timeFrom(Long time, TimeUnit unit);
• timeTo(Long time, TimeUnit unit);
• groupBy(String key);
• orderDesc();
• limit(Integer lmt);
• offset(Integer off);

It is not necessary to specify select(*) as all fields are returned by default, only use select method to slice data, where the same applies to default ascending order.

This is just one of the possible examples:

QueryBuilder query = new QueryBuilder("CloudStackIPUsageData");
query.timeFrom(1451650521, TimeUnit.SECONDS)
query.timeTo(1467375357, TimeUnit.SECONDS);
query.where("account", "martin");
query.and("usage", ">", 15);

Executing and parsing

The next logical step is to execute prepared query and parse its result. Here you have two options how to proceed, either getting back List<Map> or List<YourClass>:

InfluxDBClient client = InfluxDBClient.getInstance();
List<Map> maps = client.executeQuery(builder);
List<Own> own = client.executeQueryAndMapItToClass(builder, Own.class);

RabbitMQ