Interested in a private company training? Request it here.
An architecture will look very different depending on what you're focusing. Do you want it to be fast or reliable or cheap? You can't have it all, but you can optimize for more than one thing. These considerations will be drive decisions in all following topics.
By splitting up a monolith into bite-size microservices, you make your application a lot more suitable for the cloud. Although this is not a must, most systems will consist out of various running applications that will need to communicate.
Scaling an application has many benefits: Your application becomes more reliable, faster and handle more throughput. There are many options on how to scale an application in the cloud. In this module, we'll take a look at key benefits and drawbacks of each one.
Choosing the wrong technology or a bad scaling strategy for data can turn out really expensive. In this module, we'll learn how to avoid that.
Scaling is great and all. But can become quite complex and costly. In this module you will learn about various techniques to boost performance without requiring scaling.
This module focusses on direct communication between applications. This means using things like REST or gRPC. We'll take a look at some patterns to improve resiliency and reduce complexity.
Asynchronous communication is much more reliable than synchronous communication. In this module, you'll learn which common problems it solves, some useful patterns and clarify some of the confusing terminology often used with this type of communication.
Understanding the different offerings for message brokers is key to create good integration. You need to know how to handle heavy loads, large messages while keeping things affordable and secure.
Most likely, not all of your data will end up into a single normalized database. Chances that your data will be scattered all over the place are much higher. So, how do you keep things consistent? And what if something fails? Don't worry, my friend, this module will explain all.
CRUD is the norm but has its limitations. This includes performance and consistency. By separating read and update operations, CQRS can overcome these limitations.
There are many concerns when communicating to the external world. Most of them have to do with security, but also the fact that protocols are usually restricted to HTTP can be a problem.
Every developer knows about authentication and authorization. But there are other security concerns when deploying to the cloud.
The cloud is a great environment to build applications that are resilient, have high availability, are performant and hopefully not too expensive. But how do you achieve those goals? In this training we start from potential problems a cloud developer/architect may face. Then, we figure out what to do by using proven patterns. And finally, we look at various technologies available in Azure to implement these patterns. The focus of this training is the concepts and patterns, which apply to any cloud environment. The focus is not on technical details of each Azure resource.
This course targets people who want to become cloud developers or cloud architects in Microsoft Azure. The goal is to write cloud-native applications. This means the focus is on PaaS (Platform-as-a-Service) while also covering relevant infrastructure. Participants of this course need to have a solid developer background and must know the basics of Azure, or similar cloud.