BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Patterns Content on InfoQ

  • Anti-Patterns Working with Microservices

    The main problem with monolithic applications is that they are hard to scale, in terms of the application, but more importantly, in terms of the team. The main reason for a switch to microservices should be about teams, Tammer Saleh claimed at the recent QCon London conference when describing common microservices anti-patterns and solutions he has encountered.

  • Programming Patterns in Go

    Peter Bourgon has recently presented Successful Go Program Design, 6 Years On at QCon London 2016, discussing patterns to use or anti-patterns to avoid when programming in Go.

  • Azure Logic Apps Preview Refresh Released

    The Microsoft Integration Product team recently provided their first update since the Integration Roadmap that was released back on December 24th. On February 24th, 2016 Microsoft has announced the public preview of Logic Apps Preview Refresh.

  • A Pattern for API Backends Serving Frontends

    The web experience through a mobile device differs in many ways from a desktop version with its smaller screen, limited data plans and need for fewer requests. A mobile device also requires different data and may provide other interactions, e.g. with a bar code reader. One solution is to have one API backend for each type of client, a Backend For Frontend (BFF), Sam Newman explains in a blog post.

  • Microservices and Integration from an Enterprise Perspective

    Common misconceptions in large enterprises that Kim Clark meets are that microservices are fine grained WSDL operations or that APIs are microservices. A reason for this is that they are confusing interface granularity with component granularity, Clark claimed in a presentation at this year’s Microservices Conference in London.

  • 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.

  • Microsoft Azure Event Hubs Surpasses 1 Trillion Transactions in a Single Month

    The Microsoft Azure Event Hubs messaging service processed approximately 150 terabytes and 30 billion messages per day, or 375 000 messages per second, in June 2015, according to the Microsoft Azure Service Bus product team.

  • Ilan Goldstein on a Scrum Myth Buster Series

    This post covers scrum myths described by Ilan Goldstein, Certified Scrum Trainer.

  • A Critical Look at CQRS

    Looking at Command Query Responsibility Segregation (CQRS) in a larger architectural context there are other architectural styles available. There are database technologies solving the same problems but in a simpler way, Udi Dahan states looking into ways of approaching CQRS. There is also a way that fulfils a lot of the CQRS goals but with fewer moving parts when CQRS is really needed.

  • Eric Evans on DDD, Microservices and Boundaries

    There is tremendous value in microservices, probably giving us the best environment we have ever had for doing Domain-Driven Design (DDD), Eric Evans stated in his keynote at this year’s DDD Exchange conference in London. Iteration is the most important key to good design and microservices is the second attempt, after SOA, to get things right.

  • Introducing CQRS and Event Sourcing with a Demo Application

    Improving on his understanding of the architecture and patterns involved in Command Query Responsibility Segregation (CQRS), Sacha Barber has created a complete CQRS demo application including event sourcing and an article with a cross examination of the inner workings.

  • Introducing IODA Architecture

    For Ralf Westphal common architectural patterns like Layered architecture, Hexagonal architecture and Clean architecture all look very similar giving a very crude idea of the structure of an application. Looking for another way of describing architecture Westphal has defined an architectural style, IODA Architecture, built on three formal responsibilities: Operation, Data and Integration.

  • Mary Poppendieck Discusses Containers, Microservices and Contract Tests

    At Craft Conference 2015 in Budapest, Mary Poppendieck discussed the ‘new software development game’ and offered advice on how best to utilise containers, microservices and consumer-based contract tests to lower friction and limit risk within software systems.

  • Defining Classes of Service in Kanban Using an Alternative Approach

    There are some alternative ways of identifying different classes of service in kanban. This post talks about these methods.

  • Playing the Fearless Journey Game

    The Fearless Journey game, designed by Deborah Hartmann Preuss, builds upon the patterns described in the book Fearless Change. It is a game that teams can play to learn how to address obstacles over which they have no authority. Martin Heider and Holger Koschek facilitated a workshop where they talked about using patterns in change and played the Fearless Journey game.

BT