The article, Serverless API with ReactJS, was first published on the Serverless Guru website. Let’s build a Serverless REST API for our ReactJS website! In my last article, Deploy ReactJS App with S3 Static Hosting, we discussed hosting a simple React app on AWS with S3. This works great for simple static pages but what if you want to do something more? How do you host your API on S3?
There is a paradox at the heart of serverless. While it’s promoted as a very agile way to develop, a way to push your product as fast as possible to your customers, many development teams find it really difficult to work fast. Why does this happen and can we solve the issue? Let’s start with what makes serverless such a powerful paradigm. Serverless rests on three legs, each of which contributes to the agility that serverless is known for.
AWS Lambda has gained good traction for building applications on AWS. But, is it really the best fit for all use cases? Since its introduction in 2014, Lambda has seen enthusiastic adoption – by startups and enterprises alike. There is no doubt that it marks a significant evolution in cloud computing, leveraging the possibilities of the cloud to offer distinct advantages over a more traditional model such as EC2.
Many clients have asked me, “When do I use DynamoDB streams vs Kinesis?” It’s a great question, since both services are very similar, especially when you process their records with Lambda functions. So let’s break it down and look at the key differences between Kinesis and DynamoDB streams. When it comes to streaming and processing real-time events on AWS, Kinesis is the de facto solution in AWS.
Seed is a fully managed CI/CD pipeline for Serverless Framework applications. In one of our previous posts we looked at how to build a CI/CD pipeline for Serverless apps on AWS with CircleCI. Today, we’ll look at how to do the same with Travis CI. The purpose of these posts is to dive deep into real-world CI/CD setups, something which most of the tutorials out there skip. We’ll try to illustrate how to set up something similar to Seed but using Travis CI instead.
Did you know that CloudFormation tags don’t automatically propagate to some resource types? Chief among these are CloudWatch log groups, which means you can’t include them in your cost monitoring (via cost allocation tags) among other things. The only way to tag CloudWatch log groups right now is via API calls. You can do this with the AWS SDK, or using the AWS CLI. This is hugely inconvenient!
