Deliveroo has grown dramatically the last years, both in terms of business and IT, and is facing a lot of technical challenges with its large monolithic application. The solution is to go distributed, but without microservices, Greg Beech noted in his presentation at the recent QCon London conference, describing their move from a monolith into a distributed system.
After failing with two proof of concept, mainly with scalability issues, when trying to renew their main website the business decided to take a more agile and incremental approach and in a restart of the project inspired by Domain-Driven Design (DDD) having developers talk with domain experts, Chris Patuzzo explains describing the principles of DDD in the context of a real project.
JRuby released version 9000, the ninth release of the popular implementation of Ruby for the Java Virtual Machine. InfoQ speaks to Charles Oliver Nutter co-lead of the JRuby project and senior engineer at Red Hat about the release and about Ruby in general.
In order to improve scalability, Parse moved part of their services, including their API, from Ruby on Rails to Go, Charity Majors, Engineer at Parse, recounts. In doing so, both their reliability and deployment times benefited greatly.
Chad Fowler, CTO at 6Wunderkinder, the company behind Wunderlist, describes how they went from a large monolithic Rails application and a large monolithic database to a system with many microservices, and the architecture they ended up with. Starting by adding new functionality as services and splitting the large database into smaller databases, they ended up doing a big rewrite of a new system.
TechEmpower has been running benchmarks for the last year, attempting to measure and compare the performance of web frameworks. For these benchmarks the term “framework” is used loosely including platforms and micro-frameworks.
Rails 4.1 can now preload your application to improve startup time and comes with improvements for Action Pack, Active Record, and Action Mailer.
Using your own public API can be a challenge, Phil Calcado, Director of Engineering at Soundcloud, declared when sharing his experiences managing and rebuilding a large Rails application in a talk at the GOTO Berlin Conference.
Over the past months, InfoQ published three research items on the current state of Ruby on Rails practice. Now the results are in and we're taking a look at what tools Rails developers currently use.
Ruby’s creator announced the move to generational garbage collection in Ruby 2.1 in what is expected to be an important performance boost for the language. The announcement took place during Barcelona Ruby Conference where Ruby’s GC was singled out as a major pain point in large scale Ruby deployments.
At the end of June 2013, Engine Yard announced that they had formed a partnership with Microsoft. The first fruits of that partnership have been released as developers can now run the full Engine Yard platform-as-a-service stack on the Windows Azure cloud. This, coupled with updates to the OSS VM Depot repository, positions Microsoft as a reasonable host for a variety of open source platforms.
InfoQ's research initiative continues with an 16th question about: "Ruby On Rails State of Practice: Testing". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
The new Ruby on Rails 4 release improves page speed with Turbolinks and makes caching easier. Support for Ruby 1.8 has been dropped and Ruby 2.0 is recommended.
A months old Ruby on Rails security flaw is now being exploited on systems where tardy patch deployment has left them vulnerable to malicious attackers.
InfoQ's research initiative continues with a 15th question about: "Ruby On Rails State of Practice: Deployment and Management". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.