xylex

You're looking for setting up "Geo DNS" - Google that and it will have the info you're looking for. My preference is to use AWS's Route53 for this, good tutorial at http://www.cyberciti.biz/cloud-computing/aws/route-53-geodns-tutorial/

Just graduating college and going into the software field? If so, I'd go sleek and slim for your personal laptop. You're likely to end up with a big bulky powerhouse from work, always nice to have something more portable too.

Earthenware- that error is related to too many local sockets being opened up in the same port range. If this is something you're seeing normally under your traffic patterns, you might want to consider using persistent connections so that you're not constantly spinning up new sockets. http://www.php.net/manual/en/mysqli.persistconns.php

Yeah, MongoDB would work for this. Reason I'm suggesting it is that you're basically trying to do that with the earlier suggestions - get everything that looks like it could be a match (Map) - and then filter out just the ones that you want (Reduce). Doing it with just MySQL and PHP means that this process in single threaded/single instance orientated and won't scale well to huge datasets - might not be an issue in this specific use case, but if it's a learning project, might as well go big. Mongo runs a single thread per instance in its map/reduce handling, hence the idea to shard it across multiple instances.

This sounds like a problem for map-reduce across a few shards. Any reason you're picking MySQL?

Barracuda's e-mail security service might be what you're looking for. Depending on your size you can buy it from them or buy a fractional license from a reseller.

PHP requires you to be explicit. That's not necessarily a bad thing. For example, if you can import wildcard namespaces: namespace A{ class Foo{ public function bar(){ echo "A"; } } } namespace B{ class Foo{ public function bar(){ echo "B"; } } } namespace C{ use \A; use \B; $a = new Foo(); $a->bar(); } What's echoed?

One of the nice things with how Twig integrates with Symfony is that it makes it really easy to do edge side includes (ESI). If you can leverage that for performance, getting stuff cached before your server will obviously blow away any benchmark.

There isn't a one size fits all solution to performance and scalability, and only dealing with bottlenecks as they arise (like #3) can quickly add significant amounts time and expense. The biggest factor here is going to be finding someone with the experience and knowledge to anticipate where the bottlenecks for your specific requirements are most likely to show up and pre-addressing them in their architecture. There are plenty of best practices and methods used to scale and be performant, experience is going to be the factor in knowing which ones apply and should be implemented.

Have you read Fowler's Refactoring book? That provides a bit of a framework for tackling these types of issues in a safe and iterative manner.

I think you're referring to the Internet Garbage Collection (IGC) algorithm run by the various countries governments to periodically free up space on their countries Internet to make room for new pages. Countries like the US have lots of Internet and tune their algorithm differently than a small country like New Zealand, which has less room for Internets. For websites that retain old content, you need to apply for an IGC Meta tag to each of the country's governments that you want to retain the information. If your content is accepted for retention, you then add that key to an "igc:nodelete" header in your server response, this way you are ensured old content is retained for that country's Internets.

Little different direction than some of the above suggestions, but was just at this presentation that was one of the better explanations of how to properly setup a REST service and what to put where - Longer talk, but the general idea is maximize the use of what HTTP offers and architect your protocol give you long term maintainability and backwards compatibility.

Premiso- Just noticed the beer. You from the NW?

I'm not sure that the regex matching for the presence of the terms is going to be very valuable. For example, if the listing refers to a URL that ends in /contact.php, that would match as well as one that specifies "looking for a developer with a strong PHP background." Any thoughts of using the Solr extension and Lucene to analyze for relevancy & tagging? Seems like this would be an ideal use case for that.

I've always thought the beer@work thing was to try to keep everyone coding at the Ballmer Peak.