ASP.NET, MVC, AZURE , Azure DevOps, ANGULAR, Typescript, WEB API, SSRS, WCF , C#, JQUERY TUTORIALS

7+ Year Exp in IT Industry, Working as Technical Lead at HytechPro| Consultant | Leadership, Corporate Trainer | Motivational, Technical Speaker | Career Coach | Author | MVP | Founder Of RVS group | Trained more than 4000+ IT professionals | Azure | DevOps | Agile | ASP.NET | C# | MVC | WEB API | ANGULAR | TYPESCRIPT | MEAN | SQL | SSRS | WEB SERVICE | WCF...
Sunday, 2 February 2020

What Is Microsoft Azure And Why Should We Use It For Enterprise?

Introduction

 
Microsoft Azure is a cloud computing platform that offers 600+ cloud services under a single umbrella. Microsoft Azure was formerly known as Window Azure in October 2008. Azure provides services for building, testing, deploying, and managing applications and services through multiple data centers.
 
Azure lets you add cloud abilities to your current system through its foundation as a help (PaaS) model, or endow Microsoft with the entirety of your processing and system needs with Infrastructure as a Service (IaaS). Either alternative gives secure, solid access to your cloud facilitated information—one based on Microsoft's demonstrated engineering. Azure gives a regularly growing cluster of items and administrations intended to address every one of your issues through one advantageous, simple to oversee stage. The following are only a portion of the abilities Microsoft offers through Azure and tips for deciding whether the Microsoft cloud is the correct decision for your association.
 
Today a lot of organizations still have genuine worries about moving applications to the cloud. Fears about system security, accessibility, and potential vacation whirl through the heads of bosses, some of the time incapacitating associations into sitting tight on existing tech—despite the fact that it's maturing continuously.
 
Enter Microsoft Azure, the industry chief's answer for setting off to an in-part or thoroughly cloud-based design. The following is an itemized look at what Azure is, the intensity of joining forces with Microsoft for a cloud or half and half cloud arrangement, and the most ideal approach to get full and noteworthy perceivability into your accumulated logs and foundation measurements so your association can respond rapidly to circumstances.
 

What can Microsoft Azure do? 

 
Microsoft updates and maintains Azure services day by day to make services more secure and flexible for end-users. Some of the most popular services are listed and explained below,
 

Storage Services

 
Azure Storage is Microsoft's distributed storage answer for the current data storage approach. Azure Storage offers a hugely versatile article store for information questions, a document framework administration for the cloud, an informing store for dependable informing, and a NoSQL store. Azure Storage is: durable and exceptionally accessible.
 

Compute Services 

 
Azure Virtual Machines (VM) is one of a few sorts of on-demand, adaptable registering assets that Azure offers. You pay for extra VMs when you need them and shut them down when you don't. Broadened datacenter – Virtual machines in an Azure virtual system can undoubtedly be associated with your organization's system. Azure provides some of compute options which are given below:
  1. Virtual machine (VM)
  2. App Service
  3. Service Fabric,
  4. Azure Kubernetes Service (AKS),
  5. Azure Container instance
  6. Azure Functions
  7. Azure Batch
  8. Cloud service 

Mobile Services

 
Azure Mobile Services give an adaptable cloud backend to building Windows Store, Windows Phone, Apple iOS, Android, and HTML/JavaScript applications. Store information in the cloud, validate clients and send pop-up messages to your application within minutes. We can get the advantages of Azure mobile services which are given below,
  1. Store any type of data on Azure Storage.
  2. We can use AD Authentication.
  3. We can use the Push notification service.
  4. We can use access on-premises resources. 

Database Services

 
Azure SQL Database is one of the options to store relational databases, Microsoft Azure provides as a managed service now. So we can create a high availability based and high performance based database layer for the applications and solutions in Azure. SQL Database can be the right choice for a variety of modern cloud applications because it enables you to process both relational data and non-relational structures, such as graphs, JSON, spatial, and XML. Microsoft Azure has other database options which are given below,
  1. Cosmos DB
  2.  PostgreSQL
  3.  MySQL
  4. SQL Data Warehouse
  5. Data Lake Store

Messaging and Event Services

 
Microsoft Azure offers four types of messaging and event services in Azure: Service Bus, Storage Queues, Event Hubs, and Event Grid. Of these, two are explicitly for events: Event Hubs and Event Grid, and the other two: Service Bus and Storage lines, are for Azure messaging.
 

