InfoQ Homepage Enterprise Architecture Content on InfoQ
-
Why Developers and Staff+ Engineers Should Get Involved in Open-Source Collaborative Development
Over the last 30 years, the world has become connected and digital. Open source is how we do modern software development, stitching together downloaded open-source libraries, frameworks, and other code to create new applications or functionality. This is why every developer and senior staff+ roles need to know what open source is and how it works.
-
InfoQ DevOps and Cloud Trends Report – July 2023
InfoQ editorial staff and friends of InfoQ are discussing the current trends in the domain of cloud and DevOps as part of the process of creating our annual trends report. These reports provide InfoQ readers with a high-level overview of the topics to pay attention to and help the editorial team focus on innovative technologies.
-
In-Process Analytical Data Management with DuckDB
DuckDB is an open-source OLAP database for analytical data management that operates as an in-process database, avoiding data transfer overhead. Leveraging vectorized query processing and Morsel-Driven parallelism, the database optimizes performances and multi-core utilization for analytical data processing.
-
Using ASP.NET Core 7 Minimal APIs: Request Filters, Parameter Mapping, and More
Several features have been added to Minimal APIs with the .NET 7 release. This tutorial shows how they are now almost as powerful as traditional controller-based APIs while being far less verbose.
-
Step One to Successfully Building Your Platform: Building It Together
You may feel that investing in an internal platform is a win, but the business may need more convincing. This article covers how to frame your case in a way that the business can understand and support.
-
How to Have More Effective Conversations with Business Stakeholders About Software Architecture
Technical leaders must be able to communicate with business stakeholders to effectively design software solutions that meet the business needs and stay within an established cost threshold. Making architectural decisions requires understanding the desired quality attributes that will affect trade-off discussions between technical and non-technical stakeholders.
-
Moving Past Simple Incident Metrics: Courtney Nash on the VOID
The Verica Open Incident Database (VOID) is assembling publically available software-related incident reports. InfoQ talks with Courtney Nash about their recent findings including how MTT* metrics may not be beneficial, the average time to incident resolution, and the importance of studying near-miss reports.
-
Your Tech Stack Doesn’t Do What Everyone Needs It To. What Next?
Stack extensibility is an essential trait of well-designed IT ecosystems. Low-code BPA (Business Process Automation) has advantages that puts it at the forefront of approaches to stack extensibility. Learn how low-code software increases process resiliency by empowering business teams with an easy-to-use, easy-to-understand and, most of all, IT-sanctioned set of tools.
-
Accessing .NET gRPC Endpoints from Anywhere via JSON Transcoding
JSON transcoding is a feature that has been added to gRPC in .NET 7. It allows gRPC endpoints to be accessible via a REST API, and it's much easier to set up than any alternative technology available at the time of writing, such as gRPC-Gateway and gRPC-Web.
-
Moving to .NET 7 MSMQ Alternatives
No MSMQ support is available in the new versions of .NET; if it’s time to move, this article presents a few considerations on what that transition can look like. It will explore some of the available options. By the end, you should see that even though it may be tough, there is a pathway forward.
-
Colliding Communities, Cloud Native, and Telecommunications Standards
What happens when an ecosystem driven from the bottom up collides with a community characterized by top-down development? The 5g broadband cellular network standard by the 3rd Generation Partnership Project (3GPP), the Network Function Virtualization (NFV) standard by the European Telecommunications Standards Institute (ETSI), and the Service Function Chain RFC (request for comments) are examples.
-
Adopting Low Code/No Code: Six Fitnesses to Look for
When selecting a no-code/low-code platform, six key fitnesses should be examined: purpose fit, cost fit, ops fit, user fit, use-case fit, and organization fit. The IT team should be heavily involved in this decision as they play a pivotal role in helping citizen developers with platform adoption.