Cloud Architecture Process | Enterprise Architecture Process (How To Design A Cloud Architecture)

Looking forward to it

Mike , what you are doing and making us knowledgeable , we can only thank you, but this is not enough

Thank you Mike for sharing so generously and expertly, your knowledge freely. Those who join his program for Cloud Architects will come to realize that Mike knows the deep end of tech, and has done it as well but helps the budding Cloud Architect to focus on the right things to be successful in Digital Transformation.

This is a amazing and enlightening! Thank you for your wisdom and expertise!!

Explained in simple and easy terms, how a true Architecture would. Thanks for this insight Mike!

Dear Mike, thank your for sharing this valuable information in simple steps.
From the video, I could understand that the cloud architecture task is done after the signing off the contract with the client and handling the resulted architecture to the implementation team. Its seems that architecture it is fixed and the architect job is done for the product/project and the architect will not be part of the implementation team
From my experience, I observed that architecture is a "living" creature and it is adapted/adjusted by the team during the implementation depending on the new discovered information/needs/etc of the product or client feedback. In this case, if the architect in not part of the team, how he/she could gather valuable feedback from the implementation team about real architecture evolution? Is my understating correct regarding these aspects?

Hi Mike, I want to enrolled for the cloud architect Career bundle class, i schedule a meeting but I haven’t heard back from anyone . And pls is there any discount going on pls🙏?

Thanks Mike! You are a genious! I love your content.

Thanks Mike for the wonderful contents you share. About TOGAF, is the framework and certification a useful direction for someone looking to be a solutions architect ?

Thanks Mike for making this easy for me to understand

beautiful, i wish to be mentored

This is a great overview, but I think it's a mistake that an architect "hands off" an architecture to a highly diverse and complex implementation team. Often times, we learn things during implementation that ripples back up through the architectural plan. How do we deal with these ripples? What is the capacity for the architectural plan to change given that we now have new information. Designing an architecture for technology and business is NOT like designing an architecture for a building. To just assume that we can hand out a blueprint after having considered EVERYTHING is a fallacy and, in some ways, can be considered a mistake of hubris. The best architects constantly stay in touch with the implementation team and modify their plan based on new information. Is there guidance to handle these very real problems?