Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Model Context Protocol
    • Vector Database
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Quick Start Guides
    • Working with AI
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • Bluzelle
Bluzelle

This add-on is operated by Bluzelle

A highly distributed data caching service

Bluzelle

Last updated February 09, 2022

The Bluzelle add-on is currently in beta.

Table of Contents

  • Provisioning the add-on
  • Local setup
  • Using with Node.js
  • Troubleshooting
  • Migrating between plans
  • Removing the add-on
  • Support

Bluzelle DB is an add-on for providing data storage in a secure, scalable manner.

Features included:

  • Data is broken into shards and stored across a swarm of nodes
  • Easily scalable if more storage is required
  • Comes with BluzelleStudio which developers can use to view/manage their data
  • Full open-source code from Bluzelle’s Heroku Add-On Git Repository
  • Sample code implementation of a Heroku Application using the Bluzelle DB add-on

Bluzelle DB is accessible via an API and has supported client libraries for Python and Node.js.

Provisioning the add-on

Requirements before installing the Bluzelle DB add-on:

  • Install the Heroku CLI (see this page for installation instructions)
  • Deploy an application on Heroku

The Bluzelle DB add-on can be attached to a Heroku application using the Heroku CLI:

$ heroku addons:create bluzelledb:test -a YOURHEROKUAPP

After the add-on is successfully added, you can use the 3 configuration variables in your application’s code (your previously deployed Heroku application) to connect to the Bluzelle DB.

$ process.env.BLUZELLEDB_ADRESS (ex. ws://testnet.bluzelle.com)
$ process.env.BLUZELLEDB_PORT (ex. 51010)
$ process.env.BLUZELLEDB_UUID (ex. d5ffc87e-b447-43cd-980e-53feed3b1afe)

For more detailed instructions, please visit the Bluzelle DB add-on GitHub repository here.

Local setup

Environment setup

After you provision the add-on, it’s necessary to locally replicate its config vars so your development environment can operate against the service.

Use the Heroku Local command-line tool to configure, run and manage process types specified in your app’s Procfile. Heroku Local reads configuration variables from a .env file. To view all of your app’s config vars, type heroku config. Use the following command for each value that you want to add to your .env file:

$ heroku config:get ADDON-CONFIG-NAME -s  >> .env

Credentials and other sensitive configuration values should not be committed to source-control. In Git exclude the .env file with: echo .env >> .gitignore.

For more information, see the Heroku Local article.

Service setup

Bluzelle DB can be configured for use in a local development environment. To do this, you would export the environment variables mentioned above in Provisioning the add-on. You will then be able to run your service locally and it will talk to the Bluzelle API.

You can install the Bluzelle JS library to interact with your data in the Bluzelle DB.

Using with Node.js

To use the Bluzelle JS library, you must have Node.js and NPM installed.

Node.js applications will need to add the following entry into their package.json specifying the Bluzelle JS library.

npm install --save bluzelle
var BluzelleClient = require('bluzelle');

const bluzelle = new BluzelleClient(
        process.env.BLUZELLEDB_ADDRESS + ':' + process.env.BLUZELLEDB_PORT,
        process.env.BLUZELLEDB_UUID
    );

await bluzelle.connect();

For help with installing Node.js, please reference Installing Node.js via package manager on the Node.js website.

Troubleshooting

For any problems or needing guidance to connect to the Bluzelle DB using the Bluzelle DB add-on, please do not hesitate to reach out in the Bluzelle Gitter Channel.

Migrating between plans

Application owners should carefully manage the migration timing to ensure proper application function during the migration process.

To change your Bluzelle DB add-on plan, run the command:

$ heroku addons:upgrade bluzelledb:newplan

Removing the add-on

Please let us know in the Bluzelle Gitter Channel as to why you are removing the add-on! Your constructive feedback helps us improve.

To remove the add-on, you can run the following Heroku CLI command:

This will destroy all associated data and cannot be undone!

$ heroku addons:destroy bluzelledb
-----> Removing bluzelledb from sharp-mountain-4005... done, v20 (free)

Support

All Bluzelle DB support and runtime issues should be submitted via one of the Heroku Support channels. Any non-support related issues or product feedback is welcome at the Bluzelle Gitter Channel.

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Zara 4 Bonsai Elasticsearch

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices