Yesterday someone was looking at my code and said “uh, you’re using +T in a generic”, and I said “that’s a hipster feature of Scala, you don’t need to understand it, you just need to get it right so your code compiles.”
In my previous post I installed and configured Ghost and WordPress. The purpose of that blog post was to test relative performance of the 2 platforms to see which one could handle more load. Many requested another test where an opcode cache was in place for WordPress. So that is exactly what this blog post is about.
After finishing up the major change of moving Voron to a Write Ahead Journal, it was time to actually start doing some performance testing. To make things interesting, I decided that we shouldn’t just compare this in isolation, but we should actually compare it to its peers.
We started working on a CloudStack backend for rOCCI using our CloudStack Ruby gem. The choice of rOCCI was made due to the existence of an existing Opennebula backend and the adoption of OCCI in the European Grid Initiative Federated cloud testbed.
There's been a lot of disagreement this week regarding Sarah Mei's notorious blog post on MongoDB. This new post takes Mei's original apart in a question-and-answer format, and takes a critical look at both the Diaspora team and the intention of Mei's blog title.
API Examples is an application pattern originally devised by Daniel Worthingon-Bodart, in which a new version of a producer application is accompanied by a sibling artifact that solely contains example API requests and example API responses.
If you'll recall from several posts ago, the author had been attempting to write a web application based around the concept of a simple recommendation engine and a software retailer. The implementation was being done using a Spring-based Java stack with Neo4j as the data store.
Rather than re-inventing the wheel, and to help provide perspective, we are now working with the folks from Docker. They will be giving us their feedback, helping with integration and creating a Go profile.
Starting with an overview of relational databases and the history of NoSQL as a concept, the author breaks NoSQL down into its core components and analyzes each, exploring history, purpose, advantages, disadvantages, and specific examples for each type of database.
By now, most developers are familiar with the various debugging tools in their local development environment, but as they step towards cloud deployments, how can they achieve the same? Is remote debugging even possible in the cloud? Well of course it is.
The author was pointed to Sarah Mei's blog post titled "Why You Should Never Use MongoDB," and thought he would comment from a RavenDB perspective. His summary: If you don't know how to tie your shoes, don't run.
Developers are driven when they can architect their own solutions to problems. Nobody wants to implement someone else’s idea, especially one they may disagree with. Give your engineers (even the junior guys) the ability to get a say into how something is designed.