Azure Tutorials Series - Compute - Containers

-

We know about how containers work in Azure, we have gone through different practices one can opt for Virtual Machines(VMs), let us now look at containers and its architecture.

Containers

  • Unlike VM which uses OS, containers uses various applications hosted on one OS.
  • Lightweight than VMs
  • Respond to changes comparatively faster than VM
  • Multiple containers can run on same OS, and it could run multiple applications
  • Secured and isolated

Containers in Azure

Azure Container Instances(ACI)

  • PaaS- Fastest and Simplest way to run containers

Azure Kubernetes Service(AKS)

  • Orchestration - Managing large number of containers
  • To automate, manage and interact with containers.
  •  Existing application could be migrated to AKS by publishing it through Azure Container Registry(ACR).
Kubernetes
  • Widely used service to manage containers
  • Can run across different cloud platforms
  • Combines container management automation with API
  • Pod Management
    • A pod is one or more containers in a node
Micro Services
  • Breaking the functionality of an application into smaller modules.
  • Such that, it is independent of technology, stack or any tool
  • A dev team member can work as per his expertise
  • Results in faster release cadence
  • Each micro service is free of any dependency
  • Micro services communicate with each other using API calls
  • Highly scalable
  • Deployment
    • Can be deployed independently
    • No need to worry about entire codebase
  • Good for:
    • High release velocity
    • Highly scalable applications
    • Organisation with small development teams
Below services are used to host containerised web applications -
  • App service
  • Kubernetes service
  • Container instances
That is all for Containers! Please feel free to comment below. Happy Learning!

Comments

Post a Comment

Popular posts from this blog

Azure Tutorials Series - Azure Networking

-
Image
In this article, we will learn about Azure networking concepts such as architecture, microservices, virtual networks, VPNs, subnet, VPN gateways and most importantly Network Security Group(NSG). All these terms are to be understood if you appearing for AZ900 Microsoft Azure Fundamentals exam. Azure Networking In previous articles we have learnt about Micro- services and how they work, these are alos loosely coupled architecture. Some of the features includes Independent components interact with each other with the help of queues Can be updated and deployed independently Highly scalable Supports Asynchronous messaging N-tier Architecture Supports loosely coupled architecture Application divided into multiple tiers such that higher tier can access lower tier but not vice versa Tiers are re-usable and can be updated or replaced easily without any hassle. Three-tier in general Web Tier(front end) Application tier(back end) Data tier(Storage) Virtual Network Isolated network shared by few g
Read more

Coforge Interview Questions | Automation Testing profile

-
Image
In this article we will cover recent Coforge Interview questions asked for testing profile.  Date of Interview - 19th December 2020 Mode of Interview - Web conference through TEAMS Interviewer - Rahul Sharma Round - L1 Coforge Interview Questions | Automation testing profile Round L1 Tell me about your project I have been working as a QA for XYZ company from 5.4 years, during this tenure,  I have learnt about Manual testing, Selenium, Database testing, TestNg, framework designing and API testing. What is a webdriver? A webdriver is a an automation framework that allows executing our tests in different browsers. It also supports headless execution using HtmlUnit driver. What are hooks? @Before and @After are called Hooks, they are used before and after any test scenario. How would you like your automation framework to be designed? How can you use data properties in Test NG framework? Explain Access specifiers? Access modifiers define the visibility of the class. There are four different
Read more

Testing in CI/CD

-
If you are part of testing fraternity you would have heard CI/CD numerous times by now. It's the talk of the software testing town. In this article, we will cover the basics of CI/CD, what actually it is and how it is implemented in software testing. What is continuous integration? In simple terms, development teams can integrate their code into a shared repository. This helps in maintaining code quality and identifying potential issues with the local version of the code at an early stage. What is continuous delivery? Everything that is being continuously merged by the development team, is continuously deployed to the live environment. Continuous delivery is often coined as ‘Continuous Deployment’ as well. Since most developers work in parallel, continuously integrating their code into one repository would mean that the master branch is continuously updated with new features. In order to ensure that there is no compromise in the code quality with so many changes
Read more