Mike, I can say that these tips help a lot, not only for an interview, but also to enhance our current knowledge. Sometimes we understand the Technology, but we don't know how to explain it in a simple way. You Just did it here, thanks.
Thanks Alex. To really build a great tech career being able to explain the technology is just as important as understanding the technology. Thank you for your kind words.
Again thanks Mike, for making SQS and Decoupling concept simple to understand. I also understand the correct way to answer anyone who ask what is EC2...
Very helpful to be reminded of how to explain and communicate AWS offerings through its underlining technology. Helps clients who aren't familiar with the technology feel more comfortable about how it solves their needs.
Hi Timothy, Thank you. Not sure what you mean. We described adding caching which is volatile memory. But I’m happy to hear more about your suggestions We always like to hear other perspectives
Thank you. Generally speaking most of our questions are more vendor neutral cloud architect questions and less vendor specific like AWS or Azure. Since we focus more on architecture, it’s about how to do the end to end system design. And then just finding the per vendor services to meet the clients goals. But sometime we discuss vendor specific platforms. So I will take this suggestion and run it past my video planning and editing team.
Of course. When we train our architects we train architecture. A virtual machine is just a virtual machine whether it’s a vm on a VMware server, an AWS EC2 instance or something on google compute engine. That’s the difference between learning architecture, how the tech works, why to use the teach and certification training that teaches the names of services and how to configure them.
