The Letter Setters in Bop! (I Like to Read)

Description

For the past eight years, I have been researching a concept known as “
” throughout my research, I have concentrated on the idea that one day, delivery cycles for information technology products will become very similar to those that Henry Ford had envisioned for the Ford Motor Company.
The creation of functioning software requires the completion of a number of steps that, when combined, result in an operational system. We have all, up until this point, presumed that this procedure is highly individualised and customised to one’s own needs; nevertheless, this is not the case. The proper standards that would enable us to think about functional systems outside of our preferred base programming language have been absent from our organisations up to this point.
Starting the journey
Preparing a base of understanding
– DevOps
– Build of materials and recipes
– Cross-platform, cross-technology
– Moving from one cloud provider to another
– Segmented service architectures vs microservice architectures
– Everything as code
– Risk of change
– Keeping application records
– Technology fa?ade
– Vendor lock opens and closes your innovative growth
– Open source
– Business value
– Automation
– Inner-Source
– Pipeline
– Artificial Intelligence in Automation
– Configurations
– Hyper compute
Technology＊s choices
– YAML rather than JSON
– Azure rather than AWS
– Use of Python
– Use of Ansible
– Preference for the Bicep over the ARM
– Utilization of Azure DevOps
– Utilization of Power BI
– Preference of Command Line Tools (CLI)
– .NET preference over Java
– Utilization of backstage
Understanding the concepts
– Reference Architecture
– Landing zone, or drop zone
– Blueprint
– Code templates
– Scaffolding vs. code templates
– Branching 每 Release Flow
Practices I care about
Drafting the future
– Coding Dojo and Code Kata
– Azure DevOps for Dojo
– Communication
– Build and Release Roles
– Creating reference architectures
– Cloud Governance
– Compliance
Taxonomy – Metadata schema
– Metadata
– Tenant classification
– Subscription classification
– Subscription type
– Environments, stages, and instances
– Regions and locations
– Segmentation in Azure
– Control, Data and Management plane
– Common capabilities definition
Enterprise requirements
– Measurable metrics
– Architectural enterprise requirements
– Cloud enterprise requirements
– Operational Excellence
– – Automation
– – Release engineering
– Monitoring
– Cloud Adoption Framework for Azure
– – Motivations
– – Expected business outcomes
– – Business Outcome Template
– – 5R assessment
– – Target workload Strategy
Strategy execution
– Cloud Governance repository
– – Release Flow
– – Semantic versioning
– – Azure Container Registry (ACR)
– – Package software with Azure DevOps
– Cloud Governance
– Secret Management
– API Management
– Data Orchestrator
– Identity Management
– Automation Factory
– – Ansible Collection
– – Ansible roles
– – Ansible modules
– – Ansible folder structure
– – Ansible Telemetry
– – Cloud resource operation
– – Cloud resource action
– – Testing Ansible with Molecule
– – Python
– – Specialized docker image for development
– – Container Image Management
– – Naming conventions
– Processes
– – Crisis management process
– – Change Management Process
– – Incident Management Process
– – Configuration Management Process
– – Security Management Process
– – Compliance Management Process
– – Disaster Recovery Process