- [Voiceover] So in this step, you need to understand…that's it's important to map where you are…and where you need to go.…The as is and the to be state are…traditional architecture concepts…that are helpful here as well.…And so if you look at…traditional architecture text for example,…people building systems as much as 20 years ago,…there's discussion of as is and to be.…And you'll find that the same concepts,…without adhering to a particular type of technology,…are exactly the same.…And it's okay, I think,…especially if you're an architect who…comes from traditional systems,…to kind of remap your understanding…of as is and to be in the sense…in how they map into cloud architecture.…
So, step three is mapping the as is to the to be.…And so we've done that by understanding…the requirements in step one,…and defining our desired instate in step two.…So in this step, we take current state,…including data, compute, storage, application.…You know, say it could be an Oracle system…running with an HP server,…which may be leveraging EMC based storage…
- Cloud architecture basics
- What problems need to be solved?
- The "as is" and "to be" states
- Cloud storage, CPUs, and databases
- Building your first architecture
Skill Level Beginner
1. Cloud Architecture Introduction
2. Understand the Business Needs
3. It's All about the Cloud Parts
4. From Requirements to Solution
5. Build Your First Architecture
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.