This blog shows how to set up a MongoDB database environment on the cloud, AWS EC2 with Amazon Linux.  Pre requirement You'll need an AWS account, if you never set up an AWS account before, go here to create an AWS account. Create EC2 Instance First, we'll need to set up an EC2 instance, then we'll SSH into the EC2 instance and set up the MongoDB database. Create EC2 Instance with AWS Linux AMI. Choose t2.micro. During the setup everything as default is fine for this blog, we'll use default VPC, as long as the new EC2 can access the internet.  For the security group, we'll just open port 22, so we can SSH later to into EC2 for setup MongoDB.

This blog shows how to set up MongoDB 4.4 Community version on Mac OS, also will create a simple database, table, and collection, and how to backup and store data by using mongoexport and mongoimport. Install MongoDB Server Install MongoDB on Mac is a little different compare to the Mac, you'll need brew to install the MongoDB, on this blog assume brew is already installed on Mac. Download Homebrew formula for MongoDB brew tap mongodb/brew Install MongoDB in macOS brew install mongodb-community@4.4 Install MongoDB Tools Starting from MongoDB 4.4, use brew will also install the mongodump, mongoexport, mongoimport and some other commands. Install MongoDB Compass MongoDB Compass is the GUI tool, you should install on your local development environment so you can connect to the MongoDB server and run the query from GUI.

This blog shows how to set up MongoDB 4.4 Community version on windows 10 as a local development environment, create a simple database, table, and collection, and how to backup and store data by using mongoexport and mongoimport. Install MongoDB Server First, go to the official MongoDB installation link here to download the installation file. After the download following the installation wizard to install MongoDB.  Choose Location The default location is under windows' C drive, you can modify the location to other places. I'm using the D:\MongoDB on this blog. Choose Install MongoDB as Service If you choose to install MongoDB as a service, the installation will create a windows service so the MongoDB will be running as background. I think most of the time you should choose.

This blog shows how to use nconf for Node.js environment configuration. Environment config is needed in any coding language, for instance, the database endpoint for each of the environments, your development, and production should be different.  Install the nconf Now, use nconf is very easy, first add to your solution's dependency package. npm install nconf --save Use the nconf You can write a helper class like following to use nconf. First, you import the package to your file, load json file, then return the nconf. const nconf = require('nconf'); nconf.file('env.json'); exports.config = nconf; This JSON file will be your App's environment configuration, you can put all your configuration dependencies to this JSON file. Later, each of your environments just updates this JSON file to match that environment's config.

S3 is a cloud serverless object storage solution provided by AWS. That means you can store any files to S3 without maintaining the backend machine, and how to manager these servers are AWS's responsibility. Also it is very cheap, you can reference the pricing for each region you'll be using for the S3. For example, at the moment 2020 when I check the US East Ohio, the standard s3 first 50TB/month is $0.023 per GB, it also depends on how frequently you'll use that file the price will be changed. If you just want to store some files in S3 for a long time for archive purposes, you can use the S3 Glacier Deep Archive which is $0.00099 per GB.  So, what am I doing on this blog is to show some sample code that how to upload files to AWS by Node.js. Setup IAM User with S3 permission The first thing that needs to do before writing the Node.js code is, you have to set up a user with S3 permissions to access your S3 Bucket.

Here a few commands if you want to get a list of git commit information. This will list all the commits by the contributor. git log --author="Contributor's name" Get commit from 19 April 2020. git shortlog -s -n --since="19 April 2020" Get commit for the contributor since 19 April 2020. git log --author="Your contributor" --oneline --since="19 April 2020" Same commit log but make it pretty print.  git log --pretty="%C(Yellow)%h %C(reset)%ad (%C(Green)%cr%C(reset))%x09 %C(Cyan)%an: %C(reset)%s" --author="contributor" --since="19 May 2020 12:00:00 AM" Quit the command line by :q.

This blog shows how to backup your AWS DynamoDB table (on the cloud) to your local DynamoDB environment. It could help in case you want to do a prototype but using production data. Export table to S3 In the first step, you need to login into AWS console's DynamoDB main page, choose the table then choose export to s3 bucket. At the moment I'm writing this, you'll need to set up the Point in time backup then you can export to S3. It says could charge, but once moved to s3 you can change it back. Download data zip file Once DynamoDB export table to s3, you should be able to find your data under {your bucket}/AWSDynamoDB/{unique guid}/data, download the zip file to your OS. Following is the JSON file I download from the S3 bucket, noticed that no comma after each item object. Not sure why but you can just simply do replacement by adding a comma, after each item object.

This blog shows how to move DynamoDB local table and data to the DynamoDB Web Service, unlike SQL Database, you can use the backup file to restore to a different environment. So far at this moment, I'm writing, have not found out any other way to move Dynamo local to AWS Web service. So following sample code will just loop each item and use aws-sdk to put the request to the AWS DynamoDB web service. DynamoDB table schema Following is the sample table schema, you can manually add the table on AWS Dynamo cloud or use SDK to create a table programmatically.

AWS DynamoDB is one of the AWS services for the NoSQL database on the cloud. You can create an AWS account then go to the AWS console's DynamoDB section to create a table and add items. On the SQL database, you or someone need to create a server for the SQL database, you then access the SQL database on that server by SQL query, but on the other hand, AWS will be managing the server for this NoSQL, serverless DynamoDB database. You can access it by the HTTP request. What about the local environment!? On the SQL side, you can set up the SQL database on your local, how about the DynamoDB? You can reference this blog for how to setup Dynamodb in your local environment. This blog will show how to create a DynamoDB table in your local environment. The following example code was using Node.js running on Mac OS. npm version is 6.12.0, node version is v12.13.0.

AWS DynamoDB is a document database that provides single-digit millisecond performance, it is a serverless database, which means you can focus on use applications to access the DynamoDB and AWS will manage the server for you. It's also available in multiple AWS regions and has built-in Cache DAX.  Another good reason to use DynamoDB is the free tier provided by DynamoDB. up to 25 GB storage, 25 write capacity units, and 25 read capacity units are free. Compare to MongoDB, depend on the MongoDB cloud provider it might be 500MB storage if you try to look for a free tier.  Now, in this blog I'll show how to set up DynamoDB locally, also show a few simple codes to access local DynamoDB. Download DynamoDB Go to this link from AWS to download DynamoDB, the different region has different DynamoDB file, so choose the region you'll be using for DynamoDB. After unzipping the file, run the following command.