Media Services

 
Azure Media Services lets you convey any media, on for all intents and purposes any gadget, to any place on the internet utilizing the cloud. The assortment of features gives encoding, live or on-demand sharing, content security and ordering for video and audio data. We can take advantage of Azure media services which are given below:
  1. On-Demand service
  2. Live- Broadcasting
  3. Digital Marketing
  4.  Audio and Video security 

DevOps

 
A type of development (Dev) and operations(Ops), DevOps is the association of individuals, procedures, and innovation to consistently offer some incentive to clients.
What does DevOps mean for groups? DevOps empowers some  siloed jobs—improvement, IT tasks, quality building, and security—to arrange and team up to create better, increasingly dependable items. By receiving a DevOps culture alongside DevOps practices and apparatuses, groups gain the capacity to be more likely to be able to react to client needs, increment trust in the applications they fabricate and accomplish business objectives quicker. In simple words we can say it's a combination of plan, develop, deliver and operate. We can advantage of Azure DevOps services which are given below,
  1. Speeding up time to market
  2. Easy to adapt to the current market.
  3. Maintaining system stability and reliability and scalability.
  4. Improving the time to delivery and recovery process.
  5. Tracking and reporting of manpower and productivity.

Why are organizations showing trust in Microsoft Azure?

 
They already know about on-premise datacenters which have no future. Why are some of the top companies like 3M, BMW moving their workload to Microsoft Azure? Because of these reasons: 
  1. Security
  2. Flexibility
  3. Scalability
  4. Application Cost
  5. Disaster recovery
  6. Logging capability 
  7. Autoscaling
  8. Global datacenters
  9. High Availability
  10. High performance
  11. 24*7 Technical Support

Conclusion

 This article explained facts about the Azure Cloud, and why we should use it with enterprise applications.
Bikesh Srivastava Azure, Azure DevOps

What Is Azure DevOps And Why Should We Use It?

Introduction

 
Azure DevOps (in the past known as VSTS) is all that you need to assemble your product from start to finish. Azure DevOps is a single platform that helps every software developer team on this planet design ventures utilizing the Agile process, oversee code utilizing Git, test the application, and deploy code using using the CI/CD framework. We can understand in a simple way (Dev+Ops= DevOps), which means a combination of development and operation processes for software development.
 

 
I hope the above image is the best graphical example to understand the complete process about Azure DevOps services.
 

Online vs On-premises

 
Azure DevOps  can be accessible in two different ways: on-premises ("Server") and online ("Services"). The last structure is called Azure DevOps Services (in the past Visual Studio Online before it was renamed to Visual Studio Team Services in 2015). The cloud service belongs to the Microsoft Azure cloud platform. It utilizes a similar code as the on-premises rendition of Azure DevOps, minor adjustments, and executes the latest highlights. Azure DevOps requires no extra configuration. A user just needs to sign up from their Microsoft account to set up a domain, create a project, adding a new user.
 
So let me clarify one confusion here, today in this article I am just going to explain about Azure DevOps Service, not the Azure DevOps server.
 

History of Azure DevOps

 
As per Wikipedia details, Microsoft launched the first version of the Team Foundation Server on March 17, 2006. So Microsoft provides all types of support for TFS, Azure DevOps Service, and Azure DevOps server. See the below image which is taken from Wikipedia.
 

Source: Wikipedia 
 

Azure DevOps Keywords

  • Organization
    Azure DevOps organization is basically by default an account name/ Domain name but we can change it as well. Ordinarily, you will have one Azure DevOps account and deal with various domains inside, which means we can create multiple organizations with a single Microsoft account. We can configure access control and security for an individual organization as well.
  • Projects
    We can split Azure DevOps organization into multiple projects and can configure access control, pipeline, build process, board and code for an individual project.
  • Azure BoardAzure board is basically used for planning, tracking for Work Items, Backlog, and Sprints. Azure Board is also called an ALM (application life cycle management) tool just like other ALM tools JIRA, SpiraTeam, etc. Inside the Azure board, we can create workflows, issue types, epic, and many other components of ALM.
  • Azure Repos
    Azure Repos is a place where we can create, manage and store versions of our codebase. We can use it for code review and other version control functionality. Azure Repos basically provides us two types of version control systems now GIT (Distributed version control) and TFVC (centralized version control).
  • Azure Pipeline
    Azure pipeline is one of the automation processes of DevOps which allows us to create a build, release, test, and deploy on the target machine. We can say in simple words Azure pipeline is the combination CI/CD.
  • Azure ArtifactsAzure Artifacts is one of the extensions of Azure DevOps which helps us to create, host, manage and share packages across the team. Azure Artifacts supports multiple types of packages e.g NPM, Nuget, Maven, Python, etc.. Azure Artifacts are basically a collection/ output of dll, rpm, jar and many other types of files. One of those extension based files may contain metadata.
  • Azure Test plansAzure test plans support advance test management solutions for customer feedback, UAT, Automation testing, and manual testing.

