The course is part of this learning path
Okay Cloud Academy Ninjas, welcome back. Hopefully, those two scenarios have given you a little bit of food for thought about how you might go about tackling situations like that in real world events. Now, just a couple of things to remember is that often it's about thinking on your feet. So some of the prioritization techniques that we used in the first scenario can be quite helpful just to get you started, and to help you step your way through requirements to help people prioritize, so that you end up with a set of deliverables that you know you can achieve.
Some of the price calculation and design ideas that we discussed, hopefully will have opened your eyes a little to some of the other services that are available on the three platforms, AWS, as your own Google Cloud platforms, all have a rich feature set, and you may find it quite valuable to be able to explain to customers and to your team members just what the differences between those platforms are, and to make an objective decision about which one might best deliver on your requirements.
Okay, so as a next step here are start points to all three of the platforms. If you're familiar with one, or really, maybe explore looking at one of the others. You can never know too much about cloud services.
Now in the second scenario, it really does come down to just stepping through some of those core phases that you have to do for projects of that nature. Cloud adoption framework is a good place to start because it just gives you a framework to work in, and helps you step through some of those areas that you know you need to cover off. The design aspect, as well, is always crucial to ensure that you've identified the priorities for your customer, all right, and if you get that decision right, every other decision becomes easy. That way you can decide what stays in and what can be left out. And that becomes a very crucial part of coming up with time boxing that's gonna deliver on the business requirements. Having those kind of prioritization techniques can really help you.
Now in design, as well, I'm hoping that there's some interesting design ideas that you've learned from. Just one thing to keep in mind is that there is really no right answer to any design question. It's often a question of you coming up with the best possible mix of services to deliver in the best possible way. So how we went about some of the designs might not be exactly the way you would go about them. It doesn't mean that they're right or wrong, okay? So you become better at deciding which services will work best to deliver on a particular requirement. And I think that's a key skill of being a good solution architect. So just keep that in mind. There's also always many views on any of the ways and best ways of doing it. There's also new services that are constantly coming out from all of the vendors, and a lot of those services could perhaps answer the questions better than the ones that we've come up with on the white board. Anyway, it's up to you to keep up to date. That's why we love doing these courses and ensuring that you keep across all these fantastic services as they come out.
Okay, please let us know your feedback on this learning path. We really enjoyed putting it together for you. If there's other ways we could do it better, let us know please. And good luck in your endeavors. Well done, Cloud Academy Ninjas. Okay, so please let us know at email@example.com what you thought of this learning path. If you think we could do it better, please let us know. We really enjoyed putting it together for you and wish you all the best in your own work endeavors. No one is born a cloud expert. It's all learnt, so just keep on learning and you will be fine. Okay, well done, Cloud Academy Ninjas!
About the Author
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.