InfoQ Homepage Design Content on InfoQ
-
Design and Security in Agile: QCon London Q&A
Reviews of design diagrams by domain experts can detect potential security breaches not found by vulnerability scans or security automation. Such reviews should focus on critical functions like issuing and managing access tokens, transferring data to external services, and running untrusted code, said Kevin Gilpin, enterprise software engineer and co-founder of AppLand, at QCon London 2019.
-
Bruck: Quick Interface Layout Prototyping
Bruck is a new lo-fi prototyping system targeted at web designers that enables them to quickly build responsive, accessible layout prototypes for clients. Designers may prototype a large variety of layouts by composing up to 25 web components. Designers may additionally visualize in real time the composed layout in Bruck's online interactive playground.
-
Netflix Play API: Building an Evolutionary Architecture
At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.
-
InfoQ's New Desktop Design Launched
We've made a number of changes to InfoQ's desktop site, the third major overhaul of our design since we got started in 2006. You can switch to the new design now to try it out.
-
Jeff Patton on Fixing Agile Product Ownership
At the recent Agile India conference, Jeff Patton gave a keynote talk in which he challenged the way agile development approaches Product Ownership. He holds that product management is a discipline which was around before the Scrum term Product Owner was coined, and the way it has been applied in most agile organisations is, at best, a watered-down approach and real product management is needed.
-
Alan Cooper on Working Backwards for Better Product Design
At the Agile India conference, design expert Alan Cooper gave a keynote talk on Working Backwards in which he described an approach to design and innovation centered on three key elements: know your user and their goals, see possible solutions, and see the big picture.
-
Vaughn Vernon Uses Reactive DDD to Model Uncertainty in Microservices
Microservices and reactive systems bring with them uncertainty about messages arriving out of order, multiple times, or not at all. How to react to such uncertainty is a business decision, says Vaughn Vernon, and is best captured by modeling the uncertainty using concepts of Domain-Driven Design.
-
Relearning Functional Service Design for Microservices: Uwe Friedrichsen at microXchg
The opening talk of the microXchg microservices conference was delivered by Uwe Friedrichsen, and discussed “Resilient Functional Service Design”. Key takeaways included: microservice developers should learn about fault tolerant design patterns and caching; understanding Domain-Driven Design (DDD) and modularity is vital; and aim for replaceability of components rather than reuse.
-
The Future of Microservices: Functional Service Design and Observability
In preparation for the upcoming microXchg conference, running 16th and 17th February in Berlin, InfoQ sat down with Uwe Friedrichsen and Adrian Cole and discussed functional service design, the new challenges with observing a distributed system, and what the future holds for the microservice architectural style.
-
How GitHub Designed its New Load Balancer
GitHub has been at work for the last year to develop a new load balancer, the GitHub Load Balancer (GLB), aimed to be able to scale to billions of connections per day running on commodity hardware. GitHub engineers Joe Williams and Theo Julienne explain how GLB was designed.
-
How Agile and Architecture Parted and Finally Became Friends
People stopped seeing the need to define the architecture or do software design due to incorrect interpretation of the agile manifesto, argued Simon Brown. Many software developers don’t seem to have a sufficient toolbox of practices and the software industry lacks a common vocabulary for architecture. A good architecture enables agility with just enough up front design to create firm foundations.
-
Experiences with Behaviour-Driven Development
Behaviour-Driven Development (BDD) recognizes that software development is fundamental to businesses of today and helps to improve how business stakeholders and software developers communicate with each other, Kevin Smith claims in a recent blog post about his experiences working with BDD.
-
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.
-
How to Effectively Debug Software
InfoQ interviewed Diomidis Spinellis, author of the books Code Reading and Code Quality, about finding and fixing errors in software, principles for debugging software and how to improve the effectiveness of debugging, how to write code that requires less debugging, and what managers can do to support error prevention and handling.
-
Collision: Online Harassment and Machine Learning
Online harassment is a serious issue, one that the engineers and designers behind the keyboard don't always think about when building software. Machine learning is become more prevalent but as more technology companies take advantage of it, they risk alienating their users even more by presenting content that isn't actually relevant.