Amazon Route 53

Amazon Route 53

Utilities / Application Utilities / DNS Management

Decision at SalesAutopilot Kft. about AWS CodePipeline, Jenkins, Docker, vuex, Vuetify, Vue.js, jQuery UI, Redis, MongoDB, MySQL, Amazon Route 53, Amazon CloudFront, Amazon SNS, Amazon CloudWatch, GitHub

Avatar of gykhauth
CTO at SalesAutopilot Kft.
AWS CodePipelineAWS CodePipeline
jQuery UIjQuery UI
Amazon Route 53Amazon Route 53
Amazon CloudFrontAmazon CloudFront
Amazon SNSAmazon SNS
Amazon CloudWatchAmazon CloudWatch

I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

11 upvotes9.9K views

Decision at Limited about Amazon EC2 Container Service, Docker, Amazon VPC, Amazon Route 53, Amazon SQS, Amazon SES, Amazon CloudFront, nginx, Unicorn, Ruby, Travis CI, Selenium, RSpec, Rails, Amazon ElastiCache, Redis, Sidekiq, Elasticsearch, PostgreSQL

Avatar of sgbett
Managing Director at Limited
Amazon EC2 Container ServiceAmazon EC2 Container Service
Amazon VPCAmazon VPC
Amazon Route 53Amazon Route 53
Amazon SQSAmazon SQS
Amazon SESAmazon SES
Amazon CloudFrontAmazon CloudFront
Travis CITravis CI
Amazon ElastiCacheAmazon ElastiCache

In 2010 we made the very difficult decision to entirely re-engineer our existing monolithic LAMP application from the ground up in order to address some growing concerns about it's long term viability as a platform.

Full application re-write is almost always never the answer, because of the risks involved. However the situation warranted drastic action as it was clear that the existing product was going to face severe scaling issues. We felt it better address these sooner rather than later and also take the opportunity to improve the international architecture and also to refactor the database in. order that it better matched the changes in core functionality.

PostgreSQL was chosen for its reputation as being solid ACID compliant database backend, it was available as an offering AWS RDS service which reduced the management overhead of us having to configure it ourselves. In order to reduce read load on the primary database we implemented an Elasticsearch layer for fast and scalable search operations. Synchronisation of these indexes was to be achieved through the use of Sidekiq's Redis based background workers on Amazon ElastiCache. Again the AWS solution here looked to be an easy way to keep our involvement in managing this part of the platform at a minimum. Allowing us to focus on our core business.

Rails ls was chosen for its ability to quickly get core functionality up and running, its MVC architecture and also its focus on Test Driven Development using RSpec and Selenium with Travis CI providing continual integration. We also liked Ruby for its terse, clean and elegant syntax. Though YMMV on that one!

Unicorn was chosen for its continual deployment and reputation as a reliable application server, nginx for its reputation as a fast and stable reverse-proxy. We also took advantage of the Amazon CloudFront CDN here to further improve performance by caching static assets globally.

We tried to strike a balance between having control over management and configuration of our core application with the convenience of being able to leverage AWS hosted services for ancillary functions (Amazon SES , Amazon SQS Amazon Route 53 all hosted securely inside Amazon VPC of course!).

Whilst there is some compromise here with potential vendor lock in, the tasks being performed by these ancillary services are no particularly specialised which should mitigate this risk. Furthermore we have already containerised the stack in our development using Docker environment, and looking to how best to bring this into production - potentially using Amazon EC2 Container Service

1 upvote134 views

Decision at Promethean TV about Amazon Route 53

Avatar of OneReality
CTO at Promethean TV
Amazon Route 53Amazon Route 53

PrometheanTV utilizes the Amazon Route 53 service to manage various domains utilized by the products and services. Amazon Route 53

1 upvote5 views

Decision at Kalibrr about Amazon Route 53

Avatar of TimDumol
Lead Software Architect at Kalibrr
Amazon Route 53Amazon Route 53

Amazon Route 53 is a convenient way to manage our DNS routes. We just use the web UI for now, since we don't have any complex DNS setups. Amazon Route 53

1 upvote5 views

Decision about Amazon Route 53

Avatar of v0lkan
Chief Executive Philosopher at
Amazon Route 53Amazon Route 53

Since most of infrastructure is on AWS, Route53 is the obvious DNS of choice.

I鈥檓 also considering CloudFlare, but haven鈥檛 decided the pros and cons of migrating yet. Amazon Route 53

1 upvote

Decision about Amazon Route 53

Avatar of thanhbn87
Platform leader at Altplus Vietnam
Amazon Route 53Amazon Route 53
  • DNS registration.
  • DNS routing for private/local in VPC.
  • DNS HA/Load balancing. Amazon Route 53
1 upvote

Decision at Aquarius Logics about Amazon Route 53

Avatar of aqualogics
Managing partner at Aquarius Logics
Amazon Route 53Amazon Route 53

Amazon AWS Domain Name Services. The logical choice for AWS hosted web sites. Amazon Route 53

1 upvote

Decision at Goyoboard about Amazon Route 53

Avatar of azureru
Senior Software Engineer at Appsindo Technology
Amazon Route 53Amazon Route 53

We utilize it as main DNS for fron-tend servers, Dynamic DNS for internal VPCS and simple signal flag storage for autoscaled instances Amazon Route 53

1 upvote