4 ms·
Question for AWS users: What are you running on AWS? (web, DB, static content, ...)
by hedgehog 18y ago
Question for AWS users: What are you running on AWS? (web, DB, static content, ...)
- bemmu 18y agoFetching URLs mentioned on Twitter. It scales great, but turns out the part where I save the results to a central MySQL DB does not. Surprised that you max out your InnoDB UPDATEs after only around two thousands per second. Will try memcachedb.
- iamelgringo 18y agoElastic IP + EC2 + Elastic Block for hosting. S3 for backups. I also make judicious use of Mechanical Turk for usability testing. I also use Google apps for my domain for email hosting (free). I also use Woopra's real time analytics (free). I have an online store that I'm paying Yahoo Merchant Solutions for. I also pay for an extra line with Vonage for my business line. ($10 a month). I've used Google Adwords for advertising occasionally.
- calvin 18y agoS3 for data backups and file storage. CloudFront as a CDN. A few EC2 instances for data processing and Elastic IPs for them.
- jaaron 18y agoDifferent setup for different projects. Latest was all AWS: EC2 servers pushing out most static content to S3. Also use EC2 for test and staging servers as then we only need them up for the actual test or staging period.
- rmanocha 18y agoI use AWS mostly for static content hosting (S3 + CloudFront). I plan to shift over to EC2 when I have enough users to warrant the expenses (Currently on a 256MB slice - $20/month).
- fireteller 18y agoI'm using S3/cloudfront for assets, user data and backups, EC2 and elastic IPs, SQS, and FPS for payment processing. Love it. To the question I also pay for authsmtp, and will probably be using the pay level of "New Relic" as well soon, for rails profiling.
- wensing 18y agoPros and cons of FPS?
- fireteller 18y agoFPS provides a robust set of interface tools to the amazon payments system. It enables a number of payment models that other services don't offer such as, subscription, aggregate (i.e. micropayment), marketplace/3 party (i.e. user to user transactions with optional commission), and the prices are competitive. You can even do user to user transfers with no fees. They also offer fraud protection. It is not trivial to implement in an application but does seem to be very concise for the features it provides. The con for this flexibility naturally is increased complexity. They do offer a 'Simple Pay' solution if you don't need the extra features, but I've not used that. During development you can tie you application to the FPS 'sandbox' which simulates the complete user experience as well as virtual payments and fees so that you can see exactly how things will work in production from various points of view with out actually moving money around. I needed subscriptions, so I could not use the other popular solutions (when the decision was made), and therefore can't compare. However, I refuse to use paypal because they put 100% of the risk on the account holder, while at the same time not disclosing information about the purchaser to allow for fraud investigation, this is flat out unacceptable.
- Derrek 18y agoI second the request for pros and cons of FPS
- ible 18y agoS3 for data backups, storage. Bunch of EC2 instances with EBS for crunching data and running web crawler.