Joe Freeman

Conway's law says systems, software, and wetware, end up shaped like the organizational structure that designed them or that they are designed for.   Organizations understand this at some level. Much of the corporate re-organization efforts are fed by people trying to change the corporate structure to push closer together the people creating a new paradigm or system.  The other main approach is to live with the partitioning that aligns with the organizational structure allowing any global redundancy or other inefficiencies. Video Images used in Video Conway's law states that software systems will be designed and built with the same alignment and partitioning as the organization that built created the software.  Teams that are closer together organizationally will build software that works better together. Teams that are farther apart will build software more loosely coupled or more error-prone.   We see the same behavior for non-software ecosystems.  Chevy aligns their division

Kafka provides all kinds of metrics that can be used for operational support and tuning work.  We can use Telegraf/Jolokia to capture metrics from the various Confluent broker nodes and put those metrics into an Influx DB. We can then create Grafana dashboards for those metrics using Grafana Example Topology Deployed Components We run a custom Kafka Broker Docker Image built on top of the confluent/cp-server image. That image just adds the Jolokia JVM Agent jar file.   Run a docker-compose.yml to start Kafka that enables Jolokia as a Java Agent The agent URL for demontration purposes The Telegraf standalone agent conf enables the Jolokia2 input adapter.  The configuration file can be built into a new image or the configuration file can be mounted inside the standard DockerHub Telegraph image. Telegraf runs with this new configuration file. Telegraf retrieves the data from the Jolokia REST endpoints and sends it to InfluxDB Grafana provides visualization.  It uses InfluxDB as a data s

One of Azure's big initial innovations was their PaaS platforms.  These services were a level up  from most of Amazon's offerings. Microsoft appears to be in the process of killing of their traditional offerings. They are instead exposing the containerized underpinnings and forcing customers to do their own packaging and Docker image construction.  This makes sense for large enterprises but means that teams need to understand the underlying O/S software modules and system components that may need to be installed in their containers. PaaS PaaS makes it easier for less sophisticated teams to deploy sophisticated scalable applications. Azure PaaS lets customers deploy applications without worrying about the Operating System, System Patching, CVE security scanning , load balancing, log aggregation, or other issues.  The opacity of the underlying system meant teams had to know less and that teams couldn't know more if they wanted too. Microsoft modernized much of their PaaS plat

The public cloud has its' own issues around access, security and the patterns they use. You don't realize how minor they are until you move back to a data center or leased private cloud.  Sample Cloud Provider services vs Storage and Compute in data center Moving from a Public Cloud to a Data Center is like... Flying commuter prop plane for a long trip Most of your luggage got left on the tarmac because it weighed too much. Everything takes longer and involves a lot more noise. Moving back into your parents place You are forced to squeeze into the clothes you wore in high school and have to sleep in the skinny bed. You have a curfew.  Having a laptop with no battery You have no flexibility in how or where you work with all the constraints of a laptop screen. Moving from a 65" 4K to 25" 720k It has no remote so you have to get up and change the channel at the set.  Being banished to sleep in the shed out back It sort of feels like home. There is no air conditioning and

Sometimes you have a situation where you want to push multiple tags when you push a Docker Image to Docker Hub using the Docker Hub build automation.   We will override the default behavior to do this. Video links related to this blog are available down below. Default behavior The default behavior is to build and push every time  there is a change on master.  That auto-built  image is always tagged with :latest and pushed to the repository as :latest Standard default build on master pushed with tag latest Docker Hub supports overriding its build and deploy behavior with a set of hooks. Custom build files and build hooks are stored in  /hooks  of the code repository.  Hooks are described  https://docs.docker.com/docker-hub/builds/advanced/  .   You can see an example here  https://github.com/freemansoft/cp-server-jolokia Pushing Multiple Tags to Docker Hub This is the approach we will take The following variables are available. SOURCE_BRANCH : the name of the branch or the tag that is

Companies create Enterprise IT initiatives to support moving into new businesses, when adjusting to new regulation and audit rules, or when they want to merge systems across acquired companies or divisions. These multi-year efforts can involve hundreds of people, dozens or hundreds of cooperating systems, and millions of lines of code or configuration.  The public perception of these projects and how they actually operate can be very different.  Major software projects or IT initiatives often have more complexity than anticipated.  They can be under-sized to get funding. The project's goals almost aways change between the enthusiasm phase and the implementation  phase.  Scope changes during the project as more is learned or the market or requirements change. Planning often includes optimistic assumptions about the target state complexity or how fast the project can move. Senior management does not often have true visibility into the current state, the current goals, or the complexi

IT Enterprise Architecture acts as a forward-looking, unifying agent across teams and disciplines. The architects generally own the company's future direction and target state.  EA operates is one of the few groups that sees all facets of a company's software development, IT Operations, governance, security, best practices, 3rd party integrations, and more. This cross-cutting responsibility can often put EA in a position where they are pushing future states or constraints that make software development and business process automation even more complicated.  Enterprise Architecture can end up being viewed as pushing solutions driven by NFRs that deliver and business may only be tangentially aware of.  They often deliver designs and mandate approaches that are based on technology and platforms that do not yet exist in the enterprise. This can cause delivery and business to view architecture as an impediment to progress.  EA are the ones that always say no.   Architecture can help

Companies have all kinds of policies and behavior that determine whether they would be a good fit, a poor fit, or a stepping stone type of fit. Most job hunters know to ask the big 4:   What are the benefits? How much will I get paid? What is the work-life balance? How will I grow? There other subtle policies that determine your longevity and success in a potential new position.  Video Use public resources to investigate the company Use the public and social resources that are available to you.  Check web sites like  https://www.glassdoor.com/index.htm Use  https://www.linkedin.com/ . Look for 1st or 2nd level contacts and see if they will answer questions or talk. I answer questions for people whenever they ask.  See if there any local social media or other discussion boards.  My spouse is always telling me about the c