Keyboards are on fire: you’re cranking code for your new and awesome technology start-up. Nothing can stop you, not even this arbitrary limitation of 24 hours per day: your MVP is coming hot and heavy. You know exactly what you want to build, you even have your toolbox of choice handy, but there’s still a nagging doubt: should you build your MVP as a monolith or a set of distributed Read More...
If you’ve been following this blog, you’ve heard about our ongoing efforts to break our monolithic Rails application into smaller, more manageable pieces. You’ve also heard about our efforts around a better usage of the messaging features of the Amazon Web Services (AWS) cloud platform. These efforts are obviously linked: evolving towards an event-driven message-passing share-nothing architecture is our goal and we’re hard at work to make it happen. Why Read More...
In September 2013, the Reactive Manifesto was published and, quickly, software developers around the world started to add their signatures to endorse it. Unsurprisingly we all want to build better software, that is applications that behave gracefully when things are normal and also when the fan gets hit. The four main principles listed in the manifesto (represented in the diagram below) are not new but they are conveniently bound together Read More...