April 26th, 2013
Today we’re talking about our experience with btrfs, the next-gen Linux filesystem. btrfs has been maturing rapidly over the last few years and offers many compelling features for modern systems, so we’ve been putting it through its paces on some of our backup servers.
How does it stack up? Read on!
Posted in backup, btrfs, experiment, filesystems, Linux | Comments Off | permalink
April 25th, 2013
how assemble your pages from HTML partials on the client, front-end or CDN edge.
Posted in cdn, development, esi, front-end, javascript, nginx, ssi, web | Comments Off | permalink
April 25th, 2013
how assemble your pages from HTML partials on the client, front-end or CDN edge.
Posted in cdn, development, esi, front-end, javascript, nginx, ssi, web | Comments Off | permalink
April 25th, 2013
software estimates from psychology and human behavior point of view
Posted in development, estimates, psychology, software | Comments Off | permalink
April 25th, 2013
software estimates from psychology and human behavior point of view
Posted in development, estimates, psychology, software | Comments Off | permalink
April 14th, 2013
blog post about scale up and scale out, and hidden costs introduced by administration licensing costs for proprietary software. "Last monday we upgraded our core database server after a power outage knocked the site offline. I haven't touched this machine since 2005 so it was a major undertaking to do it last minute. We upgraded from a machine with 64 GB of ram and 8 CPUs to a HP ProLiant DL785 with 512 GB of ram and 32 CPUs ..."
Posted in design, engineering, scalability | Comments Off | permalink
April 14th, 2013
blog post about scale up and scale out, and hidden costs introduced by administration licensing costs for proprietary software. "Last monday we upgraded our core database server after a power outage knocked the site offline. I haven't touched this machine since 2005 so it was a major undertaking to do it last minute. We upgraded from a machine with 64 GB of ram and 8 CPUs to a HP ProLiant DL785 with 512 GB of ram and 32 CPUs ..."
Posted in design, engineering, scalability | Comments Off | permalink
April 14th, 2013
More often than not, the right tool for the job is piece of software that has been around for some time, with proven success. One example would be writing a backend service in Java or Python instead of Go or Node.JS. Another example would be storing data in MySQL or PostgreSQL instead of MongoDB or Riak.
Posted in development, engineering, technology, tools | Comments Off | permalink
April 14th, 2013
More often than not, the right tool for the job is piece of software that has been around for some time, with proven success. One example would be writing a backend service in Java or Python instead of Go or Node.JS. Another example would be storing data in MySQL or PostgreSQL instead of MongoDB or Riak.
Posted in development, engineering, technology, tools | Comments Off | permalink
April 14th, 2013
sometimes language makes a difference ( i.e ruby is too low for a service stack )
Posted in language, ror, ruby, scalability | Comments Off | permalink
