InfoQ Homepage Enterprise Architecture Content on InfoQ
-
Introducing the KivaKit Framework
In this article, we take a brief tour of the KivaKit open source Java microservices application framework. KivaKit is a collection of mini-frameworks designed to work together. Each mini-framework is described in more detail at https://www.kivakit.org as well as on Jonathan Locke’s blog State of the Art.
-
Microservices — the Letter and the Spirit
Microservices to be a pattern of ‘decoupled services’ managed to get the best out of it (the underlying understanding of the pattern (‘small’ vs ‘decoupled’) forces developers to take certain design decisions that are consistent with these objectives. In this article discuss we will discuss well and poor implementations: ‘small-services’ vs ‘decoupled-services’ or ‘Letter’ vs the ‘Spirit’.
-
Faster Financial Software Development Using Low Code: Focusing on the Four Key Metrics
Low code/no code can help firms achieve the four key performance metrics described in the State of DevOps Reports and Accelerate, to achieve a faster pace of software development. Financial services especially stand to benefit from the trend of adopting low code/no code to drive digital transformation.
-
Reducing Cloud Infrastructure Complexity
Cloud computing adoption has taken the world by storm, and is accelerating unabated. According to Flexera’s annual State of the Cloud Report for 2020, 93% of respondents used multi or hybrid cloud strategies. This article examines different aspects of cloud infrastructure complexity, and approaches to mitigate it.
-
How to Not Lose Your Job to Low-Code Software
The uptake of low code software is so strong that it will almost certainly make its way into your organization. Most software engineers shouldn’t be concerned about this because they are good at the things that low code software is not yet good at. The key to surviving and thriving during this change is ensuring that your role encompasses responsibilities that low code can’t yet do.
-
How to Decide in Self-Managed Projects - a Lean Approach to Governance
Whether self-managed or self-governed as a project, the power still needs to be distributed internally. If the project is open to decide how things are done, how do we decide? A solid but flexible set of tools and practices like sociocracy is a great starting point for projects to have clear but lean processes that can grow as we grow.
-
Gamification: a Strategy for Enterprises to Enable Digital Product Practices
To embrace the changing needs of consumers, organizations are exploring new ways to ideate, collaborate and create products, some of them being embracing co-creation models, investment in long-term value, and fostering collective wisdom through gamification. This article shows how gamification helps to create perspective around product practices and bring us closer to next-generation products.
-
How Medical Companies are Innovating through Agile Practices
The adoption of Agile methods has been steadily growing in medical product companies over the past ten years. Practices vary from cloud-based continuous flow for data-intensive services to sprint-based for physical devices with embedded software. The question is no longer whether, but how Agile can work in medical product development - for our mix of technical, market, and regulatory constraints.
-
Ballerina Swan Lake: 10 Compelling Language Characteristics for Cloud Native Programming
The Ballerina language has come a long way with significant improvements since the 1.0 release in 2019. The latest Swan Lake release further simplifies building and deploying cloud native apps.
-
Service Mesh Ultimate Guide 2021 - Second Edition: Next Generation Microservices Development
Get up to speed on the adoption of service mesh. Learn how to deploy service mesh solutions in heterogeneous infrastructures and application/service connectivity.
-
Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh
This part 3 article in Cloud Native Architecture Adoption series, explores service interaction in a microservices based architecture, typical challenges we experience in distributed systems without proper governance, and how patterns like service orchestration and service mesh can help address those challenges.
-
Consistency, Coupling, and Complexity at the Edge
Successful use of a microservices architecture requires maintaining a clear separation of concerns in the various layers and by employing design principles best suited to each layer. While RESTful API design has become the standard for microservices, it can cause problems at the UI layer. Alternatives such as the Backend-for-Frontend pattern using GraphQL can provide better separation of concerns.