MEAN Full Stack on Amazon AWS

DZone 's Guide to

MEAN Full Stack on Amazon AWS

This is tutorial series which will cover interesting aspects of running full stack application in Amazon AWS (from basics to advanced concepts).

· Cloud Zone ·
Free Resource

This is the first and main blog, in this, I will explain the overall idea. Please be informed that this is going to be a blog series exploring all the aspects of running the full stack application on AWS (Amazon Web Services). 

The main goal is to share the learning related to AWS but I will also explain a bit about Full stack application which we will implement in MEAN stack (Mongo, Express, Angular and Node).

  • Mongo DB: It is noSQL or document database. 
  • Express: Backend Framework.
  • Angular: Java Script framework for frontend.
  • Node: Non browser Run time environment to run Java Script.

With this blog series, you will develop understanding of following:

  • Java Script and Full Stack.
  • Software development methodology.
  • Understanding of Cloud Computing.
  • Deploying Full stack application to AWS Cloud.
  • CI/CD (DevOps)
  • Docker (Containerization)
  • Kubernetes
  • Serverless Computing
  • Security

I will demonstrate these mentioned capabilities one by one in logical order so that you gain better understanding to each concept and you will be confident with these technical stacks.

There are many ways an application can be running in AWS Cloud and will try to explore those possibilities. Please do not worry if these things are not familiar or less familiar to you as I will go in details to build the proper understanding.

I am very excited to begin this journey. Please let me know if you have any comment on the content or you want me to write blog on any specific topic in the comment section.

Happy learning!!!

New content will be added here:

angular, aws, aws architect, express, fullstack, mongo db, nodejs

Published at DZone with permission of Anupam Gupta . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}