InfoQ Homepage Enterprise Architecture Content on InfoQ
-
In Defence of the Monolith, Part 1
In the age of microservices, "monolith" has become a dirty word. Yet, monoliths, designed with an emphasis on modularity, can be a better solution for complex domains, such as enterprise applications. Part 1 of this 2-part series explores the key differences between microservices and monoliths, highlighting the pros and cons of each approach.
-
Q&A with Immuta on the Implications of EU’s General Data Protection Regulation (GDPR)
InfoQ talked with Immuta’s Andrew Burt and Steve Touw, to better understand the implications and challenges of the EU's Global Data Protection Regulation, which will come into effect in May 2018.
-
The Misaligned Middle and Getting off the Hamster Wheel Using Kanban
At the Agile 2016 conference, Dominica DeGrandis and Julia Wester of Leankit gave talks on helping middle managers adapt to change and how Kanban can be used to identify problems in workflows, which people need to address.
-
How Difficult Can It Be to Integrate Software Development Tools? The Hard Truth
Integrating tools used in software development and delivery is very hard. Getting endpoints to inter-operate is not a purely technical challenge, it’s more of a business problem. While there are a few choices in selecting the technical integration infrastructure (integration via APIs or at the database layer), the real challenges have more to do with friction caused by the dissimilarities.
-
Harnessing the Power of Architectural Design Principles
Architecture principles epitomize architecture's function: to clearly define the necessary constraints on a system's design without prescriptively defining all the design details. A good set of principles can provide context and justification for design decisions and can foster team collaboration and communication.
-
Ultimate Kanban: Scaling Agile without Frameworks at Ultimate Software
Ultimate Software settled on Kanban as its scaled methodology which went hand-in-hand with the company’s culture of autonomy. Teams define their own process and apply policies specific to their own context. Through the innovative use of flow practices and principles, Ultimate has been able to achieve many of the benefits of a Lean-Agile implementation without the use of a heavyweight framework.
-
An Open API Initiative Update
The Open API Initiative group is evolving what has become the de-facto standard API Description Format to produce a consistent and compatible format for describing APIs, allowing interoperation between tooling, systems, and runtime environments. Tony Tam, creator of the popular Swagger Specification is providing an update on the group activity.
-
CQRS for Enterprise Web Development: What's in it for Business?
With a focus on the business case for a CQRS architecture, this article covers the core concepts of Command Query Responsibility Segregation, and contrasts them with a common, n-tier architecture. Benefits including scalability and maintainability are highlighted, which can reduce the total cost of ownership, and lead to an improved return on investment when choosing a CQRS architecture.
-
Q&A and Book Review on Liftoff, Second Edition
The book Liftoff, Second Edition by Diana Larsen and Ainsley Nies, provides practices and insights for chartering teams by understanding their needs, building trust, and defining how they will interact in the team and align with other parts of the organization. It's a book for Agile coaches, Scrum masters or agile product and project managers to help teams to understand the why behind the work.
-
Two Mistakes You Need to Avoid When Integrating Services
With SOA, businesses moved from monolithic applications to heterogeneous designs by decomposing functionality into services. However, architects must be careful when integrating services. Often enterprises assume adopting patterns like ESB can help. Unfortunately, there are hidden challenges with these patterns. The danger is they go unnoticed during development but surface when a system is live.
-
Using Templates to Transform Web Service Results into Markup
The HTTP-RPC open-source Java framework returns results in JSON by default, but can use the CTemplate system to respond with custom markup. In this article, Greg Brown shows how simple annotations can be used to automatically respond to a web service in any markup (HTML, XML, CSV, etc.).
-
Creating RESTful Services with T4 Based on Model and Interfaces
When generating RESTful services with WebAPI, a lot of boilerplate code has to be implemented. Amel Musić demonstrates how T4 and EnvDTE can be used to create a flexible code generator that dramatically reduces the amount of time and effort this takes.