InfoQ Homepage Architecture Content on InfoQ
-
/articles/ballerina-api-gateway/en/smallimage/ballerina-1531766744426.jpg)
Building an API Gateway with the Ballerina Programming Language
An API Gateway is a layer in an architecture pattern that allows the business API to focus on the business functionality while taking care of the request dispatching, policy enforcement, protocol translations and analytics. This article is about how we built an API Gateway in Ballerina for the WSO2 API Manager.
-
/articles/adopting-new-tech-service-mesh/en/smallimage/adopting-new-tech-service-mesh-logo-1531154551611.jpg)
How to Adopt a New Technology: Advice from Buoyant on Utilising a Service Mesh
When adding a new technology like a service mesh into your production stack, be mindful of the impact this will have on you and your colleagues. Be clear about what problem you are solving, and define appropriate acceptance criteria. Run experiments that attempt to show how a service mesh can make life better for the various stakeholders.
-
/articles/people-reengineering-leadership-enablement/en/smallimage/logo-teams-1530280338958.jpeg)
People Re-Engineering How To’s: Leadership Enablement
There is no doubt that leadership is the management model that is now influencing the software industry, under the enormous challenges imposed by the Digital Transformation Age. People re-engineering elevates the value of leadership by taking “Leadership Enablement” as one of its basic threads, which brings vitality and vigor to a software organization.
-
/articles/service-mesh-promise-peril/en/smallimage/promisses-1529964874364.jpeg)
Service Mesh: Promise or Peril?
Service meshes such as Istio, Linkerd, and Cilium are gaining increased visibility as companies adopt microservice architectures. The arguments for a service mesh are compelling: full-stack observability, transparent security, systems resilience, and more. But is a service mesh really the right solution for you? This article examines when a service mesh makes sense and when it might not.
-
/articles/ios-application-design-patterns-review/en/smallimage/OBJC-1529812805554.jpg)
App Architecture, iOS Application Design Patterns in Swift Review and Author Q&A
App Architecture, iOS Application Design Patterns in Swift by Chris Eidhof, Matt Gallagher, and Florian Kugler presents a number of architectures for iOS Swift applications, from the ubiquitous Model-View-Controller to a few more experimental ones. The book is accompanied by a set of videos that are available as a separate purchase and add a live-coding dimension to the book content.
-
/articles/C4-architecture-model/en/smallimage/c4Model_Icon_sm-1529798065695.jpg)
The C4 Model for Software Architecture
Software architecture diagrams can be a very useful communication tool, but many teams have scaled back on the creation of diagrams, and when diagrams are created, they are often confusing and unclear. The C4 model consists of a hierarchical set of software architecture diagrams for context, containers, components, and code.
-
/articles/soa-microservices-journey/en/smallimage/SOA-to-Microservices-1529490054149.jpeg)
The SOA Journey: from Understanding Business to Agile Architecture
If your monolith is tightly coupled and not cohesive, you could split it in order for a business to be more agile. There are a lot of wrong ways that you can do that. They result in the same tightly coupled and non-cohesive monolith, but which is distributed across a network. This article examines how you can align your technical services and business-capabilities.
-
/articles/buzzfeed-microservices-migration/en/smallimage/BuzzFeed_Arrow-final-1528989561770.jpg)
How BuzzFeed Migrated from a Perl Monolith to Go and Python Microservices
Starting in 2016 BuzzFeed began a re-architecture project moving from a single monolithic application written in Perl to a set of microservices. The main reason for the move was that the Perl application was proving hard to scale, essential given that buzzfeed.com alone serves about 7 billion page views/month.
-
/articles/Can-People-Trust-Algorithm-Decisions/en/smallimage/logo-1529438072056.jpeg)
Can People Trust the Automated Decisions Made by Algorithms?
The use of automated decision making is increasing. These algorithms can produce results that are incomprehensible, or socially undesirable. How can we determine the safety of algorithms in devices if we cannot understand them? Public fears about the inability to foresee adverse consequences has impeded technologies such as nuclear energy and genetically modified crops.
-
/articles/istio-future-service-mesh/en/smallimage/Istio-Future-of-Service-Meshes-1529065924373.jpeg)
Istio and the Future of Service Meshes
A service mesh provides a transparent and language-independent way to flexibly and easily automate networking, security, and observation functions. This article examines the past, present and future of the Istio service mesh. The near-term goal is to launch Istio to 1.0, when the key features will all be in beta, including support for Hybrid environments.
-
/articles/democratizing-stream-processing-apache-kafka-ksql/en/smallimage/kafka-streaming-logo-2-1528901042755.jpg)
Democratizing Stream Processing with Apache Kafka and KSQL - Part 1
In this article, author Michael Noll discusses the stream processing with KSQL, the streaming SQL engine for Apache Kafka. Topics covered include challenges of stateful stream processing and how KSQL addresses them, and how KSQL helps to bridge the world of streams and databases through streams and tables.
-
/articles/tech-fragmentation-future-of-work/en/smallimage/logo-how-technology-smal-llogo-1528807242487.jpg)
How Technology Is Impacting the Future of Work through Fragmentation
One of the side effects of technology’s evolution is that it fragments existing architectures and creates new structures in the process. AI and Blockchain are currently doing this, but this pattern has been seen before and will continue as tech evolves. According to Kary Bheemaiah, fragmentation is impacting the future of work; it’s a tech-lead reality to be observed and leveraged when possible.