Got a question you don’t see here? Let us know so we can add it! support@rotational.io

Account Creation

Questions about setting up your account.

How do I sign up for an Ensign account?

We are so glad you are interested in checking out Ensign! You can register here and check out the quickstart guide to get started!

How much does Ensign cost?

We are working on figuring that out. For now, there is no cost because we want developers and data scientists to experiment and build what they can imagine with eventing or streaming superpowers ;-D

Eventually, we will have to charge to be sustainable, but we do commit to always having a free tier for experimenters and builders.

Our paid tier will be 1-2 orders of magnitude cheaper than other managed eventing platforms (e.g. Confluence, Redpanda. Google Pubsub).

What are Ensign “tenants”?

The term “tenant” in cloud computing refers to the sharing of compute and storage resources in virtual machines and servers.

When you create a new account with a cloud service or SaaS provider like AWS, Auth0, or Ensign, the service provider instantiates a “tenant” for you. The provider then allocates some amount of compute and storage resources to your tenant. You and only you (well, and the other people at your organization) may read from, write to, delete, or otherwise access the resources on your tenant.

An organization can have multiple tenants, e.g. Dev, Prod, Staging.

What are Ensign “organizations”?

Who should have permission to read from, write to, delete, or otherwise access your topics? In Ensign, you create an organization and invite those people so that you can grant roles and adjust permissions for each teammate. You can have an organization of one, but it’s not as fun 😉

What do I need to do to get set up?

With Ensign, you can set up any number of secure event streams — also called topics — for a project or use case. This allows you to customize how to move data in your application or organization, to where it is most useful. You don’t need specialized skills, tools, or infrastructure. Just an API key and a few lines of code.

Are my event streams and data secure?

We designed Ensign with security-first principles, including Transparent Data Encryption (TDE), symmetric key cryptography, key rotation, JWT-based authentication and authorization, and Argon2 hashing. All events are encrypted by default, and customers are empowered to control how cryptography occurs for their own data within the Ensign system.

When you set up your Ensign tenant, you’re issued server-side global keys. Your API keys are shown to you and only you, once and only once. These keys are stored in a globally replicated key management system and you can revoke them using the management UI. Once you revoke keys, data encrypted with those keys is no longer accessible.

Ensign never stores raw passwords to access the developer portal. We use the Argon2 key derivation algorithm to store passwords and API key secrets as hashes that add computation and memory requirements for validation.

For enterprise clients, we deploy instances of Ensign in virtual private clouds (VPCs).

What is Ensign?

What is Ensign? How does it fit into other database, eventing, and mlops tools I’ve heard about?

What is an event stream (aka data stream)?

You can think of an event stream as a pipeline through which data flows, much like pipes that move water in your home. You can use an event stream to connect data sources that produce or emit data (events) to data sinks that consume or process the data. A data source or producer that emits data can be a database, a data warehouse, a data lake, machines, edge devices or sensors, microservices, or applications. A data sink or consumer can be a web or mobile application, a machine learning model, a custom dashboard, or other downstream microservices, sensors, machines, or devices like wearables.

What can I use an event stream for?

Event streams are applicable to almost any use case that benefits from the continuous flow of data.

Generally speaking, developers can use an event stream to build event-driven applications. Think about how satisfying it is as a customer when you see your data update in real time — whether it’s being able to watch your package move closer and closer to being delivered, or your fitness tracker updating throughout your cardio session. These kind of rich, interactive, and personalized experiences depend on an underlying stream of data flowing in to the application.

Data scientists can also find substantial value in event streams; in fact, some of the earliest deployed machine learning apps were event-driven! That’s right — back in the 90’s, email spam filters used Bayesian models to learn on the fly. Imagine how much more robust our models would be if they were not only trained on the freshest data, but could alert you to things like data drift as soon as they happened — you’d be able to react immediately as opposed to a batchwise process where you’d be lucky to catch the issue within a day! Check out our Ensign resources for data scientists here .

