iTranslated by AI

The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
🌲

Frontend Engineer's Experience with AWS Quick Start

に公開
AWS
S3
Amplify
frontend
App Runner
idea

Overview

Regarding the personal development project currently in the planning stages, I am reviewing the features based on a prototype implemented with Firebase as the infrastructure, and considering rebuilding the backend and infrastructure.

Since the selection involves areas that cannot be fully covered by one person alone, I will rely on actual projects and technical forums.

Amidst this, I had the opportunity to attend the AWS Builders Online Series (AWS Quick Start) on Thursday, July 14th, and since there was a session tailored for frontend engineers that resonated with me, I would like to share my own summary.

How to Learn AWS

Although AWS encompasses a vast array of services and content, the learning cost can vary significantly depending on the approach. I used to think of AWS primarily as an infrastructure platform, but I learned that, depending on the combination of services, you can build applications without deep knowledge or extensive experience in containers and infrastructure.

As a starting point, the session explained the following learning indicators:

  • Concept-based knowledge: Understanding what is possible, then putting that knowledge into practice.
  • Development skills: Hands-on first, with a clear objective.

Which one do you want to focus on?

I found this approach relatable, as it reminded me of using "terminology dictionaries" and "reverse lookup dictionaries" when I first started learning HTML in the IT industry. In the next section, I will share specific services according to different learning paths.

By Content: "Grasp the Overall Picture of AWS"

This content is for those who prefer to proceed with concept-based knowledge.

By Use Case: "Learn Development Skills"

This content is for those who prefer to proceed with a development skills-based approach.

The Options: AWS Amplify and AWS App Runner

Of course, if you could acquire all of the above, it would be ideal, but considering the learning cost, it's difficult to get started. Although I have some experience using them at work, for someone like me who is not well-versed in containers and infrastructure (like Docker), there were sessions on critical tools.

Personally, "AWS Amplify" seems similar to Firebase, which I previously selected, and if it can address features like search functionality that I couldn't implement, it is definitely a viable option. "AWS App Runner" gives me the impression that it packages the infrastructure that would normally be built by combining multiple services, offering significant benefits for me.

Selection Criteria Solidified Through the Seminar

My own approach is to select development environments and tools based on past experience and proven reliability, but I also recognize that there will be times when decluttering is necessary. The seminar provided valuable information to help me decide whether to adopt AWS. While there will certainly be trial and error, I would like to proceed by comprehensively considering factors such as:

  • Can the development period, including the learning cost, be shortened?
  • Can the service be sustained over the medium to long term after release?
  • The potential, risk, and cost of updating the build environment during the growth phase.

Discussion