InfoQ Homepage Agile Architecture Content on InfoQ
-
An Introduction to Structured Data at Etsy
Etsy recently published a blog post detailing how they store and manage structured data. The Etsy team make extensive use of taxonomies, and store the structured data with JSON files.
-
Eoin Woods on Democratising Software Architecture at ICSA 2019
Last month in ICSA 2019 in Hamburg, Germany, Eoin Woods, CTO at Endava, gave a speech about how we can democratise software architecture. Starting from a historical perspective, Woods described how software systems have evolved in the past three decades. In the 80’s we were all using monolithic architectures, which evolved into distributed monoliths in the next decade...
-
Reflecting on Top-Down or Bottom-Up System Design: Vaughn Vernon at MicroXchg Berlin
Should software design be driven by a top-down or bottom-up approach? Vaughn Vernon asked the question in his presentation at MicroXchg Berlin, where he discussed different approaches to software design, actor model, reactive domain-driven design and the importance of an emergent architecture.
-
Effectively Using Jira with an Overarching Vision
Dzmitry Hryb of Atlassian partner DevInit has recently published an article responding to a TechCrunch story that claimed using Jira's issue-centric model could result in a myopia, which misses the "macro-vision." Recent writing by architect Eltjo R. Poort and DevOps lead Matt Saunders also offers patterns for using Jira with other best-fit tools to capture vision and architectural direction.
-
Johanna Rothman – Scaling Agile Projects to Programs
In a presentation for OnAgile 2016, Johanna Rothman states that thinking small, and building upon the informal communication networks already at play in an organization, can help scale practices to manage large programs. Rothman provides advice on planning, architectural design, and measuring progress.
-
How Agile and Architecture Parted and Finally Became Friends
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
-
Stop Over-Engineering, Build What the Customer Really Needs
After working with many different teams, Greg Young has found that they often are drastically over-engineeringing in their projects. Teams start to work on 9 month projects, but by thinking on the problem from another perspective they may be able to deliver 95% of the value in just a few weeks, Young claimed in his keynote at the recent DDD eXchange conference in London.
-
Characteristics of Evolutionary Architectures
The first principle of Evolutionary architecture is support for incremental non-breaking changes. Microservices architecture is one great example of such an architecture, Rebecca Parsons and Neal Ford from Thoughtworks claims when describing characteristics and principles of Evolutionary architectures.
-
Microservices at Spotify
Kevin Goldsmith talked about how Spotify uses microservices to break down architectures and be innovative at the GOTO Berlin 2015 conference. He argues that Microservices are easier to test, deploy and monitor than monolithic applications. Spotify also aims to have as few as possible dependencies in their product, and microservices are very helpful for that.
-
Directing complex IT-landscapes with Agile
Where many organizations use agile to develop IT products, agile principles and practices can also be applied for maintaining landscapes of commercial products. Gert Florijn and Eelco Rommes will talk about directing complex IT-landscapes in public sectors such as healthcare and local and national government organizations at the Agile and Software Architecture Symposium 2015.
-
Steve Freeman on What's Wrong with Most TDD Implementations and Building on SOLID Foundations
At the Agile Singapore conference last year Steve Freeman spoke about the way TDD has been misinterpreted and frequently misapplied in many adoptions and how the SOLID architectural principles are still important, perhaps more important now than in the past.
-
An Introduction to Minimum Viable Architecture
This post describes the minimum viable architecture for developing minimum viable product. It includes the architecture specification in different phases of startup.
-
Death by Planning in Agile Adoption
Management can get the feeling of losing control when their enterprise adopts agile and starts deploying self-organizing teams. Procedures, review boards and consultation bodies can become superfluous when switching to an agile approach, but they may not realize that, says Marcel Heijmans. Trying to regain control with additional planning can make things worse, causing "death by planning".
-
Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
-
Implementing Hexagonal Architecture using Life Preserver and Spring Framework
Russ Miles recently shared some thoughts and ideas about the needs for adaptability in a system and how his implementation of the Hexagonal Architecture can help in achieving this. He used a Java and Spring based application to exemplify how such a system can be implemented.