Expanding Applications to the Cloud

First session is about expanding to the cloud.
Second session making enterprise grade cloud applications.
Third session cloud or no cloud the laws of physic still apply.

First session:



Going over decision process from when to host bs using the cloud.

Buy vs build.
On premis vs cloud.

Matrix of 6 different types



Packaged application
Hosted package
Software as a service
Home built application
Hosted home built.
Cloud platform

Monitoring and management is a challenge for using the cloud.



It's important to learn the Ali for this so you can develop your own tools.

Application management is also a challenge

Application integration is also a challenge. Azure solution is the service bus.











Slide above shows options for using the cloud. You start with hosted and them over time you rearxhitext the solution to use more of the cloud services.




Use workers and queues to increase scale and availability. Gave an example of a voting system. When millions are voting the application can't update the count fast enough. You queue the votes and then let a worker work through the queue at it's own pace and not hold up the user.

Showed an example of a voting application.








Slide above asks the question of what impact the cloud will have. The interesting anawer from microsoft is they don't know.





You should handle spikes in traffic in the design of your application as an exception.

The cloud will change the way people will handle capacity planning. Software will work like utilities industry.

Workers and queues can scale automatically.




We will need to think about 3 of these directly when redesigning our application.




We will need to consider a base approach for some parts of our database.

"not all data is equal"

Move inactive data to other stores. After a user is done shopping move the data somewhere else and treat it as reference data (inactive data).

Example for us is our archived or closed tasks.