Amazon/Nintendo Presentation on Modernization of Nintendo eShop: Microservice and platform engineering
Amazon/Nintendo Presentation on Modernization of Nintendo eShop: Microservice and platform engineering
by Dude-Babes
8 Comments
Dude-Babes
I don’t know if this is of interest to most but it’s Nintendo and getting to look at **ANYTHING** from Nintendo behind-the-scene is always fascinating to me.
Taken from AWS video above…
> Nintendo eShop is a web-based ecommerce service where you can browse and purchase digital software from Nintendo Switch and other Nintendo platforms. As the digital business continues to grow, it is essential for Nintendo Systems to modernize the service’s system to improve agility and go-to-market speed. In this session, hear from Nintendo Systems about the decision and the process of decoupling their monolithic application into microservice-based architecture, and hear how they mitigate the pain points of microservice through platform engineering. Discover how Nintendo Systems develops a platform for autonomous, cross-functional development using the AWS infrastructure.
Just a really interesting look at Nintendo working on the eshop, since we all know how frustrating they’ve been on anything in this realm before. They built the eShop to be maintainable for at least 20 years.
* The frontend of the eShop on 3DS and Switch are written in React as a single-page application.
* Using the Domain Driven Design Principle to split the modular monolithic backend into an infrastructure that can be more manageable and maintained easily to handle increasing requirements as time goes by
* From 2017 and on, they realized it’s difficult to transition DevOps to other projects because they were engrained into services. Sometime in 2020 they began looking into Platform Engineering which has continued on.
It’s really just a lot of jargon and I mostly understand it myself but it is interesting since Nintendo’s evolution here.
Cyber_Punks
5 minutes…I wish I understood this lmao
Flygsand
It’s always cool to see Nintendo being this transparent. They went from on-premises to all-in on AWS! I think they made some smart decisions here. The engineer in me would love nothing more than to geek out with Kubernetes all day, but if your organization doesn’t have a dedicated ops team then you’d best to stay away from it. Nintendo has chosen to leverage a lot of AWS functionality and ECS just integrates tighter with the rest of the AWS ecosystem.
We went through a very similar progression at a former workplace, although with a much smaller DevOps organization (as in just me).
– On-premises monoliths
– Containerized monoliths on pure self-managed EC2
– Microservices on ECS
– A bunch of solutions for e.g. data processing and observability, engineered entirely by gluing AWS services together
– Infrastructure-as-code to manage it all (Terraform)
– Self-service IaC with an account-based model
Thanks for posting this!
Dracogame
Nice case study for AWS. Microservices are the future. Not really interesting for fans tho…
BayonettaAriana
I did not watch this whole video, but man I wish they’d make the eShop feel more responsive. To me it feels soooo laggy. I assume it is a webapp but I wish they’d build a native app front end to make it more responsive.
stvwlkr
Fascinating, thanks very much for sharing. Really interesting to hear what goes on under the hood when doing a seemingly simple task like launching a game on Switch. So many cloud apps in the background that no gamer is ever aware of (until they fail!)
Two_Shekels
Oh hey I was in the live audience for this one. Presenters easily got 3x the applause of any other normal session I attended.
haxxanova
Any insight offered in this why it performs so absolutely terribly?
Webp amd cache those thumbnails, Nintendo. And clean up the spaghetti React code?
8 Comments
I don’t know if this is of interest to most but it’s Nintendo and getting to look at **ANYTHING** from Nintendo behind-the-scene is always fascinating to me.
Taken from AWS video above…
> Nintendo eShop is a web-based ecommerce service where you can browse and purchase digital software from Nintendo Switch and other Nintendo platforms. As the digital business continues to grow, it is essential for Nintendo Systems to modernize the service’s system to improve agility and go-to-market speed. In this session, hear from Nintendo Systems about the decision and the process of decoupling their monolithic application into microservice-based architecture, and hear how they mitigate the pain points of microservice through platform engineering. Discover how Nintendo Systems develops a platform for autonomous, cross-functional development using the AWS infrastructure.
Just a really interesting look at Nintendo working on the eshop, since we all know how frustrating they’ve been on anything in this realm before. They built the eShop to be maintainable for at least 20 years.
* The frontend of the eShop on 3DS and Switch are written in React as a single-page application.
* Using the Domain Driven Design Principle to split the modular monolithic backend into an infrastructure that can be more manageable and maintained easily to handle increasing requirements as time goes by
* From 2017 and on, they realized it’s difficult to transition DevOps to other projects because they were engrained into services. Sometime in 2020 they began looking into Platform Engineering which has continued on.
It’s really just a lot of jargon and I mostly understand it myself but it is interesting since Nintendo’s evolution here.
5 minutes…I wish I understood this lmao
It’s always cool to see Nintendo being this transparent. They went from on-premises to all-in on AWS! I think they made some smart decisions here. The engineer in me would love nothing more than to geek out with Kubernetes all day, but if your organization doesn’t have a dedicated ops team then you’d best to stay away from it. Nintendo has chosen to leverage a lot of AWS functionality and ECS just integrates tighter with the rest of the AWS ecosystem.
We went through a very similar progression at a former workplace, although with a much smaller DevOps organization (as in just me).
– On-premises monoliths
– Containerized monoliths on pure self-managed EC2
– Microservices on ECS
– A bunch of solutions for e.g. data processing and observability, engineered entirely by gluing AWS services together
– Infrastructure-as-code to manage it all (Terraform)
– Self-service IaC with an account-based model
Thanks for posting this!
Nice case study for AWS. Microservices are the future. Not really interesting for fans tho…
I did not watch this whole video, but man I wish they’d make the eShop feel more responsive. To me it feels soooo laggy. I assume it is a webapp but I wish they’d build a native app front end to make it more responsive.
Fascinating, thanks very much for sharing. Really interesting to hear what goes on under the hood when doing a seemingly simple task like launching a game on Switch. So many cloud apps in the background that no gamer is ever aware of (until they fail!)
Oh hey I was in the live audience for this one. Presenters easily got 3x the applause of any other normal session I attended.
Any insight offered in this why it performs so absolutely terribly?
Webp amd cache those thumbnails, Nintendo. And clean up the spaghetti React code?