BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Enterprise Architecture Content on InfoQ

  • Q&A with Jason Fox on How to Lead a Quest

    In the book How to Lead a Quest Jason Fox explores what can be done to develop insights for strategic decisions and innovation, and for driving progress and delivering value. The book provides approaches and rituals for asking deeper, bigger questions and slow, thorough thinking, creating options and designing experiments for dealing with complexity, ambiguity and uncertainty.

  • Growing Agile… Not Scaling!

    What makes an agile team successful is not the “process” nor the “tools” but rather the way people develop an effective level of interaction with each other. Growing agile means both focusing on culture, and on co-evolution of practices and tools.

  • HTTP-RPC: A Lightweight Cross-Platform REST Framework

    HTTP-RPC is an open-source framework allowing developers to create and access cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles such as statelessness and uniform resource access.

  • Article Series: Cloud and "Lock-in"

    With the fast-pace of cloud changes (new services, providers entering and exiting), cloud lock-in remains a popular refrain. But what does it mean, and how can you ensure you're maximizing your cloud investment while keeping portability in mind?

  • Q&A with Johanna Rothman and Jutta Eckstein on Cost of Delay

    The book Diving For Hidden Treasures - Uncovering the Cost of Delay in Your Project Portfolio by Johanna Rothman and Jutta Eckstein explores how projects become delayed and provides tools and methods to analyze and limit the costs of delay in projects.

  • Everything Is “Lock-In”: Focus on Switching Costs

    Coding in Java, buying SAP, deploying OpenStack, and using Amazon Web Services: each one introduces a type of lock-in. However, it makes no difference how hard you try- some form of lock-in is unavoidable. What matters most is understanding the layers of lock-in, and how to assess and reduce your switching costs.

  • Locating Common Micro Service Performance Anti-Patterns

    In this second installment on diagnosing performance issues, performance engineer Andreas Grabner focuses on spotting patterns that cause performance and scalability issues in distributed Micro Service Oriented Architectures.

  • Production Like Performance Tests of Web-Services

    Tests should always keep the end user view in mind. But how to test web services, which are not directly customer-facing, and in particular, how to performance test them in a meaningful way? This article outlines performance split testing as a performance test approach that is relying on real-time production traffic.

  • Q&A on Achieving Impact through Engagement

    The book achieving impact through engagement by Si Alhir and and Peter L. Simon explores two models on employee and customer engagement: The Ownership Pyramid (TOP) and Artful Agility or Actions-Intentions-Results (AIR). Together these models can be used to achieve impact in organizations based on increasing engagement.

  • The Agility Challenge

    To be successful, a company needs to become an agile enterprise. In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.

  • From Monolith to Multilith at ticketea

    ticketea is a large online ticket selling platform in Spain. This article describes their growing pains and how DevOps and an API-based distributed architecture allowed them to cope with growth, both from a technical (from monolith to multilith) and people (awareness and knowledge sharing) perspective.

  • Thinking Outside-In: How APIs Fulfill the Original Promise of Service-Oriented Architecture

    The article explores how and why APIs are a lightweight and agile way of building reusable business systems. While some SOA adopters delivered these goals many efforts faced complexity and failed. The key difference with APIs is in the shift from hierarchical services to distributed resources, simplicity, statelessness and a focus on making it practical for the business to understand and implement

BT