React website AWS CI/CD Pipeline with Cloudformation Template

In this article, we will look into steps to create an AWS CI/CD pipeline to deploy a static react app on AWS S3 using the AWS Cloudformation Template. We will use AWS Codecommit as a source code repository and AWS Codebuild to build the code.

React App

We can simply create a react app using create-react-app command in terminal.

npx create-react-app <app_name>

After creating an app, use these commands to open the react app in your browser to check if the app is working or not.

cd <your_app_name>
npm start

I prefer using visual studio code and it’s terminal. You can use any other as per your convenience.

VS Code Terminal & React App Files

Pushing Code to CodeCommit

Now we will create a repository on CodeCommit. We will navigate to Codecommit from the management console and create a new repository.

After creation clone your repo to your local system or either upload the files and commit them.

You can Copy paste these files from your react app folder, commit and push it to your code commit repository. You should have the following files

#cicd-pipeline #aws-cloudformation #aws #devops #react

What is GEEK

Buddha Community

Serverless CI/CD on the AWS Cloud

CI/CD pipelines have long played a major role in speeding up the development and deployment of cloud-native apps. Cloud services like AWS lend themselves to more agile deployment through the services they offer as well as approaches such as Infrastructure as Code. There is no shortage of tools to help you manage your CI/CD pipeline as well.

While the majority of development teams have streamlined their pipelines to take full advantage of cloud-native features, there is still so much that can be done to refine CI/CD even further. The entire pipeline can now be built as code and managed either via Git as a single source of truth or by using visual tools to help guide the process.

The entire process can be fully automated. Even better, it can be made serverless, which allows the CI/CD pipeline to operate with immense efficiency. Git branches can even be utilized as a base for multiple pipelines. Thanks to the three tools from Amazon; AWS CodeCommit, AWS CodeBuild, and AWS CodeDeploy, serverless CI/CD on the AWS cloud is now easy to set up.

#aws #aws codebuild #aws codecommit #aws codedeploy #cd #cd pipeline #ci #ci/cd processes #ci/cd workflow #serverless

How native is React Native? | React Native vs Native App Development

If you are undertaking a mobile app development for your start-up or enterprise, you are likely wondering whether to use React Native. As a popular development framework, React Native helps you to develop near-native mobile apps. However, you are probably also wondering how close you can get to a native app by using React Native. How native is React Native?

In the article, we discuss the similarities between native mobile development and development using React Native. We also touch upon where they differ and how to bridge the gaps. Read on.

A brief introduction to React Native

Let’s briefly set the context first. We will briefly touch upon what React Native is and how it differs from earlier hybrid frameworks.

React Native is a popular JavaScript framework that Facebook has created. You can use this open-source framework to code natively rendering Android and iOS mobile apps. You can use it to develop web apps too.

Facebook has developed React Native based on React, its JavaScript library. The first release of React Native came in March 2015. At the time of writing this article, the latest stable release of React Native is 0.62.0, and it was released in March 2020.

Although relatively new, React Native has acquired a high degree of popularity. The “Stack Overflow Developer Survey 2019” report identifies it as the 8th most loved framework. Facebook, Walmart, and Bloomberg are some of the top companies that use React Native.

The popularity of React Native comes from its advantages. Some of its advantages are as follows:

• Performance: It delivers optimal performance.
• Cross-platform development: You can develop both Android and iOS apps with it. The reuse of code expedites development and reduces costs.
• UI design: React Native enables you to design simple and responsive UI for your mobile app.
• 3rd party plugins: This framework supports 3rd party plugins.
• Developer community: A vibrant community of developers support React Native.

Why React Native is fundamentally different from earlier hybrid frameworks

Are you wondering whether React Native is just another of those hybrid frameworks like Ionic or Cordova? It’s not! React Native is fundamentally different from these earlier hybrid frameworks.

React Native is very close to native. Consider the following aspects as described on the React Native website:

• Access to many native platforms features: The primitives of React Native render to native platform UI. This means that your React Native app will use many native platform APIs as native apps would do.
• Near-native user experience: React Native provides several native components, and these are platform agnostic.
• The ease of accessing native APIs: React Native uses a declarative UI paradigm. This enables React Native to interact easily with native platform APIs since React Native wraps existing native code.

Due to these factors, React Native offers many more advantages compared to those earlier hybrid frameworks. We now review them.

#android app #frontend #ios app #mobile app development #benefits of react native #is react native good for mobile app development #native vs #pros and cons of react native #react mobile development #react native development #react native experience #react native framework #react native ios vs android #react native pros and cons #react native vs android #react native vs native #react native vs native performance #react vs native #why react native #why use react native

React website AWS CI/CD Pipeline with Cloudformation Template

In this article, we will look into steps to create an AWS CI/CD pipeline to deploy a static react app on AWS S3 using the AWS Cloudformation Template. We will use AWS Codecommit as a source code repository and AWS Codebuild to build the code.

React App

We can simply create a react app using create-react-app command in terminal.

npx create-react-app <app_name>

After creating an app, use these commands to open the react app in your browser to check if the app is working or not.

cd <your_app_name>
npm start

I prefer using visual studio code and it’s terminal. You can use any other as per your convenience.

VS Code Terminal & React App Files

Pushing Code to CodeCommit

Now we will create a repository on CodeCommit. We will navigate to Codecommit from the management console and create a new repository.

After creation clone your repo to your local system or either upload the files and commit them.

You can Copy paste these files from your react app folder, commit and push it to your code commit repository. You should have the following files

#cicd-pipeline #aws-cloudformation #aws #devops #react

AWS CloudFormation Template Basics

Have you ever tried to move resources from one AWS region to another? It can be quite painful. You have to figure out how all of the resources connect together, then plan out what order you need to recreate them. Fortunately, AWS has a simpler way of doing that. It’s called CloudFormation.

CloudFormation allows you to define all of those resources (and their relationships) in a JSON or YAML file called a template. The template can take in some parameters too, which means you can define multiple environments with a single template.

In this article, I’ll explain the fundamental sections of a CloudFormation template and how to use it to deploy a stack.

CloudFormation Template Structure

Cloud formation templates are YAML files with a few specific root properties that are referred to as sections. If you want to see the sections not covered in this article, checkout out the CloudFormation User Guide.

Parameters

The parameters section allows you to create parameters (duh). Using parameters allows you to create a single template that can be reused across multiple environments. Just change the parameter values and you have a new environment–or at least an updated one.

#cloudformation #aws #aws-s3 #aws cloudformation

Creating CI/CD Pipeline for AWS ECS

Amazon Elastic Container Service (ECS) is Amazon’s solution for running and orchestrating Docker containers. It provides an interface for defining and deploying Docker containers to run on clusters of EC2 instances.

In this blog post I will explain how to run simple node.js application in Amazon EC2 Container Service (ECS) and then in the next part we will create CI/CD Pipeline.

You can download the source code from my GitHub account.

Prerequisites

1. You should have VPC created in your account with Public and Private Subnets and Private subnets should have a route to NAT Gateway.
2. Amazon Elastic Container Service (ECS) Cluster
3. Application Load Balancer
4. ECR Repository
5. Permission to Create IAM roles, policies
6. AWS CLI
7. Application Load Balancer

#docker #aws #devops #aws-ecs #ci/cd pipeline