InfoQ Homepage Architecture Content on InfoQ
-
Calculating the Operations Cost of Software You Haven't Developed: Q&A with John Davis from easyJet
At the DevOps Enterprise Summit, John Davis, lead architect at EasyJet, will present “Calculating the Operations Cost of Software You Haven't Developed”. InfoQ sat down with Davis to discuss how traditional organisations can migrate to a more collaborative “DevOps”-enabled approach for implementing IT projects, and how project management and costing will change.
-
The Economics of Microservices: Phil Calçado Recommends Avoiding ‘Microliths’ at CraftConf
At CraftConf 2017 Phil Calçado presented “The Economics of Microservices”. The key takeaway from the talk: the ‘Inverse Conway Maneuver’ can be a useful tool to shape an application’s architecture during a migration away from a monolith, but this can lead to creating ‘microliths’ unless the ‘transaction cost’ of creating a new service is lowered to below the cost of adding to an existing monolith.
-
Nikita Ivanov on Apache Ignite In-Memory Computing Platform
Apache Ignite is an in-memory computing platform with transactional support, that supports both key-value persistence as well as streaming and complex-event processing. Ignite was open-sourced by GridGain in late 2014 and accepted in the Apache Incubator program. InfoQ interviewed Nikita Ivanov, CTO of GridGain, to find out more about Apache Ignite.
-
A Crystal Ball to Prioritise Technical Debt in Monoliths or Microservices: Adam Tornhill's Thoughts
At QCon London, Adam Tornhill presented “A Crystal Ball to Prioritise Technical Debt”, and claimed that although the technical debt metaphor has taken the software world with storm, most organizations find it hard to prioritise and repay their technical debt. Key takeaways from the talk included methods to identify ‘hotspots’ of code complexity and churn.
-
From Microliths to Microsystems: Jonas Bonér at QCon London
At QCon London, Jonas Bonér, CTO at Lightbend, presented “From Microliths to Microsystems”, and explored microservices from first principles, and discussing the architectural style in the context of distributed systems. Key takeaways included: avoid building ‘microliths’, and instead create systems that are resilient and elastic; and practice events-first Domain-Driven Design (DDD).
-
MicroProfile Becomes Eclipse MicroProfile
MicroProfile, the community initiative to provide a microservices standard for enterprise Java, has joined the Eclipse Foundation. The move is aimed at ensuring that MicroProfile remains a vendor-neutral project, and hopes to leverage the resources and momentum of the Eclipse Foundation. The decision has caused some arguments and temporarily diverted efforts from other objectives.
-
The AWS Well-Architected Framework Adds Operational Excellence
Amazon has updated their AWS Well-Architected Framework (PDF) based on feedback from clients, adding a new pillar, Operational Excellence.
-
Grow with Conway’s Law, Not against It
Jason Goth, Micah Blalock, and Patricia Anderson of Credera explained at SpringOne how they used Conway's law to tailor a client's technical architecture and processes to reverse falling productivity and accelerate the production of high-quality code.
-
Service-Based Architecture as an Alternative to Microservice Architecture
ThoughtWorks director Neal Ford argued in a recent talk that organizations transition more easily from a monolithic architecture to a service-based architecture than to a microservices architecture. Ford spoke at UberConf 2016 about service-based architecture, a middle ground between service-oriented architecture and microservices.
-
Keeping Systems "Poised for Change" with Evolutionary Architecture
At the Agile on the Beach 2016 conference, held in Cornwall, UK, Rebecca Parsons argued that the requirements for improved time-to-market and increased business agility can be achieved by architecting software for real evolvability, keeping systems poised for change, lowering the cost (and risk) of experimentation, maximising visibility and feedback, and aligning the organisation.
-
Building a Scalable Minimum Viable Product
Scalability should be considered when developing a Minimum Viable Product (MVP). An MVP needs to be technically scalable and you need to have a plan on how to scale quickly when your MVP attracts many users and becomes successful. Knowing your possible performance bottlenecks and using common sense while developing your MVP will get you very far, says Erik Duindam, CTO at Unboxd.
-
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.
-
Microservices Imply a Distributed System
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
-
A Sample Serverless Microservice Architecture from Autodesk
In the webcast entitled "What's Better Than Microservices? Serverless Microservices," Alan Williams (Autodesk), Asha Chakrabarty (Amazon) and Alan Ho (Apigee) discuss the architecture of a serverless microservice built with lambda functions with Apigee end-points running on AWS.
-
How and Why Etsy Moved to an API-First Architecture
At QCon New York 2016, Etsy software engineer Stefanie Schirmer told how her company successfully transitioned to an API-first architecture that supports multiple devices, addresses server-side performance problems, and was quickly adopted by development teams.