Azure Event Hubs - Namespaces Hubs Schema Registry RBAC

Microsoft has added a Schema Registry to their Azure Event Hubs.  This is another feature parity checkbox for those thinking of moving from Kafka to Event Hubs. The Schema Registry at this point feels like it was created by a different team with a slightly different organizational structure and RBAC than that of the Hubs themselves. 

Schema Registries are useful in a lot of circumstances. Microsoft would have been better served by Making the Schema Registry a stand-alone offering with its own Portal blade.  

The video below walks through how the Schema Registry is fitted into Event Hubs.



Video

 

Speaker Notes

Namespaces

Namespaces are the Azure EventHubs primary top-level organizational unit.
  • Hub RBAC can be applied at the Namespace level.
  • Schema Registry RBAC can be applied at the Namespace level

Hubs

Hubs are the individual event streams. They are topics in Kafa terms
  • Access tokens are supported at the Hub level
  • RBAC can be applied at the Hub level.
  • RBAC applied at the Namespace level is inherited by all of the contained Hubs

Schemas

Schemas are data contracts that describe AVRO or other message types. They are often logically bound to an Event Hub documenting that Hub's data contracts. Schemas support schema evolution. They can be configured at the time of creation to support backwards or forwards compatible changes.

Schema topology differs from Hubs in that they reside in Schema Groups instead of directly in the Namespace. Schemas are similar to Kafka Schemas.
  • RBAC can be applied at the Namespace level.
  • RBAC applied at the Namespace level is inherited by all the contained Schemas

Schema Registry

A Schema Registry is an organizational construct inside the Namespace to manage Hub schemas.  Schemas are contained in Schema Groups that are contained in Schema Registries. Event Hub Schema Registries are similar but not identical to the Kafka Schema Registry. 
  • RBAC can be applied at the Namespace level.
  • RBAC applied at the Namespace level is inherited by all the contained Schemas.
  • RBAC cannot be applied directly to a Schema Registry.

Schema Groups

A Schema Group is an organizational construct inside the Schema Registry that sits inside a Namespace.  A Schema Group can contain any number of Schemas.  

The provisioned tier determines the number of Schema Groups that are allowed.  The standard tier is limited to one Schema Group.  The number of schema versions is also limited by tier. There can be only one Schema Group in a given Event Hubs Namespace. This feels like a work in progress at the end of 2021.
  • RBAC can be applied at the Namespace level.
  • RBAC applied at the Namespace level is inherited by all the contained Schemas. The permissions transit from the Namespace through the Schema Registry, through the Schema Group, to be seen at the Schema level.
  • RBAC cannot be applied directly to a Schema Group.
References
  • https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas

Source Code

GitHub repository to create the Azure environment in video
  •  https://github.com/freemansoft/eventhubs-sanbox-azure

Created 2021 12
Updated 2022 01

Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more