Anyone have experience with either of these setups? Am currently on a straight forward CDN - rackspace. But as I move along I'd be needing some PHP on them pages, so after some research and digging around STM, I've came down to 2 choices:
1. AWS EC2 + Route 53
2. AWS S3 + Cloudfront CDN
A programmer i'm working with recommends option 1, with feedback that 2. does not support dynamic PHP. But with some googling and searching around, seems like Cloudfront does indeed support PHP.
going in circles with these 2, if anyone has any input it'd be greatly appreciated! especially in terms of performance/price/speed.
CloudFront is a CDN. CDN's don't process PHP for you, so #1 is your only option.
I'm not sure why you are focused on Amazon?
Plenty of providers can give you an unmanaged VPS for $10-20/month that will outperform an EC2 instance, e.g. Linode, DigitalOcean, Ramnode.
You can use Amazon's Route 53 for DNS if you want, and CloudFront as a CDN, both of these are separate to the servers you use and provider.
Basic server + cloudflare is pretty solid. You'd be amazed as the performance you can deliver at such a low cost.
It's pretty straight forward if our main GEO consists only of one country (then we can get a basic server + CDN closer to that geo)...., but what if we're dealing with large volume of mobile traffic from countries in different continents.....what servers/services can we use to serve our PHP mobile landers with the fastest loading/redirect/connecting speed from our server to our end-users with a monthly budget of $600 - $1000 to spare?
It can accelerate delivery of that content, but can't process the PHP. A clear difference to those involved with that kind of stuff but a bit muddy to others.
CloudFront can pull content from your server on the fly and act as a bridge between your user and your server, allowing it to pull dynamic (PHP) content through their network. If your content changes every few minutes you can actually cache it. If it changes each page load per user, you can't, and arbitraging it through the CloudFront network can just help deliverability but may not (it depends...).
What works well is to layer CloudFront over your server and have it directly pull cacheable content like images, then have a rule telling it to not touch PHP i.e. not cache at all.
This is not ideal to do over the top of a tracking system unless you know what you're doing as it gets a bit complex.
Got it Zeno, many thanks!
I've just set up on S3 and Cloudfront, would it be considered good practice for mobile campaigns, mainly from a speed point of view?
What about add NodeJS in myserver,
1. Install Selft Hosted Tracker like
2. Create Independent redirected script using nodejs, that connected to tracker database
any ideas?