AWS APAC Community Summit 2022 -From the Serverless Perspective-
Tags: aws, awscommunityapac, awscommunity, serverless
Published: 2022-10-09 03:58:26

## TL;DR

This is a blog report for my attendance to **AWS APAC Community Summit 2022** hosted by AWS between Sep. 14th and 16th in Bangkok, Thailand.

## $ whoami

Hello! Thank you for visiting my blog! I'm Kosuke from Japan, who is a Product Owner of IoT platform in a water and housing product manufacturer.
My SNS list is here -> [Linktree](https://linktr.ee/coosuke) and please feel free to follow me!

## What is AWS APAC Community Summit?

AWS APAC Community Summit is hosted by [Amazon Web Services](https://aws.amazon.com/), and for AWS influencers from APACJ region such as
* [AWS Heroes](https://aws.amazon.com/developer/community/heroes/)
* [AWS Community Builders](https://aws.amazon.com/developer/community/community-builders)
* Leaders from [AWS User Groups](https://aws.amazon.com/developer/community/usergroups/?community-user-groups-cards.sort-by=item.additionalFields.ugName&community-user-groups-cards.sort-order=asc&awsf.location=location%23apac&awsf.category=*all)
* AWS Alliances

I hear AWS hosted the APAC regional community leader summit several times before COVID-19 but the summit was the first in-person and APAC regional summit after  COVID.

I was invited the summit as one of the Community Builders so I went to Bangkok and attend it.

## Serverless & Containers Feedback Session

The summit was sooooo impressive as I posted in LinkedIn,
{% embed https://www.linkedin.com/posts/kosuke-enomoto_aws-awscommunityapac-awscommunity-activity-6976571330624188416-sToG %}

and it is too hard for me to pick up one or two sessions...
However **I am a Serverless Community Builder**, so I decided  to focus on the sessions regarding Serverless.

In Day 1, I joined a breakout session that was called **Serverless & Containers Feedback Session** and 3 lightening talks and panel discussion delivered.

### Build better with Step Functions with SDK integrations by Jones

The first talk was delivered by [Jones Zachariah Noel](https://twitter.com/zachjonesnoel) from India who is a Serverless Community Builder. His talk focused on [Step Functions with SDK Integrations](https://docs.aws.amazon.com/step-functions/latest/dg/supported-services-awssdk.html).

**Why SDK Integrations?**
![Why SDK Integrations?](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/us57xgm64quspm70am2x.png)

**How to implement the integrations**
![How to implement the integrations](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e1hu5k2783qrl9u703xb.png)

From his talk I learned that Step Functions with SDK integrations makes us more productive and efficient.

### How our team embraced EventBridge for our event-driven serverless architecture by Raphael

The second talk was delivered by [Raphael Jambalos](https://www.linkedin.com/in/raphael-justin-jambalos/) who is also a Serverless Community Builder from Philippines. His talk focused on [EventBridge](https://aws.amazon.com/eventbridge/?nc1=h_ls) and how he converted from a monolith application on EC2 to microservices with EventBridge.

**Customer Painpoint**
![Customer Painpoint](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zjqsyar6eqek3qbh9fsa.png)

**Scenario**
![Scenario](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ev19zr4t4xjoft8fat9y.png)

He brought throughout the talk that
- How he worked on decoupling to microservices and building event-driven(serverless) architecture
- What issues occurred and how he resolved them
   - Payload too big
   - Destination unreachable
   - Steps must be done sequentially

### Serverless Web Hosting Strategy For Modern Front-end Application by Takahiro

The third talk was delivered by [Takahiro Horike](https://twitter.com/horike37) who is a Serverless Hero from Japan.
{% embed https://twitter.com/coosuke/status/1570281011610791936 %}

**Single Page Application has changed front-end landscape**
![Single Page Application has changed front-end landscape](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ktk91ajqmfk82gmcrnb2.png)

**Evolution never stops!**
![Evolution never stops!](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/sl8mts4acp2cockfjkzi.png)

First he mentioned that Single Page Application, Server-Side Rendering and Static Site Generation has been the game-changer on front-end strategy. And he also mentioned the key consideration to follow [Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/?nc1=h_ls) as follows;
- **Grasping the front-end design pattern(SPA, SSR, SSG etc)**
- **CI/CD workflow and optimization that fit the design pattern**
- **Leveraging managed service for efficient infrastructure**

To satisfy the consideration he explained some options
- Load balancing and virtual machines (EC2 or Fargate)
- Serverless (S3 bucket, API Gateway + Lambda or CloudFront)
- **built-in CI/CD workflow solutions ([Amplify Hosting](https://docs.amplify.aws/cli/hosting/hosting/) or [App Runner](https://docs.aws.amazon.com/apprunner/latest/dg/what-is-apprunner.html))**
- **Full-stack develop environment ([Amplify Studio](https://docs.amplify.aws/console/))**

And he concluded that with leveraging AWS serverless platform like them we could maximize our work efficiently.

### Panel Discussion
Then 3 presenters joined the panel discussion hosted by [@FarrahC32](https://twitter.com/FarrahC32) and [@donnieprakoso](https://twitter.com/donnieprakoso) from AWS. 
The interesting fact is... {% embed https://twitter.com/coosuke/status/1570286314590969857 %}

Anyway, the panel discussion was so impressive!

## Serverless - past, present and future - by Kameda-san
In the same day, [@kameoncloud](https://twitter.com/kameoncloud) who is a Senior Evangelist in AWS Japan delivered another Serverless session.
![beginning of Kameda-san's session](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/0ps6cd9kjjahq1a2xg4u.png)

He presented the history of **back-end** of AWS serverless architecture... How it was architected in the past, how it is improved at the present. 
Here are the remarks;
- **AWS Lambda is born in 2014**
   - Event = S3, Kinesis and DynamoDB only
   - Up to 1GB memories, 5mins duration, 25 invocations 
   - Lambda worker were running on EC2 instances
- **Improvement**
   - Nitro System = Nitro Controller + Nitro Hypervisor(light-weighted KVM)
   - Nitro System could run w/o EC2 instances, Containers
   - Firecracker = fast to launch micro VMs 
   - Cold Start will become faster
   - Relational Database access - VPC
   - AWS Hyperplane and V2N(VPC to VPC NAT) made true Lambda access to RDB
- **Who will invoke Lambda function?**
   - Synchronous : API Gateway
   - Asynchronous : Just put event (put object into S3, DynamoDB) to internal queue
   - Event Source Mapping : Synchronous under the hood
   - Dynamic resource allocation(Lambda) vs Stateful(Fargate)

{% embed https://twitter.com/coosuke/status/1570321077733322756 %}
{% embed https://twitter.com/coosuke/status/1570321834343813121 %}

## Conclusion
All the serverless session were AWeSome. I am a Serverless Community Builder as well but not familiar with Step Functions and EventBridge. I was lucky to listen to the experience regarding those services. And 2 Japanese talks were also impressive. I had tons of lessons learned from those sessions.

Oh do you want to see more about the summit?
OK, go on to the tweet gathering [#AWSCommunityAPAC](https://twitter.com/search?q=%23AWSCommunityAPAC)
{% embed https://togetter.com/li/1946877 %}

### P.S.
*日本語の振り返り記事は、別途執筆中で後日公開予定です。*