Posts

Showing posts from August, 2022

Cloud Migration Overview

Image
 Application migration objective Conduct application discovery and assessment  Create an approved Azure target architecture Complete the Deployment Design Document (DDD) Deploy the application in Organization's Azure environment  Run tests to prove production readiness Capture Application Key Stakeholders name form Migration and Application team side: Application Team stakeholders Migration Team stake holders Follow Public Cloud Core Six Principles: Secure the Network Monitor the Environment Protect the Data Deploy Infrastructure as Code Control the Access Make the allocation match the demand Secure the Network Private network connectivity to the cloud – Private (VPC) and Public (PaaS) Peering Private network connectivity to/from VPCs and PaaS services Support for "Bastion” VPC with private satellite workload VPCs using transitive routing from source No Internet ingress/egress other than from a designated VPCs Micro-segmentation of resources using Network Security Groups Monit

Technology Stack to Azure Service Mapping

Image
  Technology Stack to Azure Service Mapping:         On Premise Datastore to Azure IaaS & PaaS Mapping:   -On-premise to Azure IaaS and PaaS Data Store Mapping Recommendations -Existing “Core, Contain, and Sunset” applications are to be ported to Azure IaaS with using its current datastore to minimize cost and accelerate migrations -App on-prem apps are encouraged to migrate to directly to PaaS when it makes good business sense to do so -Selected strategic applications are to be Modernized to Azure PaaS, the remaining applications will be Optimized to run on Azure IaaS. -All new application and microservices are to be developed on Azure PaaS datastores with Cloud Native enablement. -All new applications and microservices are to select the most optimal datastore model (i.e relational, document, key-value, etc.) based on the application data profile, characteristics, shape, and/or size ( see Azure data store selection guide – https://docs.microsoft.com/en-

Benefits of moving to the cloud

 Benefits of moving to the cloud : Faster deployment, Lower costs, Self-Service, Operational Simplicity, Innovations are the key pointers for cloud. Self-service capabilities: Shorten our time to market Cost effective and efficient Operational Simplicity Innovation at scale Types of Publi c  Cloud Services: IaaS, PaaS, SaaS. Public Cloud First Policies: 1) Public Cloud First for Non-Network Workloads 2) Security Controls 3) Network Integration 4) Deployment Governance 5) Cost Management, Optimization and Visibility Optimization Public Cloud Migration Strategy: Assessing >4K apps for migration Estimating 80% of the workloads assed will migrate  Represents >250K servers today Targeting 75% reduction in allocated compute memory resources. Migration approaches: Optimization : Optimize the app during Lift & Shift approach. Everything else not involving source code changes Examples: Re-host applications from IaaS to PaaS Right size compute and storage Consolidate multiple services

Cloud Security principles and DevOps Task to follow

 Cloud Security Principals to follow: 1) Secure the Network 2) Protect the Data 3) Control the access: use generation for AUTH, provide least privilege's access 4) Monitor the Environment 5) Deploy architecture as a Code: mutable infrastructure deployment 6) Ensure allocation matches the demand There are the 5 Key Cloud DevOps Skills your team need to Successfully Perform 40 App Support Tasks in to Public Cloud: 1) Account and Subscription Security: Management of access to application workloads for groups and individuals. Active Directory Group creation and management Subscription-level access through Azure IAM  2) Availability and Performance Monitoring: Creation and response to alerts and advisor notifications Azure Monitor and insights for availability and performance monitoring. Azure Advisor for proactive recommendations on reliability, security, performance and cost. 3) Capacity Planning: Analysis of resources usage against current and future application needs. 4) Infrastruc

Enterprise Automation strategies of tomorrow

 What should be Enterprise Automation strategies of tomorrow CIOs and IT leaders have spent months adapting to change and scaling new solutions at speed; thus, spending considerable effort and energy; often to the point of burn out. Much of this is due to the changing natures of infrastructure and the application landscape; as IT leaders scramble to go cloud first in enabling new forms of working and reimagining operating models. In a cloud-first and increasingly automated world, CIOs and IT leaders must pay close attention to how their infrastructure is utilized and managed; as well as how apps are delivered – securely and to their optimum utility. It is therefore no surprise that the collective realization is that -  strategic infrastructure standardization ,  modernization  and  automation  efforts will be critical for successful digital transformation. The key questions many CIOs and IT leaders continue to have are as follows: 1.       How to craft automation as an ongoing discipli