InfoQ Homepage Enterprise Architecture Content on InfoQ
-
The Seven Steps to Building a Successful Software Development Company
Building a successful software development company is hard. There are lots of challenges and barriers that need to be overcome. This article provides seven things that can help start on the right footing and keep on track for success. Build the right team, have a clear focus, leverage partnerships, nurture and protect your culture, identify and leverage new technologies and look to the finances
-
Six Pointers for Creating Strong Operational Business Values
A system that is flexible and open to inputs works for organizations of all sizes. This article is a rulebook for leaders on how to create a values-driven culture that not only lifts a new business off the ground, but also keeps it going in the long run, by encouraging creativity, an ownership mentality, honesty in feedback, and open communication across the board.
-
Perspective on Architectural Fitness of Microservices
In this article we peel the onion of potential architectural fitness of microservices in the context of Master Data Management, and the challenges a microservices-based architecture may face when solving problem domains that require compute-intensive tasks, such as the calculation of expected losses on a portfolio of unsecured consumer credit.
-
Building a Blockchain PoC in Ten Minutes Using Hyperledger Composer
This article examines what businesses look for when considering blockchain’s role in their organization and how the Linux Foundation's Hyperledger Composer can help application developers easily create compelling blockchain solutions for the enterprise.
-
Know the Flow! Microservices and Event Choreographies
This article explores ways to implement services which are long running and stretch across the boundary of individual microservices using event based architectures.
-
Q&A on the Book Sense and Respond
The book Sense and Respond provides ideas for executives, managers and business line leaders to leverage the power of technology to build more successful businesses. Authors Jeff Gothelf and Joshua Seiden explain how you can use experimentation and learning and continuous market feedback to deliver valuable products to customers, and manage teams on outcomes and foster effective collaboration.
-
Q&A on the Book Agile Enterprise
In the book Agile Enterprise, Mario Moreira explores the end-to-end and top-to-bottom view needed to run an effective agile enterprise, focusing on the needs of customers and employees. He explains how cutting-edge and innovative concepts and practices can be incorporated into a robust agile and customer value-driven framework.
-
Q&A on the Book It's All Upside Down
In the book It's all Upside Down, Paul McMahon provides stories from software development teams supported by upside down principles and coaching tips for applying them. He explains how you can use Essence to improve processes leading to better organizational performance.
-
Culture May Eat Agile for Breakfast
Making culture your priority during the scaling phase of your organization is a sound business decision. You have to invest by hiring for mindset and educating everyone joining the organization in agile principles to prevent turning an existing agile culture into a traditional one.
-
Q&A with Ash Maurya on Scaling Lean
In the book Scaling Lean, Ash Maurya explores how entrepreneurs can collaborate with stakeholders to establish a business model for a new product or service using Lean Startup principles. It builds on top of his first book, Running Lean, showing how to use experiments, measure business progress, and scale your startup.
-
Always Be Publishing: Continuous Integration & Collaboration in Code Repositories for REST API Docs
API documentation is an often overlooked part of making any API a success. This article explores how to make the documentation part of a continuous integration pipeline keeping it closer to the code itself.
-
Does IT Industry Need Better Namings?
The IT industry borrows terms from other domains, which is a fairly good approach. But we distort their meanings or use terms in inconsistent ways, within IT and also in comparison to other disciplines. This article shares some of these leaky terminologies with examples, explains why this matters and suggests how to deal with inconsistencies and improve the situation.