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 Public  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 running on multiple servers to run on a single set of servers
  • Replace MySql with manages MySql
  • Migrate Kumbernetes hosted applications to Azure K8s Service
  • Recommend small code changes/improvements to be done by the following application team






Optimization requires very little coding changes and no change to the applications.


Modernization: Application components will be recoded to be more efficient in the cloud. Eg replacing apis and app with cloud provided services.

Examples:

  • Rplace APIs or sub-systems with Azure Services
  • Recode applications components to be more efficient in Azure
  • Replace databases with alternate technologies: e.g : replace oracle with Postgress SQL
  • Replace an app with SaaS or PaaS services
  • Convert apps to a micro-services architecture
  • Convert apps to Docker container-based deployments

 

Rewriting: Completely reconstructing the app to fit cloud living. New application development will be done if there is no corresponding SaaS services are available.


Self-Migrate & New App Infor:

App team is driving & funding their Azure deployment

Example:

  • New app build directly on native Azure vs on-prem
  • Existing app moving to azure from 3rd party cloud
  • Existing application with code development for enhancing the application features
  • Existing application migrating sooner than Factory schedule can accomodate
  • App team opts out of Factory funding & process, no charge for Microsoft CSA consulting
  • Conducting Proof of Concept to vet new technologies and PaaS services

Shared Responsibility Model: Organization to CloudOps

Pubic Cloud Architecture:

Principles
Patterns
Blocklisted Services
Technology Mapping
Encrypting All Data





Comments

Post a Comment

Popular posts from this blog

Pickle Vs M, VS ONNX vs SavedModel vs TorchScript

-
  Pickle Vs M, VS  ONNX vs SavedModel vs TorchScript Let’s break it down in terms of purpose, use cases, compatibility, and safety : 🥒 Pickle (.pkl) Pickle is a Python-specific serialization format for objects, including machine learning models. Feature Details Use Case Serializing Python objects (including scikit-learn, XGBoost models) Compatibility Python-only (tight coupling with specific versions) Frameworks scikit-learn, XGBoost, LightGBM, etc. Speed Fast to load/save Portability ❌ Low — not portable across languages or platforms Security ⚠️ Unsafe to unpickle untrusted data (can execute arbitrary code) Deployment Typically for offline inference or Python-based pipelines ✅ Best For : Local development, internal tools, reproducible experiments ❌ Not Ideal For : Cross-platform deployment, mobile/edge/cloud scaling 🧠 TensorFlow SavedModel (MD) SavedModel is TensorFlow’s official format for storing trained models for production use. ...
Read more

Experiment Tracking and Versioning during Model Training

-
 Experiment Tracking and Versioning during Model Training Experiment Tracking   Following is just a short list of things you might want to consider tracking for each experiment during its training process:  • The loss curve corresponding to the train split and each of the eval splits.  • The model performance metrics that you care about on all nontest splits, such as accuracy, F1, perplexity. • The log of corresponding sample, prediction, and ground truth label. This comes in handy for ad hoc analytics and sanity check • The speed of your model, evaluated by the number of steps per second or, if your data is text, the number of tokens processed per second.  • System performance metrics such as memory usage and CPU/GPU utilization. They’re important to identify bottlenecks and avoid wasting system resources.  • The values over time of any parameter and hyperparameter whose changes can affect your model’s performance, such as the learning rate if you use...
Read more

Module 3: Fine-Tuning and Customizing Generative AI Models

-
  Module 3: Fine-Tuning and Customizing Generative AI Models Overview: In this module, we will explore how to fine-tune and customize pre-trained generative AI models to meet specific needs and tasks. Fine-tuning allows developers to adapt powerful, pre-existing models (such as GPT-3, BERT, or GANs) to domain-specific applications and data, which is often more efficient than training a model from scratch. You'll learn how to fine-tune various types of generative models for use cases like code generation, text generation, image synthesis, and more. By the end of this module, you will have the skills to tailor pre-trained models to your specific software development needs. Lesson 3.1: Understanding the Fine-Tuning Process 3.1.1: What is Fine-Tuning? Fine-tuning is the process of taking a pre-trained model and adapting it to a specific task or dataset. Pre-trained models are typically trained on large, diverse datasets (e.g., GPT-3 trained on vast text data). Fine-tuning helps ...
Read more