Event streams can also play a huge role in process automation for data engineers and database administrators. Eventing can streamline ETL processes and enable database maintenance and scaling without the danger of data loss or application downtime. You can even use eventing to provision data more securely, updating event encryption to turn on and off access for downstream processes and users. Check out our Ensign resources for data engineers here .

What are Ensign “projects”?

How does your organization group its datasets? In traditional storage, related data is stored in a database. An Ensign project defines a collection of datasets related by use case.

What are Ensign “topics”?

How does your organization normalize data? Traditional relational database management systems (RDBMS) break data down into tables that describe objects. Ensign topics are the same, but also capture all changes to every object (in chronological order!).

What should I name my topics? Are there good naming conventions?

First and foremost, consider your teammates when you name your topics. Come up with names that facilitate communication, not cause confusion. Check out this handy resource we put together to help you.

Where does the data go? Where do my topics live?

Ensign is a hosted solution, which means that the data goes to (“lives in”) virtual servers and machines that are maintained by Rotational Labs.

For enterprise clients, we happily deploy private instances of Ensign within the cloud provider or virtual private cloud (VPC) of your choice, or even on-prem. We have deployed on Google Cloud, AWS, Azure, and Linode.

What does it mean to persist data?

Data persistence is a mechanism for saving data in a way that will protect it from failures like power outages, earthquakes, server crashes, etc.

Think about how stressful it would be if you were depositing money at an ATM, and the ATM screen shorted out and went black before your bank had a chance to update your account balance in their database! Or what if you were buying concert tickets online, and the ticket sales website crashed after your payment went through but before your Taylor Swift tickets were issued!

Considering how important data persistence is to fostering trust in consumer-facing contexts, you might be surprised to learn that most streaming tools don’t provide data persistence! Some only save data for a few days before it is discarded, some must be specially configured to save data, and others do not have an ability to save data at all.

Ensign, on the other hand, persists all data by default — because it’s better to be safe than sorry! Read more about how the Ensign Broker (which is responsible for persisting data) works here !

What is change data capture (CDC)?

Databases are constantly changing, particularly transactional databases. However, databases must also support the underlying consistency models of the applications and organizations they support.

For example, when you look at your checking account balance, you expect to get a single amount, even though in reality that amount is continually going up and down (hopefully more up than down :-D). And let’s say at the same time you were checking your account balance, your account manager also checks your balance — you would expect to both see the same value, even if you were checking from your phone while on vacation in Tokyo and your account manager is checking from her desk in Nebraska.

But it’s tough for a database to be able to provide that level of consistency while also providing detailed insights about the up-and-down movement of your account balance. That’s where change data capture comes in!

Ensign’s event streams can provide bolt-on change data capture (CDC) by logging all changes to a database over time. In our bank example, an Ensign CDC log could be used for a lot of useful things — from training models to forecast negative balances and flag account holders before they incur fines, to real time alerting to protect customers from fraud.

Architecting and Interacting with Ensign

Questions for builders, analysts, and implementers.

What is EnSQL and how do I use it?

EnSQL is basically the same as SQL (because who wants to learn yet another query language??) — a lightweight structured query language that helps you query your topics just like you would any table in a relational database. With EnSQL, you can also retrieve changes to objects over time rather than being limited to querying current state or version of the data.

We’ve made EnSQL’s syntax as close to actual SQL as possible; this reference provides an in-depth tutorial on how to use it.

Can you share any data flow diagrams as a starting point?

Sure thing! Check out this link that contains a data flow diagram and a primer on how to design event-driven architectures for building streaming applications.

Does PyEnsign integrate with leading streaming platforms (e.g. Apache Kafka, AWS Kinesis etc.)?

Absolutely! Since Ensign is also a streaming engine, you can use the Pub/Sub framework to interact with Kafka and Kinesis. For example, you can create an Ensign subscriber that subscribes to a Kafka topic or ingests from a Kinesis stream and does some data transformations. On the flip side, you can have an Ensign publisher that publishes data to a Kafka topic or Kinesis stream.

Ensign is cloud agnostic and therefore it can be used in any environment with no additional infrastructure requirements. All you have to do is create an Ensign account and pip install pyensign and write your application code.