What can Azure DevOps do?

  • PlanningAs discussed above, the Azure board is an ALM tool. So the Azure board helps us to maintain an Agile process which means Azure DevOps helps us to plan, track development history for individual developers and detects issues using a kanban and scrum. 
  • DevelopTo manage our workspace and code repository multiple types of version control are already integrated with Azure DevOps. Almost all features related DevOps already inbuilt inside.
  • Integration/Build
    We can use continuous integration and continuous deployment (CI/CD) with the help of the Azure pipeline. There are multiple types of job agents, and templates are already available inside. 
  • Package
    As we know we have already an inbuilt extension available, Azure Artifacts, so we don't need to go anywhere for any type of packages.
  • TestingAs we know Testing is an important part of the DevOps process. So Azure DevOps provides multiple types of inbuilt testing templates and management tools.
  • ReleaseAs we know the software release process is a very critical moment of DevOps. So Azure DevOps has already multiple types of inbuilt features to make the process easy and risk-free.
  • Configure/OperateAs per my experience, it's very easy to configure and operate, because Azure DevOps has a simple process to configure organization, kanban, sprints, etc..
  • MonitorEach phase of the DevOps life cycle should be monitor because it helps to ensure the health, performance, and reliability of your application.
  • Reporting
    Azure DevOps has a dashboard where we can see reports, a summary and can generate an analytical report with BI integration. 
  • Wiki
    Azure DevOps Wiki helps us to distribute information, share knowledge and collaborate across team and stakeholder. A Wiki can be used to explain about the project's user stories, sprints, release notes, etc..

Conclusion

 
Azure DevOps platform is generally utilized in the Software Development process. Along these lines, this platform helps the association which is as of now utilizing Azure and making the SLA simple. In this article, we have talked about the Introduction to Azure DevOps. In our upcoming articles, we will talk about progressively every topic with details and instructional exercises of Azure DevOps. 
Bikesh Srivastava Azure, Azure DevOps
Sunday, 3 November 2019

How To Create Angular App With .NET Core In Visual Studio


In this article, I am going to share knowledge "How to create an angular app inside .net core". Most of the developers are thinking about angular if it can be merged with visual studio .net core so that's fantastic. So don't worry guys I am here and going to explain about this0. If you are not aware of Angular and .net core separately please go through the below-given link these links are very helpful to create an angular app with .net core step by step.
I am going to explain in some of the steps to create an Angular app using .net core using visual studio:
Before start, you should make sure you have already installed Visual Studio 2017.

Step1:
Open Visual Studio and create a project after clicking on File> New> Project, See the below image for more help. 



Choose template ASP.NET Core Web Application and click on OK after that one other popup will be displayed there, so now time to select the SPA category. We can choose any template e.g React, Angular, WebAPI, any template according to your requirement, Now we should select Angular because we are going to create SPA with .netCore with Angular. see image for more help



Select Angular and click on OK, Now SPA template is generating by Visual Studio for Angular with .netCore. it will take 1 minute approximate to create a complete application structure with all configuration on your system. see image for more help. 



Now open solution explorer and we can see SPA application structure is ready. Application structure completely follow the latest version of the framework .net Core. Open the given link if not aware of .net Core click here https://docs.microsoft.com/en-us/visualstudio/ide/quickstart-aspnet-core?view=vs-2019.
So let me explain about  ASP.NET Core - Project Structure one by one:

AngularSPAwithCore: Solution Name and project Name (in this project both names are the same but you can choose different).
Connected Services: We can use to connect any cloud services e.g Azure.
Dependency: It contains all the installed serverside NuGet packages as well as clientside frameworks such as jQuery, Angular etc. Client-side dependencies are managed using NPM in Visual Studio. 
Properties: Properties set the configuration launchSettings.json file which includes Visual Studio profiles of debug settings. 
wwwroot: Basically, This is root folder of the application and treated as webroot () folder, Inside wwwroot should be separate folders for the different types of static files such as JS, CSS, Image, bootstrap etc. 
ClientApp: Complete Angular application with all configuration. see below image to understand in easy way.



