mirror of https://github.com/01-edu/public.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
nprimo
bcb1275241
|
10 months ago | |
---|---|---|
.. | ||
README.md | 10 months ago |
README.md
General
Check the Repo content.
Files that must be inside the repository:
- Detailed documentation in the
README.md
file. - Source code for the microservices and scripts required for deployment.
- Configuration files for the chosen cloud provider Infrastructure as Code (IaC), containerization, and orchestration tools.
Are all the required files present?
Play the role of a stakeholder.
Organize a simulated scenario where the students take on the role of Cloud engineers and explain their solution to a team or stakeholder. Evaluate their grasp of the concepts and technologies used in the project, their communication efficacy, and their critical thinking about their solution. Suggested role play questions include:
- What is the cloud and its associated benefits?
- Why is deploying the solution in the cloud preferred over on-premises?
- How would you differentiate between public, private, and hybrid cloud?
- What drove your decision to select the specific cloud provider for this project, and what factors did you consider?
- Can you describe your microservices application's cloud-based architecture and the interaction between its components?
- How did you manage and optimize the cost of your cloud solution?
- What measures did you implement to ensure application security on the cloud, and what security best practices did you adhere to?
- What monitoring and logging tools did you utilize, and how did they assist in identifying and troubleshooting application issues?
- Can you describe the auto-scaling policies you implemented and how they help your application accommodate varying workloads?
- How did you optimize Docker images for each microservice, and how did it influence build times and image sizes?
- If you had to redo this project, what modifications would you make to your approach or the technologies you used?
- How can your solution be expanded or altered to cater to future requirements like adding new microservices or migrating to a different cloud provider?
- What challenges did you face during the project and how did you address them?
- How did you ensure your documentation's clarity and completeness, and what measures did you take to make it easily understandable and maintainable?
Were the students able to answer all the questions correctly?
Did the students demonstrate a thorough understanding of the concepts and technologies used in the project?
Were the students able to communicate effectively and justify their decisions?
Could the students critically evaluate their solution and consider alternative strategies?
Review the Architecture Design.
Review the student's architecture design, ensuring that it meets the project requirements:
Scalability
: Does the architecture utilize services to manage varying workloads and scale as required?Availability
: Is the architecture designed to be fault-tolerant and maintain high availability, even during component failures?Security
: Does the architecture integrate security best practices, such as data encryption, use of VPC, and secure API endpoints with managed authentication?Cost-effectiveness
: Is the architecture designed to be cost-effective on the chosen cloud provider without compromising performance, security, or scalability?Simplicity
: Is the architecture straightforward and free of unnecessary complexity while still fulfilling project requirements?