hide

Read Next

Peek Behind the Scenes at Socialize

Socialize is well known for the robust infrastructure of its drop-in social platform, which handles over 20 requests per second -- over 1.5 million requests in the past 24 hours across thousands of mobile apps and millions of end users.  But how does a team of just ten employees set up and manage such an infrastructure?  Here's a sneak peek behind the curtain so you can see how it's done.

Our databases, servers, Partner API and SDKs have been architected to always push meta data to our systems.  Each component is built as stand-alone infrastructure, allowing us to audit and optimize intelligence on how each piece is performing.  We then leverage tools by Splunk to turn our massive log files into actionable intelligence, and we use TeamCity for continuous integration.  Even further behind the scenes we are using Nginx, Apache, load-balanced Amazon AWS & RDS, Robotium, Selenium, gh-unit, OCMock, KIF, Google App Engine and other best-in-class technologies. It all comes together on a 50" flatscreen monitor and 32" iMac that our Quality Assurance engineer monitors and all our employees can see.  We even have a flashing green light that turns red when a build breaks or we detect latencies in our system, and all our developers are notified when there's a problem.

Here's a video of Sean describing the systems and how we use them to ensure Socialize is always available and performing flawlessly in your app:

More pictures of our system:

Click to Enlarge -- Our Performance Dashboard Socialize is well known for the robust infrastructure of its drop-in social platform, which handles over 20 requests per second -- over 1.5 million requests in the past 24 hours across thousands of mobile apps and millions of end users.  But how does a team of just ten employees set up and manage such an infrastructure?  Here's a sneak peek behind the curtain so you can see how it's done. Our databases, servers, Partner API and SDKs have been architected to always push meta data to our systems.  Each component is built as stand-alone infrastructure, allowing us to audit and optimize intelligence on how each piece is performing.  We then leverage tools by Splunk to turn our massive log files into actionable intelligence, and we use TeamCity for continuous integration.  Even further behind the scenes we are using Nginx, Apache, load-balanced Amazon AWS & RDS, Robotium, Selenium, gh-unit, OCMock, KIF, Google App Engine and other best-in-class technologies. It all comes together on a 50" flatscreen monitor and 32" iMac that our Quality Assurance engineer monitors and all our employees can see.  We even have a flashing green light that turns red when a build breaks or we detect latencies in our system, and all our developers are notified when there's a problem. Here's a video of Sean describing the systems and how we use them to ensure Socialize is always available and performing flawlessly in your app: More pictures of our system: /td> /td>

Beating Someone at His Own Game

On Tynan

As babies we learn through imitation. We use our unrefined motor control skills to mimic what our parents do, and eventually with enough practice, most of us master the basics like eating and speaking.

The problem is that many people stay in this imitation phase for their whole lives, always having someone that they're trying to be, or at least copy. Maybe it's a cooler friend or maybe it's a celebrity.

What these people don't realize is that trying to copy someone is a fool's game, because it puts a ceiling on how good you can actually ever get. Take Steve Jobs, who I use as an example because he was a very distinct person whose qualities we're all familiar with. No one else will ever be Steve Jobs. You'll never hear the phrase, "He's like Steve Jobs, but even better."

Trying to become excellent AND copy someone else at the same time is like putting a Miro in the copy machine and expecting it to come out better than the original. It just doesn't happen. I don't know for sure why it's impossible to beat someone at their own game, but my guess is that it's because we can only really understand so much about someone from their actions. There's so much activity within their brains that we're not privy to. We see the tip of the iceberg, but sometimes we're trying to replicate 90% that's underwater just by looking at the visible portion.

Rendering New Theme...