Above image, Now we see inside ClientApp Angular configuration available e.g. Component, Package.json, Index.html. etc. If you are already not aware about angular application structure so click on this link Clickhere.

Controller: In this folder, we can create our business logic e.g API
Pages:  Application related .cshtml pages e.g error.cshtml.
.gitignore: This file is part of the git code versioning tool to configure the setting of git logic as well as to ignore folder and file from the application.
appsetings.json:   As we know don't have anything called Web.config in Asp.net Core application which we use to write our connection strings or application-specific settings. Here we have a file called appsettings.json to store such type of information.
Program.cs: As we know Asp.net Core application starts from the program.cs file and execute always void main() function. 
Startup.cs: As we know about Asp.net Core Application there is no Global.asax file so instead of that use Startup.cs which is executed the first time when the application starts.

Now we can change the configuration in any file according to our project requirement. So let's move to our application which is already configured by default.
Application is ready to run but before that, we should make sure all client-side and server-side packages available inside the dependency node_module folder. If the yellow icon indicator displaying on the dependency folder it means we need to rebuild the application to restore the packages.

Let's press f5 or run the application after compile and build application will open in browser with default https://localhost:44391/See the below image.




In this application already default SPA application template is created. Now we can change layout, component, service etc. 
I hope this article is helpful to learn about ASP.NET Core SPA Application with Angular. 

      Happy Coding!! Keep learning!!

Bikesh Srivastava Angular, Interview Question
Saturday, 7 September 2019

Microsoft Azure DevOps Syllabus for deep learning

Getting started with Azure DevOps.
  1. Overview of Azure DevOps
  2. What DevOps Service and DevOps Server.
  3. Create Azure DevOps Account
  4. Roles And Responsibilities in Azure DevOps
  5. Create Project and User mapping to Azure DevOps
  6. Azure DevOps access to Different roles
  7. Project management using Azure DevOps
  8. Test case Management through Azure DevOps
  9. Methodologies In Azure DevOps (SCRUM,AGILE,CMMI)
  10. Deployment Group Creation
  11. Configure the Azure DevOps  service in the virtual machines
  12. Agent management in the Azure DevOps.
  13. Capacity Planning using Azure DevOps.
  14. Kanban Board Management
  15. Scrum Management


Azure DevOps Keywords
  1. Organization
  2. Projects
  3. Azure Board
  4. Dashboard
  5. Wiki
  6. Repos
  7. Pipelines
  8. Test Plans
  9. Artifacts


Repository Management/Branch Management
  1. Create the New repository
  2. Create the Master branch
  3. Create the Own Branches based on the developer requirement
  4. Branch merging
  5. Import Repository from Outside of the vsts to vsts
  6. Creating Pull requests And Accepting Pull Requests


CI/CD Process Using Vsts and Azure
  1. Task Creation Based on the Application Repository
  2. Create the CI Process
  3. Build Setup
  4. Environments Setup
  5. Authenticate Build to Azure Web service
  6. Failover Mechanism
  7. Load balancing
  8. Cluster Creation for Load Balancing
  9. Continues Integration Setup
  10. Test Cases Build
  11. Build alerts Configuration
  12. IAAS Deployments
  13. PAAS Deployments
  14. Micro Services Deployment using Azure
  15. Alerts Configuration Using Azure
  16. Arm Build and Release templates Creation
  17. Build And deployments through powershell
  18. Big bucket Jenkins internal configuration using Vsts for ci cd
  19. Build And Deployments Authentication and authorization


Working with Azure App service
  1. Overview of App Service
  2. Deployment in App Service
  3. Deploy and maintaining web apps
  4. Configuring web apps
  5. Monitoring web apps and WebJobs
  6. Traffic Manager


Working with Azure SQL Database
  1. Overview of SQL Database on Azure
  2. How to Deploy Azure SQL Database
  3. Implementing and managing Azure SQL Database
  4. Managing Azure SQL Database security
  5. Monitoring SQL Database in Azure
  6. Managing Azure SQL DB recovery
  7. Import and Export Data


