• CoffeeScript
  • Node
  • Ruby
  • Python
  • Redis
  • Elasticsearch
  • Cloud computing


  • Responsive design
  • Elastic architecture
  • Stream processing
  • Continuous integration
  • Agile development

Open Source

  • Patchboard - Rich HTTP APIs and clients
  • Mutual - Remotable EventEmitter
  • Orca - High-fidelity load testing
  • Testify - Dead-simple tests
  • Pirate - Simple storage interface
  • KeyForge - Generate URL-safe keys
  • Alexandria - Cache Web content in ElasticSearch
  • Typely - Method overloading
  • Verse - Forward-looking CSS framework
  • Ark - Serve up bundled JavaScript


Today, application performance can mean many things.

An experience that feels quick and light.

A design that adapts naturally to tablet and mobile.

Features that are social … yet secure.

An architecture that helps you grow.

This is what we do.

A Seasoned Team

Our core team has decades of experience.

We've worked together for years.

We've successfully taken on a wide-variety of challenges.

We have a track record of succesful innovation.

We decided to start a company together.

And we named it … Panda Strike.

A Proven Approach

We love to innovate. But we also love results.

We have a progressive approach that works for us.

We think it will probably work well for you, too.

We'll be blogging more about this soon.

Innovative Technology

We're nerds, so we have to talk about technology!

We've tried to balance competing concerns.

For example, we love CoffeeScript because it's expressive—which results in more cost-effective development.

But also because it's easy for developers to learn.

We're … uh … kind of opinionated about this stuff.



  • HTTP Made Simple, Part 5

    A narrow passage running through the rock-hewn ruins of Petra. The desert city was possible due to clever use of dams, cisterns, and pipelines to capture and control water from flash floods.

    Here's what we've learned so far:

    • In part 1, we said that HTTP views the Internet as a big key-value store.
    • In part 2, we established that GET, PUT, and DELETE were the main methods, with POST acting as fallback for things that don't fit the key-value store model.
    • In part 3, we discussed how to discover and dynamically construct URLs to reduce coupling between client and server.
    • In part 4, we explored a flexible mechanism, known as content negotiation, that allows the client to choose their preferred content format.

    In this installment, we're going to look at how HTTP helps us optimize performance. After all, network requests are the considerably slower than reading and writing from disk or memory. We want to do everything we can to speed things up. As it turns out, HTTP can help us do that.One of the primary mechanisms HTTP provides for doing this is caching. It's a measure of how confused things have gotten that most of the search results for http caching concern turning caching off. And, indeed, we see this often at clients, due to the fact that, for historical reasons, browsers are very aggressive about caching HTML, CSS, JavaScript, and image assets. But that shouldn't discourage you from using HTTP caching for your APIs.

    Read more…

  • OpenSSL Heartbeat Vulnerability

    Heartbreak Hotel
    OpenSSL, you broke our hearts.

    The recently reported OpenSSL vulnerability is no joke. Although it was patched quickly, huge portions of the Web were, and in many cases, remain, vulnerable. Among other things, cloud providers must first update to the patched version and then their customers must get new certifications, since the old ones might well have been compromised. Finally, consumers must update their passwords on virtually their Web site accounts, but that's only really useful once everyone updates their certificates.

    But lurking quietly amidst the chaos is the proverbial elephant: should we be using OpenSSL at all?

    Read more…

See All Blog Posts