Amazon Route 53 vs Wix: What are the differences?
Amazon Route 53: A highly available and scalable Domain Name System (DNS) web service. Amazon Route 53 is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating human readable names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Route 53 effectively connects user requests to infrastructure running in Amazon Web Services (AWS) – such as an Amazon Elastic Compute Cloud (Amazon EC2) instance, an Amazon Elastic Load Balancer, or an Amazon Simple Storage Service (Amazon S3) bucket – and can also be used to route users to infrastructure outside of AWS; Wix: Wix.com is a web development platform enabling anyone to build a stunning online presence using simple cloud-based creation and management tools. Creating your stunning website for free is easier than ever. No tech skills needed. Just pick a template, change anything you want, add your images, videos, text and more to get online instantly.
Amazon Route 53 belongs to "DNS Management" category of the tech stack, while Wix can be primarily classified under "Website Builder".
"High-availability" is the top reason why over 187 developers like Amazon Route 53, while over 2 developers mention "WYSIWYG" as the leading cause for choosing Wix.
According to the StackShare community, Amazon Route 53 has a broader approval, being mentioned in 1396 company stacks & 470 developers stacks; compared to Wix, which is listed in 17 company stacks and 9 developer stacks.
We are looking for advice / best-practices / caveats about migrating off BIND on to Unbound https://nlnetlabs.nl/projects/unbound/about/ for internal & external (customer-facing) DNS. Is unbound suitable for this, or is it only recommended for caching? How easy or difficult is it to move 10000's of existing BIND DNS zone entries? We already use Amazon Route 53 for our AWS instances and Cloud DNS for our GCP ones, but would like to maintain internal DNS for cost, control, and latency reasons.
I usually take a slightly different tack because the technical level of people I usually am dealing with is lower. I tend to be pitching to decision makers and not tech people. A bit of my standard answer is below.
Wix and Squarespace are proprietary systems meant for unsophisticated users who want to build their own websites quickly and easily. While they are good for that specific use case, they do not offer any way to move beyond that if your needs arise. Since they are proprietary closed systems if you need something more advanced at some point your only option is to start over.
WordPress is an Open Source CMS that allows much more freedom. It is not quite as simple to setup and create a new site but if you are talking to me then you are not looking to build it yourself so that is really a non-issue. The main benefit of WordPress is freedom. You can host it on virtually any decent web hosting service and since it uses PHP and MySQL you can have virtually any developer take over a project without problem.
I believe in open source because of that freedom. It is good for me as a developer and it is good for my clients. If something were to happen to me or my company you would have no problem finding another qualified WordPress developer to take over the site in a totally seamless fashion. There would be no need to start from scratch.
Additionally the extensible nature of WordPress means that no matter what your future needs, WordPress can handle it. Adding things like e-commerce and custom quoting systems are just two examples of advanced solution's that I have added to WordPress sites years after they were first built.
WordPress is used by tiny one person businesses all the way up to major websites like the NY Times and I think it is right for this project as well.