Working with Active Directory
  1. Overview of Active Directory
  2. Why need AD for Azure
  3. Active Directory Configuration in Azure
  4. Domain Controller in Azure
  5. AD Federated Services in Azure
  6. Custom domain
  7. Monitoring Azure Active Directory


Microsoft Azure Syllabus for deep learning

Introduction to cloud computing and Microsoft Azure
Types of cloud computing
  1. What is What is Cloud Computing
  2. SaaS: Software as a service
  3. PaaS: Platform as a service
  4. IaaS: Infrastructure as a service
  5. Advantages and Disadvantages of Cloud Computing
Azure services
  1. Compute services
  2. Data services
  3. Application services
  4. Network services
Azure key concepts
  1. Datacenters and regions
  2. Azure portal
  3. Resources
  4. Resource groups
  5. Resource Manager templates
Automation
  1. Azure PowerShell
  2. Azure command-line interface
  3. REST APIs
Getting started with Azure subscriptions & pricing Calculation
  1. Select and enable an Azure subscription
  2. Grant administrative access to an Azure subscription
  3. View billing information in the Azure portal
  4. Get billing information from billing APIs
  5. Forecast cost with the pricing calculator
  6. Set up billing alerts
Azure Resource Manager
  1. Tips for creating resource groups
  2. Building Resource Manager templates
  3. Security of Azure resources (RBAC)
Azure App Services - Web Apps
  1. Introduction
  2. App Types
  3. Deploying Web App directly from Visual Studio.
  4. Scaling a Web Apps
  5. Application Settings Configuration

Azure SQL Database 
  1. Introduction/Overview.
  2. Creating and Using SQL Server and SQL Database.
  3. Azure SQL Database Tools.
  4. Using Azure SQL Database with EF Code First.
  5. Migrating on premise database to SQL Azure.
  6. Elastic Storage.
  7. Manage Business Continuity
  8. Azure SQL Database vs SQL Server in IaaA VM

Azure Virtual Machines
  1. Use cases
  2. Deployment of virtual machines
  3. Portal
  4. PowerShell
  5. Command-line interface
  6. Access and security for virtual machines
Azure Storage
  1. Use cases
  2. Blob storage
  3. File storage
  4. Table storage
  5. Queue storage
  6. Deploying a storage account
  7. Portal
  8. PowerShell
  9. Command-line interface
  10. Access and security for Azure Storage
  11. Virtual machine disks
  12. Storage tools
  13. Storage API
  14. Storage access keys
  15. Shared access signatures
  16. C# / MS.NET Azure Storage SDK
Azure Virtual Network
  1. Use cases
  2. Cloud-only virtual networks
  3. Cross-premises virtual networks
  4. Deploying a virtual network
  5. Portal
  6. PowerShell
  7. Command-line interface
  8. Access and security for virtual networks
Azure Web Jobs
  1. Logic App
  2. Web Jobs
  3. Microsoft Flow
  4. Functions
Azure Service Bus 
  1. Service Bus Basics
  2. Relayed Messaging
  3. Service Bus Queues
  4. Topics and Subscriptions

Azure Active Directory 
  1. Azure AD Introduction
  2. Relationship between AD DS and Azure AD
  3. Managing Active Directories
  4. Adding a custom domain name to Azure AD
  5. Managing Users, Groups and Devices
  6. Adding Co-Administrators for a Subscription
  7. Configuring Role Based Access Control
  8. Integrating On-Premise AD Identities with Azure AD
  9. Integrating Gallery Applications with Azure AD
  10. Integrating On-Premise Applications with Azure AD
  11. Implementing Azure AD B2B Collaboration


Bikesh Srivastava Azure, DevOps, Syllabus, Training & Seminar
Wednesday, 5 June 2019

Agile Vs. DevOps: What’s the difference?

What is DevOps?

DevOps is a software development method which focuses on communication, integration, and collaboration among IT professionals to enables rapid deployment of products.
DevOps is a culture that promotes collaboration between Development and Operations Team. This allows deploying code to production faster and in an automated way. It helps to increases an organization's speed to deliver application and services. It can be defined as an alignment of development and IT operation.

What is Agile?

Agile Methodology involves continuous iteration of development and testing in the SDLC process. This software development method emphasizes on iterative, incremental, and evolutionary development.
Agile development process breaks the product into smaller pieces and integrates them for final testing. It can be implemented in many ways, including scrum, kanban, scrum, XP, etc.

Agile Vs. DevOps

