InfoQ Homepage Architecture Content on InfoQ
-
/articles/architect-agile-manifesto/en/smallimage/logo-1561702950808.jpg)
The Agile Manifesto: A Software Architect's Perspective
While the role and responsibilities of a software architect can be seen as contradictory to the values of the Manifesto for Agile Software Development, a good architect finds techniques that support an agile development team.
-
/articles/evolve-devops-devsecops/en/smallimage/How-to-Seamlessly-Evolve-DevOps-into-DevSecOps-logo-small-1561367768393.jpg)
How to Seamlessly Evolve DevOps into DevSecOps
As DevOps evolved, it became obvious that it was about more than just software development and operations management. With each new story of a massive data breach and its catastrophic consequences, cybersecurity swiftly became recognized as a critical part of any IT ecosystem. This realization led to DevSecOps. This article looks at how to embrace a DevSecOps approach.
-
/articles/book-review-scrum-spirit-game/en/smallimage/logo-1561370560291.jpg)
Q&A on A Scrum Book: The Spirit of the Game
In A Scrum Book: The Spirit of the Game, Jeff Sutherland and James Coplien explore how to do Scrum well using patterns. There are more than ninety patterns which provide insight into Scrum’s building blocks, how they work, and how highly effective teams use them.
-
/articles/obscuring-complexity/en/smallimage/obscuring-complexity-s-1560786483000.jpeg)
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.
-
/articles/openapi/en/smallimage/open-api-s-1560967631428.jpeg)
Using OpenAPI to Build Smart APIs for Dumb Machines
This article discusses how to build, manage and maintain APIs with OpenAPI, including some of the most notable features in v. 3.0.
-
/articles/ios-android-react-native-design-patterns/en/smallimage/ios-android-react-native-design-patterns-s-1560548191789.jpeg)
Five Android and iOS UI Design Guidelines for React Native
This article will explain why UI designers should follow platform specific guidelines while designing for multiple platforms. This can be quite a complex task, due to the variety of constraints and guidelines there are to consider. We propose five easy guidelines to design for multiple platforms focusing on React Native and without missing key usability concerns.
-
/articles/book-review-internal-tech-conferences/en/smallimage/book cover-s-1560258705887.jpg)
Q&A on the Book Internal Tech Conferences
The book Internal Tech Conferences by Victoria Morgan-Smith and Matthew Skelton is a practical guide on how to prepare, organise, and follow-up on internal tech conferences. It shows how to run internal events that enable sharing and learning across teams and departments, and explores the benefits that such events can bring.
-
/articles/cloud-transactions-dahan/en/smallimage/cloud-transactions-dahan-s-1559898649885.jpeg)
How Do We Think about Transactions in (Cloud) Messaging Systems? An Interview with Udi Dahan.
Do today's cloud-based messaging services have different transactional support than those that preceded it? If so, what are the implications? In this interview with distributed systems expert Udi Dahan, we explores the question.
-
/articles/correctness-versus-change/en/smallimage/Logo-1559817158528.jpg)
Correctness vs Change: Which Matters More?
In ongoing software development, our core work is changing code. Jessica Kerr argues that by building changeable software on top of existing, well-understood components, and by improving delivery automations, teams will get better at their core work of delivering value and "changing reality".
-
/articles/service-mesh-api-federating/en/smallimage/service-mesh-api-federating-s-1558080393545.jpeg)
Towards a Unified, Standard API for Consolidating Service Meshes
Service mesh architectures enable a control and observability loop. At the moment, service mesh implementations vary in regard to API and technology, and this shows no signs of slowing down. Building on top of volatile APIs can be hazardous. Here we suggest to use a simplified, workflow-friendly API to shield organization platform code from specific service-mesh implementation details.
-
/articles/application-integration-service-mesh/en/smallimage/role-application-integration-cloud-native-microservices-landscape-logo-small-1557478517420.jpg)
Application Integration for Microservices Architectures: A Service Mesh Is Not an ESB
A service mesh is only meant to be used as infrastructure for communication between services, and developers should not be building any business logic inside the service mesh. Other frameworks and libraries can be used to implement cloud native enterprise application integration patterns.
-
/articles/agile-anti-patterns-systems-thinking/en/smallimage/a-common-language-through-systems-thinking-logo-small-1557241618851.jpg)
Agile Anti-Patterns: A Systems Thinking Approach
Agile anti-patterns can disguise themselves as "solutions" or "workarounds". This article discusses the importance of recognising and classifying a new generation of agile anti-pattern with a systems thinking approach. It shows how to create and promote a shared language using value streams as an effective means of creating a systems thinking culture amongst agile teams and the wider business.