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).

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.

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.

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.

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

Clojure simplifies and reduces the coding efforts involved in creating CloudRepo. The fact that it runs in the JVM gives us access to all the libraries that we could ever need. Our code base is much smaller and easier to reason about than it would have been had we gone with pure Java.

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.

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.

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

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.

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.

jQuery is required by some of the libraries we use on the website. Other than that, having jQuery around is just great for manipulating the DOM or other common functions.

Since we generate a static website for our website, AWS S3 provides hosting for us so that we don't have to run our own servers just to serve up static content.

The pricing is great as you only pay for what you use.

CloudFront is our CDN - it allows our website to be retrieved quickly and viewed all around the world.

We started with a bootstrap based template and then completely rewrote it due to poor design of the template. Using boostrap properly was a great experience - once you learn it and use it properly, it's simple to use and very good at being responsive and adapting to the various screen view.

We don't leverage much of the new features in HTML5, except for the new Doctype - since it was the latest when we started designing, that's what we used.

We wanted to pay the cost for website generation up front. Doing this allows us to put our website up in AWS S3 where it can be served reliably and for cheap.