Afrikaans
Akan
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranî)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
1
Now, before concluding this section, I just want to touch on another topic that is quite important,
2
especially for software architects, and this is about the architects and the cloud.
3
Now, traditionally, software architects that were designing regular systems needed to know the non-functional
4
requirements of the system, the technology stack, the components architecture and the communication
5
patterns.
6
This is all true for traditional systems.
7
Now, if you're not sure about any or some of these terms, then feel free to take a look at my course,
8
the complete guide to becoming a software architect.
9
It explains everything here in this list and of course, much more.
10
But this is a situation with traditional software architects, but cloud based systems required, in
11
addition, also infrastructure knowledge.
12
So the architect will often need to design the networking, the firewall, the application gateways,
13
the VPN, the low balances, etc..
14
The architect also has to know a lot about the security and what I mean who is, of course, the unique
15
aspect of security that are relevant to the cloud and to the infrastructure, because, of course,
16
a great architect must be fluent in securing application as integral part of its role.
17
And many times the architect has to have a great hands on knowledge and experience with the cloud because
18
no one else in the organization is as expert and knowledgeable about the cloud as the architect.
19
So these are the three skills are unique to cloud based systems and usually traditional architects are
20
not dealing with it when designing on premises system.
21
So keep in mind that you will need to know all of this.
22
And of course, don't worry, we will learn all of that in this course.
23
So by the end of this course, you, of course, will know how to design the infrastructure.
24
What are the security measures you need to take?
25
And of course, you will have a lot of hands on experience.
26
And with that, let's move on to the next section.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.