InfoQ Homepage Architecture Content on InfoQ
-
Design for Continuous Evolution: Immutable Model Is Key for Robustness
At QCon New York, Eric Brewer described how advancing from continuous delivery to fast and stable continuous evolution requires a discrete construction step to define an immutable model of the system. Brewer’s compute infrastructure design team uses Helm to construct and safely validate new deployment models, prior to attempting real deployment, although the concepts are technology agnostic.
-
Juval Löwy: Why Every Class Should Be a Service
Juval Löwy has pioneered a method of building service-oriented applications in which each class represents a service onto itself. While these applications may initially seem like 'class explosion', they are actually the product of a truly decomposed system; one that has been properly analyzed and designed. Juwal explains his intent and describes how development teams can improve from this process.
-
Stop Over-Engineering, Build What the Customer Really Needs
After working with many different teams, Greg Young has found that they often are drastically over-engineeringing in their projects. Teams start to work on 9 month projects, but by thinking on the problem from another perspective they may be able to deliver 95% of the value in just a few weeks, Young claimed in his keynote at the recent DDD eXchange conference in London.
-
FaaS, PaaS, and the Benefits of the Serverless Architecture
This article discusses what serverless is, comparing it with PaaS and SPaaS, the benefits and costs of a serverless architecture and the need for a framework.
-
Key Takeaways from the O’Reilly Software Architecture Conference: Day Two
This article presents a review of the second day at the O'Reilly Software Architecture conference, held in New York City 12-13th April. Sessions covered include 'Evolving toward microservices: How HomeDepot.com made the transition’, ‘Going cloud native: It takes a platform’, ‘Let's make the pain visible’, ‘Microservices in reverse’, and ‘The architect as coach’.
-
Lessons Learned at the O’Reilly Software Architecture Conference: Day One
This article presents a review of the first day at the O'Reilly Software Architecture conference, held in New York City 12-13th April. Sessions summarised include, ‘blah, blah... microservices...blah, blah’, ‘the evolution of evolutionary architecture’, ‘Death Star Security’, ‘Twelve Patterns for Hypermedia Architecture’, ‘Architecture Without an End State’ and 'Leading Simplicity'.
-
"Wait, What!? Our Microservices Have Actual Human Users?" The Importance of UI Architecture
At the microXchg conference, Stefan Tilkov presented “Wait, what? Our microservices have actual human users?”. Tilkov proposed that current microservice discussions tend to be centered around backend topics. The presentation argued that it is of paramount importance to increase focus on how to structure what is arguably the most important part of a microservice application - the UI.
-
Using Microservices in the Internet of Things
In this interview Fred George explains how the internet of things can exploit microservices and the challenges that the Internet of Things is posing and how to deal with them. InfoQ also asked him for advice for the software industry regarding the usage of microservices for the Internet of Things.
-
Microservices, DevOps and PaaS - The Impact on Modern Java EE Architecture
InfoQ sat down with Markus Eisele, developer advocate at Red Hat, at the Devoxx BE conference, and asked about his thoughts on implementing microservice architectures within large-scale enterprise organisations. The conversation was primarily based on his recent O'Reilly mini-book publication, “Modern Java EE Design Patterns: Building Scalable Architecture for Sustainable Enterprise Development".
-
Redux: An Architectural Style Inspired by Flux
Redux uses a unidirectional data flow similar to Flux, but it has a single store which is changed by cloning the original store and applying some functions without side effects. There is no Dispatcher.
-
The AWS Well-Architected Framework
Amazon has published the AWS Well-Architected Framework, a guide for architecting solutions for AWS, with design principles that apply to systems running on AWS or other clouds.
-
Big Data Architecture: Push, Pull, or Search in Place?
A surprisingly common theme at the Splunk Conference is the architectural question, “Should I push, pull, or search in place?”
-
Key Takeaways from the 'Agile on the Beach' Conference: Day One
At the fifth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key messages included the need for the more rigorous use of the scientific method throughout the software delivery lifecycle, and the benefits provided by applying agile principles to product development.
-
Building Microservices with Go and ‘Go kit’: Peter Bourgon Q&A
At the Golang UK Conference, Peter Bourgon introduced ‘Go kit’, an open source microservice toolkit that can be used to facilitate and standardise the creation of Go-based services within the modern enterprise application stack.
-
10 Properties Defining Software Architecture
Software architecture is a process; a sequence of strategic design decisions mapping specification and business goals to architecture design, and a thing; a set of views produced by the process that address different stakeholders, Michael Stal states describing how to define a software architecture.