BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Scalability Content on InfoQ

  • Five Lessons Security Can Learn from DevOps

    Just as DevOps emerged to meet new business needs, new approaches in security are now needed to address the challenges of a DevOps-driven world. These new security approaches themselves must incorporate DevOps practices that rely on modularity, automation, standardization, auditability, and mirrored systems.

  • Book Review and Q&A - The Art of Scalability

    The Art of Scalability is a book on scaling organisations to adapt to web scale growth of their products and services. As well as having technical and architectural implications, scale needs to be dealt with on the organizational level. The goal is to show the reader how to organize technology, people and processes to result in a virtuous circle, a path of continuous improvement to scalability.

  • Storm Applied Review and Q&A with the Authors

    Storm is a distributed, fault-tolerant, real-time computation system that was originally developed at BackType and later open sourced by Twitter. Storm Applied is a new book from Manning that aims to provide a practical guide on using Storm, both in a development and in a production setting. InfoQ has spoken with two of the book’s authors, Sean T. Allen and Matthew Jankowski.

  • Jonas Bonér on Reactive Systems Anti-Patterns

    Taking the opportunity offered by the update to the Reactive Manifesto, InfoQ asked Jonas Bonér, TypeSafe CTO and original author of the first Reactive Manifesto, some questions about his vision of “Reactive” applications. Jonas offered his thoughts about both desirable features of reactive applications and what is not reactive programming.

  • Shift Left Performance Testing - a Different Approach

    This article will explain a different approach to traditional Multi User Performance testing; using the same tools but combine them with modern data visualisation techniques to gain early insight into location specific performance and application areas that may have "sleeping" performance issues.

  • Reliable Auto-Scaling using Feedback Control

    Philipp K. Janert explains how to reliably auto-scale systems using a reactive approach based on feedback control which provides a more accurate solution than deterministic or rule-based ones.

  • Interview: Adrian Cockcroft on High Availability, Best Practices, and Lessons Learned in the Cloud

    Netflix is a widely referenced case study for how to effectively operate a cloud application at scale. While their hyper-resilient approach may not be necessary at most organizations, Netflix has advanced the conversation about what it means to build modern systems. In this interview, InfoQ spoke with Adrian Cockcroft who is the Cloud Architect for the Netflix platform.

  • CAP Twelve Years Later: How the "Rules" Have Changed

    The CAP theorem asserts that any networked shared-data system can have only two of three desirable properties (Consistency, Availability and Partition Tolerance). In this IEEE article, author Eric Brewer discusses how designers can optimize consistency and availability by explicitly handling partitions, thereby achieving some trade-off of all three.

  • Finding the Right Data Solution for Your Application in the Data Storage Haystack

    With the recent NoSQL movement there are several alternative data storage solutions available compared to the traditional relational databases. In this article, author Srinath Perera discusses the various data storage options and what to consider when choosing each of these solutions.

  • Book Review and Excerpt: Scalability Rules

    Martin Abbott and Michael Fisher's book, Scalability Rules, is a compilation of 50 rules for scaling applications based on experience garnered at eBay, Intuit, PayPal, Etsy, Folica and Salesforce. The book is a handy reference for experienced and novice architects, managers, developers and operations personnel through a mix of heuristics and a priority-benefit model to rank the rules.

  • Large-Scale Agile Design & Architecture: Ways of Working

    During my 2011 QCon London keynote on "Scaling Lean & Agile: Large, Multisite or Offshore Delivery", I mentioned — as an aside — that, "Architecture is a bad metaphor. We don't construct our software like a building, we grow it like a garden." This prompted many a tweet, and some people were interested in clarification or elaboration.

  • Gregg Pollack and the How-To of Scaling Rails

    Ruby on Rails has done well since its introduction a few years ago but has taken some criticism for not being able to scale. Developers know there is always a right way and a wrong way to solve any problem and scaling Ruby on Rails is no different. Learn about what is being done to address Ruby on Rails and scaling to the enterprise.

BT