BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Design Content on InfoQ

  • Moving from a Monolithic to a Microservices Architecture

    Moving from a monolith to microservices the only value business stakeholders care about is reducing cost. It will not increase or protect revenue and neither scaling nor distribution are good reasons that will convince the business, Ian Cooper claimed in his presentation at this year’s Microservices Conference in London describing guidelines moving from a monolith to a microservices architecture.

  • Most Common Issues Caused by Mobile Fragmentation

    Device fragmentation can be a serious hindrance to providing great mobile user experiences. A review of the most common issues faced by developers.

  • Redux: An Architectural Style Inspired by Flux

    Redux uses a unidirectional data flow similar to Flux, but it has a single store which is changed by cloning the original store and applying some functions without side effects. There is no Dispatcher.

  • Human Refactoring: Applying Refactoring to Your Life

    Bryan Beecham gave a keynote about Human Refactoring at the Agile Testing Days 2015. InfoQ interviewed him about how Human Refactoring can help us to improve our lives, how it relates to refactoring code, why he considers eating healthy food to be important, how agile teams can benefit from human refactoring, and where people can find more information about self improvement and individual growth.

  • Rebuild or Refactor?

    Should you rebuilding or refactoring software?An interview with Wouter Lagerweij about what it is that makes refactoring so difficult, if rebuilding software is less risky than refactoring, and how continuous delivery fits with rebuilding software.

  • Getting Business Advantage from Continuous Delivery

    Gojko Adzic presented a keynote on "how to turn continuous delivery into competitive business advantage" at the Agile Tour London 2015. InfoQ interviewed Adzic about getting benefits from continuous delivery, Gojko's three rules of continuous delivery, possible problems and risks, and using multi versioning with continuous delivery.

  • Atomic: A UI Designer for Android, iOS and the Web

    Atomic is a user interface designer that runs in the browser. Without writing any code, application designers can use it to show how the interface of an application should look like and behave when certain commands are executed.

  • What is API Developer Experience and Why It Matters

    API developer experience is a relatively novel focus aimed to improve API design so it provides a seamless experience to developers when writing software. It can help increase programmers’ efficience and make it easier for developers to achieve goals on behalf of end users.

  • JAX London 2015 Round-Up

    JAX London 2015, which took place from 12th to 15th October at the Business Design Centre in London, United Kingdom, gathered many of the experts in the areas of Java, Microservices and other modern development practices. Although the topics were varied, the overall message seemed to indicate both that these technologies are maturing, and that users are learning to use them more effectively.

  • Domain Events and Eventual Consistency

    Eventual consistency is a design approach for improving scalability and performance. Domain events, a tactical element in Domain-Driven Design (DDD), can help in facilitating eventual consistency, Florin Preda and Mike Mogosanu writes in separate blog posts, each describing the advantages achievable.

  • Dino Esposito on CQRS, Messages and Events

    Command Query Responsibility Segregation (CQRS) is the starting point of a change that will have a profound impact on system architecture, Dino Esposito claims in three articles in MSDN Magazine. It’s the first step in an evolution transitioning software architects from the idea of “models-to-persist” to the idea of “events-to-log” and about event-based data instead of data snapshots.

  • Introducing DDD in a Project at “Which?”

    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.

  • Internet of Things Design Manifesto 1.0 Released

    IOT Design Manifesto 1.0 has been recently released. This manifesto serves as a code of conduct for everyone involved in developing the Internet of Things, outlining 10 principles to help create balanced and honest products in a burgeoning field with many unknowns.

  • Software – Is it "Engineering" Yet?

    At the GOTO Amsterdam 2015 conference Mary Shaw talked about progress towards an engineering discipline of software. She explored what it means to have an engineering discipline, how far we have progressed toward having one for software, and what can be the next steps.

  • 10 Common DDD Mistakes to Avoid

    Not interacting with domain experts is one of a common set of mistakes done when using Domain-Driven Design (DDD), finding and correcting them early on may save a team time, Daniel Whittaker claims describing ten mistakes he regularly see developers do.

BT