Why am I not seeing any events coming to my subscriber?

In order for an event to be seen by a subscriber, two things need to happen. First, the ensign server needs to have successfully received the event from the ensign client. The server communicates the successful receipt by sending an ack message. Second, the publisher needs to receive this ack message before publishing the event to the topic. If there is a failure in any of the steps, the event won’t be seen by the subscriber. For this reason, it is recommended that users write code to handle acks and nacks (successful and unsuccessful receipt of messages sent by the ensign server to the ensign client).

Also, ensure that the subscriber is stood up first to receive messages because it is possible for messages to have already been sent to a topic before the subscriber started listening to them.

Furthermore, make sure that a sleep interval is set on the publisher because it is possible that there can be delays in receiving data from either the ensign server or the data source (e.g. an API). If the sleep interval is not set, it is possible that the publisher terminates before an acknowledgement from the ensign server or before receiving data from the data source. In such cases, the event does not get added to the topic and so the subscriber will not see it.

How do you deploy models?

In a streaming application, you can deploy a model by publishing it to a model topic from which a subscriber can retrieve the model and use it for generating predictions.

For example, we can create a publisher that will periodically send requests to an API to receive data to train a classification model. Once we are satisfied with the model’s performance and choose to deploy, we can pickle the model and the performance metrics and then publish the event to a model topic. We can then create a subscriber on the other end that is listening for new messages on this topic as well as a score_data topic that sends new data that will be used to generate predictions. Once the subscriber receives the message, it will extract the model from the event. Now, it is ready to use this model to generate productions on data it receives from the score_data topic.

The added benefit of this architecture is that the model topic serves as a model registry that can be used to version control models and because we are storing metrics, it is easy to evaluate different model versions.

Check out this repository for an implementation of this design pattern.

I’m curious about using Ensign to version models using topics. How does this compare to using something like Artifactory or H20.ai?

If you already use Ensign, you eliminate the need for a different tool, and you don’t need to spend additional time learning and configuring another component in your environment. If your data is in Ensign, there will also be reduced latency because the model and the data are on the same cluster.

If you already use and love Artifactory, H20.ai, or another model registry, we love that for you; keeping using it!

What are Ensign’s limits?

Ensign is a streaming engine, and therefore, events cannot be larger than 5 megabytes. If you have data that is larger, you can compress it and/or break it down before publishing and provide a way for the subscriber on the other end to put it together for processing. If you are attempting to publish a model that is simply too large to be streamed, then one option is to store it on AWS S3 or another storage solution and include the link to the location in the event that is published to the model topic. A similar strategy can be employed for other types of data.

What are protocol buffers and why does Ensign use them?

Eventing is all about machines talking to each other, and that needs to happen as efficiently as possible. Binary serialization is an excellent way to enable message transmission to be as fast as possible.

Protocol buffers (aka gRPC) is a free and open-source cross-platform data format used to serialize structured data. Ensign uses protobuf to help the machines in our clusters quickly send and receive messages to and from each another, so that your publishers and subscribers can publish and consume your events as quickly as possible. You can read a bit more about how we use protobuf at the bottom of the SDK page .

What/Who is Ensign for?

Who is using Ensign and what are they using it for?

What are some good use cases for Ensign?

Ensign can be used for many different types of real-time applications. We put together this guide to help you come up with ideas for your next project.

What can I build - how do I get started?

Glad you asked! Check out some ideas here .

In what agencies or companies is this kind of work relevant? Where can I work if I want to do projects like this?

Ensign serves a broad set of use cases, some of which we have outlined in this guide .

As Faraz Rahman says :

All data is inherently streaming in nature. The only real difference is how we decide to conceptualize that data — as what it really is (a stream of changes) or as what it looks like right now (a snapshot).

Suffice to say, the data flowing through most workplaces is already happening in a stream — which means it’s pretty likely that being able to do preprocessing, analytics and modeling on streams of data is relevant to your industry or organization, whatever that industry or organization happens to be.