InfoQ Homepage SOA Content on InfoQ
-
The Future of DevOps is No-Code
The need for high-quality DevOps personnel is skyrocketing, but it is harder than ever to find enough staff. It is possible to augment your DevOps organization using no-code and low-code tooling. Low-code and no-code tools can free up existing developers by reducing the time spent on integrating and administering DevOps toolsets.
-
Build, Test, and Deploy Scalable REST APIs in Go
In this article, we'll look at how to use the gin framework to create a simple Go application. We will also learn how to use CircleCI, a continuous deployment tool, to automate testing and deployment.
-
Choosing the Right Cloud Infrastructure for Your SaaS Start-up
As a solutions architect, I have been designing SaaS applications for years and I have seen start-ups struggle to find the right cloud infrastructure and improve their product offering. These experiences prompted me to write this article as a tool to help companies make a pragmatic fact and data-driven decision.
-
Building Workflows with AWS Step Functions
AWS Step Functions use a state machine to represent the workflow. A workflow consists of a set of tasks, each of which represents a discrete activity to be performed. Each task is defined by a state of the state machine. In this article, we will learn about the main concepts of AWS Step Functions and apply those to build a workflow for a sample business process: Order Fulfillment.
-
The Implication of Feedback Loops for Value Streams
Lead time and throughput are dynamic variables which impact flow in a value stream. Capacity, processing time and feedback loops (such as error conditions) have a significant impact on WIP and flow and need to be mapped and measured when building value stream maps.
-
Business Systems Integration is about to Get a Whole Lot Easier
A new breed of integration software is arising that syncs business data into a simplified data hub and then syncs that data to the destination system. The benefit of this integration pattern is that it reduces the number of manual transformations required (often to zero) and makes it easier to write manual transformations when you have to.
-
How Development Teams Can Orchestrate Their Workflow with Pipelines as Code
Infrastructure as Code was just the beginning. Configuration as Code followed shortly after – again becoming extremely commonplace and enabling organisations to scale their engineering capacity by a number of times. And in order to continuously increase the value development teams generate, Pipelines as Code is the natural consequence.
-
DevOps and Cloud InfoQ Trends Report – June 2022
This article summarizes how we see the "cloud computing and DevOps" space in 2022, which focuses on fundamental infrastructure and operational patterns, the realization of patterns in technology frameworks, and the design processes and skills that a software architect or engineer must cultivate.
-
A Standardized, Specification-Driven API Lifecycle
At QCon Plus last November, Kin Lane, Chief Evangelist with Postman, and the Open Technologies Team lead presented on API specifications. API specifications are essential to him and at Postman. So he wanted to share a bit of how they see API specifications impacting how they produce and consume APIs.
-
Ballerina for Full-Stack Developers: a Guide to Creating Backend APIs
This article explores Ballerina’s intuitive syntax for writing REST APIs. We also discuss authentication, authorization, OpenAPI tool, observability, SQL/NoSQL client libraries, and key language features. At the end of this article, you will have a good understanding of why Ballerina is a prominent candidate for writing your next backend API.
-
Low-Code Tools Optimize Engineering Time for Internal Applications
Internal tools are critical pieces of software, often custom-built, and requiring significant developer bandwidth. Low-code platforms can optimize developer productivity, facilitate collaboration, and allow less technical employees to be more active in the development process.
-
Lightweight External Business Rules
Complex enterprise applications usually come with varying business logic. Such conditions and subsequent system actions, known as rules, are ever varying and demand involvement of domain specific knowledge more than technology and programming. The rules must reside outside the codebase, authored by people with core domain expertise with minimal tech knowledge.