InfoQ Homepage SOA Content on InfoQ
-
The Excel Formula Language Is Now Turing-Complete
The Excel team announced LAMBDA, a new feature that lets users define and name formula functions. LAMBDA functions admit parameters, can call other LAMBDA functions and recursively call themselves. With LAMBDA, the Excel formula language is Turing-complete: user-defined functions can thus compute anything without resorting to imperative languages (e.g., VBA, JavaScript).
-
Benefits of Loosely Coupled Deep Learning Serving
As deep networks are becoming more specialized and resource-hungry, serving such networks on acceleration hardware in tight-budget environments is also becoming difficult. Instead of using API frameworks, loosely coupled components can be preferred as an alternative. They bring high controllability, easy adaptability, transparent observability, and cost-effectiveness when serving deep networks.
-
Microsoft's Low-Code Strategy Paints a Target on UIPath and the Other RPA Companies
Microsoft is investing big in the low code space and has put together a collection of products that is hard for other companies to match, capped recently by the announcement of PowerFX. The target in their sights is the Robotic Process Automation (RPA) companies such as UIPath, Automation Anywhere and Blue Prism who are closing big deals with big enterprises.
-
GraphQL Reference Guide: Building Flexible and Understandable APIs
This online guide aims to answer pertinent questions for software architects and tech leaders, such as: Why would you use GraphQL? Why should you pay attention to GraphQL now? How can GraphQL help with data modelling in the Enterprise?
-
Low-Code Platforms and the Rise of the Community Developer: Lots of Solutions, or Lots of Problems?
Low-code platforms are the hottest enterprise software category right now. With the current level of investment, it is hard to imagine a future that doesn’t feature lots of bespoke business apps being built by non-IT staff for use by their teams. Visibility of low code solutions is the key to managing risk.
-
How Apache Pulsar is Helping Iterable Scale its Customer Engagement Platform
In this article, author Greg Methvin discusses his experience implementing a distributed messaging platform based on Apache Pulsar.
-
Using a DDD Approach for Validating Business Rules
If the goal is to create software applications that emulate the behavior of domain experts, then the challenge is in capturing and implementing the business rules. This is more a factor of good knowledge management than it is raw coding ability. Following techniques from Domain-Driven Design can provide a structure for effectively validating and implementing business rules in a system.
-
Software Architecture and Design InfoQ Trends Report—April 2020
An overview of how the InfoQ editorial team sees the Software Architecture and Design topic evolving in 2020, with a focus on fundamental architectural patterns, framework usage, and design skills.
-
Enterprise API Management: Q&A with Book Author Luis Weir
In the Enterprise API Management book, Luis Weir provides technology-agnostic strategies that organizations can implement to drive more predictable outcomes. The topics that Weir covers in this book include the Business Value of APIs, Business-Led API Strategy, API-Led Architectures, API-Architecture Styles, API Life Cycle and more.
-
SLOs Are the API for Your Engineering Team
SLOs provide a simple common language for evaluating risk in terms of error budgets. SLOs save everyone involved both time and energy, which you can redirect toward more important things, like keeping your customers happy.
-
Waste Not, Want Not: A Simplified Value Stream Map for Uncovering Waste
This article describes a simplified form of Value Stream Maps that makes it easy to visualize bottlenecks and inefficient processes in the software delivery lifecycle. It focuses on the two forms of Lean waste defined as Inventory and Waiting.
-
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.