Stakeholders and communication chain in a typical IT process.
Agile addresses gaps in Customer and Developer communications
DevOps addresses gaps in Developer and IT Operations communications

Difference Between Agile and DevOps

Parameter
Agile
DevOps
What is it?
Agile refers to an iterative approach which focuses on collaboration, customer feedback, and small, rapid releases.
DevOps is considered a practice of bringing development and operations teams together.
Purpose
Agile helps to manage complex projects.
DevOps central concept is to manage end-to-end engineering processes.
Task
Agile process focusses on constant changes.
DevOps focuses on constant testing and delivery.
Implementation
Agile method can be implemented within a range of tactical frameworks like a sprint, safe and scrum.
The primary goal of DevOps is to focus on collaboration, so it doesn't have any commonly accepted framework.
Team skill set
Agile development emphasizes training all team members to have a wide variety of similar and equal skills.
DevOps divides and spreads the skill set between the development and operation teams.
Team size
Small Team is at the core of Agile. As smaller is the team, the fewer people on it, the faster they can move.
Relatively larger team size as it involves all the stack holders.
Duration
Agile development is managed in units of "sprints." This time is much less than a month for each sprint.
DevOps strives for deadlines and benchmarks with major releases. The ideal goal is to deliver code to production DAILY or every few hours.
Feedback
Feedback is given by the customer.
Feedback comes from the internal team.
Target Areas
Software Development
End-to-end business solution and fast delivery.
Shift-Left Principles
Leverage shift-left
Leverage both shifts left and right.
Emphasis
Agile emphasizes on software development methodology for developing software. When the software is developed and released, the agile team will not care what happens to it.
DevOps is all about taking software which is ready for release and deploying it in a reliable and secure manner.
Cross-functional
Any team member should be able to do what's required for the progress of the project. Also, when each team member can perform every job, it increases understanding and bonding between them.
In DevOps, development teams and operational teams are separate. So, communication is quite complex.
Communication
Scrum is most common methods of implementing Agile software development. Daily scrum meeting is carried out.
DevOps communications involve specs and design documents. It's essential for the operational team to fully understand the software release and its hardware/network implications for adequately running the deployment process.
Documentation
Agile method is to give priority to the working system over complete documentation. It is ideal when you're flexible and responsive. However, it can hurt when you're trying to turn things over to another team for deployment.
In the DevOps, process documentation is foremost because it will send the software to the operational team for deployment. Automation minimizes the impact of insufficient documentation. However, in the development of complex software, it's difficult to transfer all the knowledge required.
Automation
Agile doesn't emphasize on automation. Though it helps.
Automation is the primary goal of DevOps. It works on the principle to maximize efficiency when deploying software.
Goal
It addresses the gap between customer need and development & testing teams.
It addresses the gap between development + testing and Ops.
Focus
It focuses on functional and non-function readiness.
It focuses more on operational and business readiness.
Importance
Developing software is inherent to Agile.
Developing, testing and implementation all are equally important.
Speed vs. Risk
Teams using Agile support rapid change, and a robust application structure.
In the DevOps method, the teams must make sure that the changes which are made to the architecture never develop a risk to the entire project.
Quality
Agile produces better applications suites with the desired requirements. It can easily adapt according to the changes made on time, during the project life.
DevOps, along with automation and early bug removal, contributes to creating better quality. Developers need to follow Coding and Architectural best practices to maintain quality standards.
Tools used
JIRA, Bugzilla, Kanboard are some popular Agile tools.
Puppet, Chef, TeamCity OpenStack, AWS are popular DevOps tools.
Challenges
The agile method needs teams to be more productive which is difficult to match every time.
DevOps process needs to development, testing and production environments to streamline work.
Advantage
Agile offers shorter development cycle and improved defect detection.
DevOps supports Agile's release cycle.

Conclusion:
  • DevOps is a software development method which focuses on communication, integration, and collaboration among IT professionals.
  • Agile software development method emphasis on iterative, incremental, and evolutionary development.
  • Agile refers to an iterative approach which focuses on collaboration, customer feedback, and small, rapid releases.
  • DevOps consider as a practice of bringing development and operations teams together.
  • Agile method is to give priority to the working system over complete documentation. It is ideal when you're flexible and responsive.
  • In the DevOps, process documentation is foremost because it will send the software to the operational team for deployment.
Bikesh Srivastava DevOps

Life Is Complicated, But Now programmer Can Keep It Simple.