What are we running and how do we know it?

Modern software systems can be complicated with many moving parts.  Each of those parts can be updated, upgraded, or changed at any time.  We need the ability to understand which versions of each component or configuration are running in each environment at any time.  

Smart designs, automation, and the appropriate metadata can set us up to understand the specific configurations and versions in each layer in every environment.

We will attack this problem in the static / design phases and the dynamic run time phases. What versions do we have available? What versions are we running?

Video

This blog page exists to provide readers with images and tables used in this video. Text content is subject to extensive editing.

We have a bunch of stuff

Modern applications can be topologically complicated. There are multiple layers and multiple components in each layer. We want to have a repeatable process for creating and instantiating components of every type and a way of determining which configurations and versions exist in a given SDLC environment.

Version what?

Software system complexity starts at the infrastructure level and moves up the stack.  Automation makes it possible to track changes in all tiers as they are updated.  Good design makes it possible to interrogate all resources to determine the version that is currently deployed.
  1. System and infrastructure resource deployments are complex.  Each component has its own configuration requirements.  Each deployment can be thought of as another version of that infrastructure.  One of the amazing things in the cloud is the possible levels of automation via APIs and templates.  We can now version our Infrastructure as Code. We can track our changes over time. We can interrogate running infrastructure to tie back to our configuration versions.
  2. Software deployments have mature version tracking practices.  We can specify which version of a deployment we want.  We can put code in every deployable that can be interrogated for its version.
  3. Software deployments expose APIs.  Those APIs often have their own versioning behavior.  We can register API versions at deployment time and expose version information at run time.
  4. Messaging is another type of API, a payload schema-driven API.  We can implement payload/schema versioning in the configuration as code.  We can register the deployed schema in schema registries.  We can query those registries at run time to determine the deployed supported schemas.
  5. Databases are a little different than code and other components in that they have to protect persisted data.  This means we don't deploy via drop and replace like we do for code, messaging schemas. Automation makes it possible to model data stores and version them across time.  Automation makes it possible to apply database schema changes to databases within certain limitations.  That same automation can be used to register versions in schema catalogs. That same automation can deploy the schema version into the datastore where it can be queried at runtime.

Design Time vs Run Time

Versions are managed as part of design time.  Components, schemas, and data models can all be registered at design time in API registries, schema registries, and other tools.  The same information can be registered every time a component is updated.  This builds a catalog linking between a component and its version everywhere it exists.  Version metadata can be embedded in applications, contracts, and data models in a way that can be interrogated at runtime.  This lets us build a real-time dashboard as running. Runtime version metadata helps us find places where automation failed or humans messed something up.

Versioning Options

This table describes where design-time and run-time versioning information can be registered and retrieved.
Component Type Versioned Artifact Creation Time Live Object
Network Configuration Provision Logs Tags
Compute VMs/Containers Configuration Provision Logs Tags
Compute Serverless Configuration Provision Logs Tags
Data Stores Configuration Provision Logs Tags
Streams and Messaging Configuration Provision Logs Tags
Build Artifacts Code Version Build Tags Repository Tags
Deployments Build Artifacts Build Artifacts Tags, API
APIs API versions Catalog Registration API Endpoint
Data Models Model Versions Catalog Registration DB Entity
Payloads Schema Versions Catalog Registration Schema Registry
Models Model Versions Model Registration Model Registry?


Created 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  Update Driver  does  not  install the RNDI
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 defaults to a maximum RAM size of 5
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 access id and secret key.
Read more