InfoQ Homepage Architecture Content on InfoQ
-
Microservices Evolution at SoundCloud
At the MicroXchg conference in Berlin, Bora Tunca from SoundCloud presented the evolution of SoundCloud’s microservices architecture throughout the years. We had the opportunity to interview him and learn more about SoundCloud’s architecture evolution and microservices in general.
-
One API, Many Facades?
An interesting trend is emerging in the world of Web APIs, with various engineers and companies advocating for dedicated APIs for each consumer with particular needs. Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. You might need to optimize your API accordingly.
-
A Web for All: Accessibility and Inclusive Design
Accessibility allow everyone to have access to information and services. The goal is to provide those with disabilities the same opportunities as their normative counterparts. This article explores how accessibility does not have to be a painful, after the fact initiative, if products are designed with accessibility at the start using inclusive design.
-
Automate Deployment & Management of Docker Cloud/Virtual Java Microservices with DCHQ
This article demonstrates a solution for automating the build, deployment and management of a Docker Java microservices application on any cloud or virtualization platform. We extend an existing money transfer application consisting of event sourcing, CQRS and Docker, to run and manage this app on 13 different clouds and virtualization platforms.
-
Graph API in a Large Scale Environment
MyHeritage is a rapidly-growing destination used around the world to discover, preserve and share family histories. There is increasing demand for our services, accessed both internally and externally by our partners via the FamilyGraph API. Millions of API calls are made every day providing a huge challenge in terms of performance, scalability and security.
-
The Agility Challenge
To be successful, a company needs to become an agile enterprise. In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.
-
IAP: Fast, Versatile Alternative to HTTP
Jakob Jenkov's organization has analyzed the modern application stack, including high level architectures, concrete technologies like databases, query languages, messaging, distributed computing models, & network protocols, and constructed the next gen alternative to HTTP. IAP is the resulting emerging standard protocol, and ION the high speed alternative to JSON and Protocol Buffers.
-
A Reference Architecture for the Internet of Things
This is the first article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases. This first article will cover the definition of a more concrete and comprehensible architecture whereas the second part will then apply this architecture to actual use cases.
-
Microservices in the Real World
An interview with Alexander Heusingfeld and Tammo van Lessen about getting operations involved in architecture and dealing with "us vs. them" behavior when applying DevOps, how to use the Self-Contained Systems approach to modernize software systems, similarities and differences between Self-Contained Systems and microservices, improving deployment pipelines and using measurements in deployment.
-
From Monolith to Multilith at ticketea
ticketea is a large online ticket selling platform in Spain. This article describes their growing pains and how DevOps and an API-based distributed architecture allowed them to cope with growth, both from a technical (from monolith to multilith) and people (awareness and knowledge sharing) perspective.
-
Thinking Outside-In: How APIs Fulfill the Original Promise of Service-Oriented Architecture
The article explores how and why APIs are a lightweight and agile way of building reusable business systems. While some SOA adopters delivered these goals many efforts faced complexity and failed. The key difference with APIs is in the shift from hierarchical services to distributed resources, simplicity, statelessness and a focus on making it practical for the business to understand and implement