In this video, explore a scenario that will be used throughout this chapter. Widget makers need an AWS solution and you're going to help them implement it with some solid design recommendations.
- Before we get into the details of the four pillars of the well architected framework that we have left to discover, I want to take you through a scenario. I have the opportunity to meet an executive with Widget Makers and we're going to talk a little bit about the systems they have in place and what systems they might want to move into the cloud. This is where you'll start as an architect, get a good understanding of what you need to accomplish based on what's already there, or in some cases, it's just a vision for a solution in AWS, so in many cases, people are moving to the cloud, and in other cases they're just implementing something new in the cloud, in this case, with our discussion with Widget Makers, we're talking about moving their existing on-premises systems into the cloud, so let's see what we can learn from the executive. I appreciate you taking the time to meet with me today, I know that as an executive your time's valuable and there's a lot going on here at Widget Makers right now. - You bet. - What I wanted to do is just meet with you to get a brief overview of what you're doing. I understand that right now everything is on-premises, that you have your own data center, and you're looking at saving costs in operational management, and having a cloud-first mentality and starting to move into the cloud more. - Perfect. - So, I guess to help me out, I need kind of some summary information about your systems and, the key thing is, keep in mind, I can the excruciating details from your tift. - Good. (laughs) - I'd like to get your perspective on your five most important systems that you want to look at moving into the cloud. So where would you start? - I'm sure order processing is probably the number one. We've got our inventory management system, our payroll, all of our user data stuff, and our website, those are probably the five most important. - Alright, well with the order processing, do you have some details you can give me relating to that? - [Executive] Sure, it's web-based for the client, it's a SQL server based backend, and we have 50 to 75 users ballpark, it's a SQL server database, I think that's about it. - [Interviewer] Okay, excellent, and how long have you been using that system? - [Executive] Probably close to 10 years. - Okay, because that tells me a lot about how much data you're going to have inside of there, so it's always good to know. Now the other one you mentioned was inventory process, tell me a little more about that. - [Executive] It's web-based at this point, we use My SQL, we keep the inventory, we do our reconciliation at the month-end and year-end, it does interact with the order processing so that we have an ongoing system and then we true that up at the end of each month. - Okay, so basically your inventory system, you're getting some information out of that in the order processing database so basically when you - Yep, exactly. - process orders, you know if you've got inventory in stock or not. - Yep, yep, draws it down. - Okay, that makes sense. Excellent. Now then you mentioned that you've got payroll. - Sure, sure, we have a time clock function that we gather the information, I think we handle it all on our SQL server as well, the managers are allowed to access and rewrite on that, and obviously the accounting interacts with the accounting side so... - Okay, so the accounting side, that's probably for payroll processing right? - Sure, absolutely. - And then, I guess this would be also your employee database basically. - Yeah, yeah we keep the basic HR stuff. - Okay, well you mentioned user data too, so are we talking about some kind of storage for that or something? What are we looking at there? - [Executive] We've got the Windows server share that we map on our desktops, we've got about 700 megabytes per user, ballpark maybe 250 active users growing hopefully quickly. (laughs) - [Interviewer] Oh yeah? - [Executive] Maybe 160 gigabytes of total usage. - Okay, that's definitely good to know, it's going to help us think about costs is AWS and so forth. Alright, and the last system that you mentioned was your website, which obviously makes sense to move into the cloud, so what're we looking at there? - [Executive] We've go maybe 3500 daily visits during the week, maybe 600 per day on the weekends, it's a WordPress system, we have some custom plugins. - [Interviewer] Okay. Okay, so the custom plugins, that's not going to be a problem, AWS can handle anything WordPress can do so we'll be golden there. Well it sounds like this is a great place to start, and I can get more technical information that I need from some of your other tech folks. (laughs) - (laughs) Yeah! - So, that's going to free us up and I really appreciate you taking the time to meet with me today. - Absolutely! - You've given us great information to start with. - Absolutely, very good! - So I've been working on taking the notes that I got from the executive about their current systems and make sure I have everything organized so we have a good diagram to move forward in the project. So I build all of this using just a web-based tool that you can use called draw.io, let's take a look at what I have so far. So I have the order processing system and made sure I documented that it's a SQL database, web-based interface with less than 100 users, he told us there were 50 to 75 users there. We have our inventory management system which is also a SQL server database, just a few users with a web-based interface. We also have our payroll system with our time clock connection, now that's very important to me because I need to talk to the tech person and find out what protocols that might use to make sure we can get that into AWS. I know that managers have read/write access and accounting has read. We have the user data store which is for about 230 users right now but they plan to grow, and around 700 megabytes of data in Windows shares, and then we have a web server using WordPress with custom plugins. So we've got our diagram as it is, now what we'll do is, as we go through looking at how to move this information into AWS, we'll look at what it might start to look like as an AWS diagram. So what would things look like as we build them out with a well architected framework within the AWS architecture? We have everything that we need so that we can actually begin moving forward with the well architected framework and get into the four pillars so that we can take what they have and look at how we can build it in the cloud, so that it's resilient and reliable, it has good performance, it has the proper security, and we've optimized our costs. (upbeat music)
This course was recorded and produced by Total Seminars. We're pleased to host this training in our library.
- AWS media content delivery services
- Working with ElastiCache
- AWS analytics engines
- DevOps services in AWS
- Architecting resilient design solutions
- AWS best practices for secure design
- Designing for cost optimization in AWS