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

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 defaults to a maximum RAM size of 5
Read more

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  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more