CloudRepo

Decision at CloudRepo about Angular 2

Avatar of 64BitChris
Founder at CloudRepo
Angular 2Angular 2

The Angular 2 CLI is great, it's easy to get up and running with a project.

The really great thing about Angular 2 is it allows us to work with designers by augmenting their artifacts (html pages) with Angular directives. This allows our designs to go back and forth between designers and engineers without having to learn a new markup language (like JSX). Angular 2

1 upvote14 views

Decision at CloudRepo about Amazon DynamoDB

Avatar of 64BitChris
Founder at CloudRepo
Amazon DynamoDBAmazon DynamoDB

We store customer metadata in DynamoDB. We decided to use Amazon DynamoDB because it was a fully managed, highly available solution. We didn't want to operate our own SQL server and we wanted to ensure that we built CloudRepo on high availability components so that we could pass that benefit back to our customers. Amazon DynamoDB

1 upvote5 views

Decision at CloudRepo about Bootstrap

Avatar of 64BitChris
Founder at CloudRepo
BootstrapBootstrap

We use Bootstrap because it's great for building a quick and effective layout. It has all the components we need to build the tools our customers need. Bootstrap

1 upvote2 views

Decision at CloudRepo about Amazon CloudFront

Avatar of 64BitChris
Founder at CloudRepo
Amazon CloudFrontAmazon CloudFront

We use this because it's a CDN that sits in front of our static resources hosted in S3. It makes it so that users in other countries can have quick access to our portal. Amazon CloudFront

1 upvote2 views

Decision at CloudRepo about Amazon S3

Avatar of 64BitChris
Founder at CloudRepo
Amazon S3Amazon S3

We use Amazon S3 to host the static assets that we use for our portal. This allows us to avoid the overhead of hosting dedicated servers to server up static resources. Amazon S3

1 upvote2 views

Decision at CloudRepo about AWS CloudFormation

Avatar of 64BitChris
Founder at CloudRepo
AWS CloudFormationAWS CloudFormation

Manually clicking around the AWS UI or scripting AWS CLI calls can be both a slow and brittle process.

We needed to be able to reconstruct CloudRepo's infrastructure in case of disaster or moving to another AWS Region.

Setting up our infrastructure with CloudFormation allows us to update it easily as well as duplicate or recreate things when the need arises. AWS CloudFormation

1 upvote2 views

Decision at CloudRepo about Amazon CloudWatch

Avatar of 64BitChris
Founder at CloudRepo
Amazon CloudWatchAmazon CloudWatch

If you have a single server, checking log files is as easy as SSHing to it and viewing logs. When you move to the container world, with many servers, you need a place to aggregate and search through all of your logs. CloudWatch provides us with this and it was trivial to setup. Amazon CloudWatch

1 upvote2 views

Decision at CloudRepo about Amazon EC2

Avatar of 64BitChris
Founder at CloudRepo
Amazon EC2Amazon EC2

EC2 runs our application servers - the servers that do all the heavy lifting for CloudRepo. Amazon EC2

1 upvote2 views

Decision at CloudRepo about Amazon EC2 Container Service

Avatar of 64BitChris
Founder at CloudRepo
Amazon EC2 Container ServiceAmazon EC2 Container Service

We use the container service so that we can deploy our application services with Dockerfiles, so that we can test locally and deploy to AWS simply.

Additionally, the ability to scale containers and have them automatically restart in case of failure is very helpful to our operations. Amazon EC2 Container Service

1 upvote2 views

Decision at CloudRepo about Amazon S3

Avatar of 64BitChris
Founder at CloudRepo
Amazon S3Amazon S3

We store the software components that CloudRepo stores for its customers here for the following reasons:

  • Data is Encrypted at Rest
  • Data is stored across multiple physical locations
  • Pricing is competitive
  • Reliability is industry leading and our customers need to be able to access their data at all times list text here Amazon S3
1 upvote2 views