Microsoft Azure, SCRUM and MicroServices with .NET
In an increasingly crowded market how do you STAND OUT from the crowd?
What are the key technology skills in HIGH DEMAND today?
Do you want to elevate yourself above the competition and INCREASE your earning power? Then this is the course for you!
I’ll teach you the step by step how to understand and use:
Take your career to the next level and learn how the top developers can demand bigger salaries!
Freelance & contract developers with these skills can make upwards of $800 a day, and the demand is increasing each year. Completing this course will open your eyes to a new world of potential earnings.
With the development community growing each year, it’s becoming harder and harder to impress potential customers or employers – but what separates the high earners from the rest is knowing how to use the latest tools, technologies and methodologies.
In this course I teach you how to get setup and started for free with Microsoft Azure and start building environments with
Web & API Apps
I’ll then show you how to setup a SCRUM project, recording and managing user stories, tasks and sprints.
Finally we will use Azure’s offerings to start building applications around Microservices architectures, building, testing and deploying automatically into Microsoft Azure using DevOps pipelines.
By the end of the course you will be comfortable with building enterprise applications using the latest technologies with seamless and repeatable deployments.
For Freelancers & Consultants you will;
Get Happier Customers
More Easily Estimate & Manage Projects
Gain Faster More Accurate Feedback
Stand Out From Your Competitors
Demand Higher Fees
Demonstrate Credible Knowledge
Stand Out From The Crowd
Demand Higher Salaries
And of course, being part of Udemy you get:
FREE lifetime access to this course
ALL future lectures and upgrades (of which there will be many!) included for free
Udemy’s Unconditional 30 day money back guarantee – so there’s NO risk
So Elevate yourself today and get started RISK FREE!
What are the different tools we need?
If you are not careful, even with the Azure trial, costs can run away with you. I highly advise watching this to understand how best to keep an eye on costs and keep them to a minimum.
Find out where you can get access to the code used in the examples throughout this course.
This course assumes a certain amount of coding knowledge - you would be able to complete the course without too much experience, however this video will show you where you can get some additional help.
Why do you need this course? Why has software development changed?
What's wrong with Waterfall? Why do we need Agile?
SCRUM & DevOps
Consuming APIs and Sharing Code
In this first lecture of the section we setup a base Web UI that will consume our Customer API.
How do we share code? Create a Private NuGet service using Azure DevOps.
With our NuGet service in place, create a Models project that can be shared across the UI and API projects.
Setup a NuGet build, package and publishing pipeline with automatic versioning.
With everything in place, we can now use our Models NuGet library in the UI.
Setup the automated build and deployment pipeline of our UI project to an Azure WebApp
Refactor the API project to use the Models NuGet package, and amend the build pipeline to use the new NuGet service.
We don't always need to keep models consistent between services - this lecture explains why.
We won't need to use the customer API and UI after this lecture, so we'll clean up the Azure resources to keep costs down. Don't worry - you're code is till in DevOps!
Platform Services and Managing Branches
Introduction to PaaS and Branch Control.
Using branching policies to control who can commit code, and ensuring that code if of the highest quality.
Walkthrough of the Supplier API.
Creating a pull request.
Approving Pull Requests and managing comments and updates.
Create an Azure API App
Step by Step process of creating an Azure SQL Database, and how to interact with it from an administrative point of view.
How do you manage different settings such as connection strings for different environments? How do we create different settings for local, dev, test and prod environments?
With everything in place, we walkthrough building CI/CD pipeline, taking into account the additional options we can now use.
Now we've build the Supplier API using PaaS, can you re-work the Customer API pipeline to use PaaS instead of IaaS?