Joule
  • Welcome to Joule's Docs
  • Why Joule?
    • Joule capabilities
  • What is Joule?
    • Key features
    • The tech stack
  • Use case enablement
    • Use case building framework
  • Concepts
    • Core concepts
    • Low code development
    • Unified execution engine
    • Batch and stream processing
    • Continuous metrics
    • Key Joule data types
      • StreamEvent object
      • Contextual data
      • GeoNode
  • Tutorials
    • Getting started
    • Build your first use case
    • Stream sliding window quote analytics
    • Advanced tutorials
      • Custom missing value processor
      • Stateless Bollinger band analytics
      • IoT device control
  • FAQ
  • Glossary
  • Components
    • Pipelines
      • Use case anatomy
      • Data priming
        • Types of import
      • Processing unit
      • Group by
      • Emit computed events
      • Telemetry auditing
    • Processors
      • Common attributes
      • Filters
        • By type
        • By expression
        • Send on delta
        • Remove attributes
        • Drop all events
      • Enrichment
        • Key concepts
          • Anatomy of enrichment DSL
          • Banking example
        • Metrics
        • Dynamic contextual data
          • Caching architecture
        • Static contextual data
      • Transformation
        • Field Tokeniser
        • Obfuscation
          • Encryption
          • Masking
          • Bucketing
          • Redaction
      • Triggers
        • Change Data Capture
        • Business rules
      • Stream join
        • Inner stream joins
        • Outer stream joins
        • Join attributes & policy
      • Event tap
        • Anatomy of a Tap
        • SQL Queries
    • Analytics
      • Analytic tools
        • User defined analytics
          • Streaming analytics example
          • User defined analytics
          • User defined scripts
          • User defined functions
            • Average function library
        • Window analytics
          • Tumbling window
          • Sliding window
          • Aggregate functions
        • Analytic functions
          • Stateful
            • Exponential moving average
            • Rolling Sum
          • Stateless
            • Normalisation
              • Absolute max
              • Min max
              • Standardisation
              • Mean
              • Log
              • Z-Score
            • Scaling
              • Unit scale
              • Robust Scale
            • Statistics
              • Statistic summaries
              • Weighted moving average
              • Simple moving average
              • Count
            • General
              • Euclidean
        • Advanced analytics
          • Geospatial
            • Entity geo tracker
            • Geofence occupancy trigger
            • Geo search
            • IP address resolver
            • Reverse geocoding
            • Spatial Index
          • HyperLogLog
          • Distinct counter
      • ML inferencing
        • Feature engineering
          • Scripting
          • Scaling
          • Transform
        • Online predictive analytics
        • Model audit
        • Model management
      • Metrics engine
        • Create metrics
        • Apply metrics
        • Manage metrics
        • Priming metrics
    • Contextual data
      • Architecture
      • Configuration
      • MinIO S3
      • Apache Geode
    • Connectors
      • Sources
        • Kafka
          • Ingestion
        • RabbitMQ
          • Further RabbitMQ configurations
        • MQTT
          • Topic wildcards
          • Session management
          • Last Will and Testament
        • Rest endpoints
        • MinIO S3
        • File watcher
      • Sinks
        • Kafka
        • RabbitMQ
          • Further configurations
        • MQTT
          • Persistent messaging
          • Last Will and Testament
        • SQL databases
        • InfluxDB
        • MongoDB
        • Geode
        • WebSocket endpoint
        • MinIO S3
        • File transport
        • Slack
        • Email
      • Serialisers
        • Serialisation
          • Custom transform example
          • Formatters
        • Deserialisers
          • Custom parsing example
    • Observability
      • Enabling JMX for Joule
      • Meters
      • Metrics API
  • DEVELOPER GUIDES
    • Setting up developer environment
      • Environment setup
      • Build and deploy
      • Install Joule
        • Install Docker demo environment
        • Install with Docker
        • Install from source
        • Install Joule examples
    • Joulectl CLI
    • API Endpoints
      • Mangement API
        • Use case
        • Pipelines
        • Data connectors
        • Contextual data
      • Data access API
        • Query
        • Upload
        • WebSocket
      • SQL support
    • Builder SDK
      • Connector API
        • Sources
          • StreamEventParser API
        • Sinks
          • CustomTransformer API
      • Processor API
      • Analytics API
        • Create custom metrics
        • Define analytics
        • Windows API
        • SQL queries
      • Transformation API
        • Obfuscation API
        • FieldTokenizer API
      • File processing
      • Data types
        • StreamEvent
        • ReferenceDataObject
        • GeoNode
    • System configuration
      • System properties
  • Deployment strategies
    • Deployment Overview
    • Single Node
    • Cluster
    • GuardianDB
    • Packaging
      • Containers
      • Bare metal
  • Product updates
    • Public Roadmap
    • Release Notes
      • v1.2.0 Join Streams with stateful analytics
      • v1.1.0 Streaming analytics enhancements
      • v1.0.4 Predictive stream processing
      • v1.0.3 Contextual SQL based metrics
    • Change history
Powered by GitBook
On this page
  • Overview
  • Development principles
  • Component based architecture
  • GraalVM
  • In-memory analytics database
  • Rest API
  • Connectors

Was this helpful?

  1. What is Joule?

The tech stack

High level overview of technologies used within the Joule platform

PreviousKey featuresNextUse case enablement

Last updated 3 months ago

Was this helpful?

Overview

Joule's architecture principle is to always keep things simple but powerful.

The SDK provided, aids developers to customise and leverage key mature technologies that are able to support a wide array of use cases.

Development principles

When developing Joule, the desire was to keep the solution as small as possible to enable deployment on to any JVM supported hardware. This meant smaller independent established frameworks needed to be considered to provide the key features Joule needed.

Therefore, frameworks such as Spring were not consider even though the main developer has many years development experience using the Spring ecosystem. The result is, the use case deployment artifact size is reduced and can be managed to the components needed.

Selection consideration used:

  1. Has a strong community.

  2. Modern and proven in the wild.

  3. Lightweight with minimal dependencies.

  4. Best of breed within category.

  5. Standards based to enable solution switch if needed.

Component based architecture

Joule follows a component driven architecture approach to bring new features to the platform incrementally while leveraging existing assets.

GraalVM

However, further benefits such as fast process startup time, lean runtime and low resource usage has made this a no-regrets decision.

Key features used:

  • Compile and Runtime JRE

  • Dynamic scripting support for Python, Javascript and Node.js

In-memory analytics database

This is a lightweight, open-source, portable and performant modern database solution that is gaining significant traction since v1.0.0.

Key features used:

  • Event capture and storage

  • Metrics engine

  • Enrichment processing

  • Data export

  • Low-latency data access

Rest API

Open access to a Joule nodes is through Rest APIs.

Key features used:

  • Jetty Http server

  • OpenAPI and Swagger Docs

  • Web sockets for event ingestion and distribution

  • SSL support

Connectors

All developed connector integrations could have easily been provided using the Sprint Integration framework at an overhead cost which was not acceptable. This has meant a focused approach on the key OOTB solutions provided.

All connector integrations are developed against client libraries and updated every six months.

was primarily chosen for its ability to support Python and Javascript within the Java processing environment.

Joule uses as an internal analytics database solution.

The web framework library is used due to its lightweight, simple and flexible approach to development.

GraalVM
DuckDB
Javalin
Joule works alongside your existing data and visualisation platforms so you can focus delivering value add use cases.