InfoQ Homepage Architecture Content on InfoQ
-
Updated Principles of Service Orientation
Our understanding of SOA has changed over the last 15 years including new aspects such as Service Execution Context and a re-defined notion of the Service Contract. This paper reviews and updates the Principles of Service Orientation based on the first OASIS SOA RAF standard bridging the gap between business and technology and eliminating technology-specific wording in their formulation.
-
Is Bitcoin a Decentralized Currency?
Bitcoin currency model is getting more attention than any other digital currency proposed to date. In this article, authors analyze Bitcoin's decentralized model and discuss possible solutions to enhance its decentralization.
-
Measuring and Improving Software Development Productivity
The book Improving Software Development Productivity contains practices, models and case studies to quantitatively support adoption of agile software development. An interview with Randall Jensen about measuring and improving productivity, contribution of agile to productivity, benefits from pair programming and teams, knowledge retention in maintenance and commandments for communication.
-
Personal UX -- Solving Unique Problems Created by Widespread Global Mobilization
Smartphone users are estimated to number 3.5 billion by 2019, and the different usages (mobile is most common during morning commutes and late at night, for example) create new challenges and opportunities. Data collection via our devices, smart-home gadgets and even our cars allows software engineers to offer increasingly personalized user experiences.
-
How SOA Governance (and SOA Management) Should Actually Be Done
Ganesh Prasad proposes separating governance and management in large SOA projects to make sure that right dependencies are used throughout the system in order to promote agility, lower operating costs and reduced operational risks.
-
Q&A about the book Common System and Software Testing Pitfalls
The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.
-
Sam Newman: Practical Implications of Microservices in 14 Tips
What are the practical concerns associated with running microservice systems? And what you need to know to embrace the power of smaller services without making things too hard? At last GeeCon 2014 in Krakow, Sam Newman tried to answer those questions by giving 14 tips about how microservices can interface, how the can be monitored, deployed, and made safer.
-
Analytics Across the Enterprise: How IBM Realizes Business Value from Big Data and Analytics
Analytics Across the Enterprise: How IBM Realizes Business Value from Big Data and Analytics book by Brenda L. Dietrich, Emily C. Plachy, and Maureen F. Norton is a collection of experiences by analytics practitioners in IBM. InfoQ spoke with the authors about the lessons learned from the book, the arsenal of technologies IBM has about Big Data and the future of Analytics.
-
Why Some Web APIs Are Not RESTful and What Can Be Done About It
Many Web API designers claim their are RESTful, but their APIs have little in common with REST. What can be done to make a web service API truly RESTful?
-
How to Effectively Map SQL Data to a NoSQL Store
Sytze Harkema explains how to save and retrieve relational SQL data into a NoSQL key-value store as implemented by FoundationDB, an open source, scalable, fault tolerant and ACID database.
-
Jonas Bonér on Reactive Systems Anti-Patterns
Taking the opportunity offered by the update to the Reactive Manifesto, InfoQ asked Jonas Bonér, TypeSafe CTO and original author of the first Reactive Manifesto, some questions about his vision of “Reactive” applications. Jonas offered his thoughts about both desirable features of reactive applications and what is not reactive programming.
-
The State of Practice in Model-Driven Engineering
In this article, authors discuss the practice of Model Driven Engineering (MDE) based on a survey of MDE practitioners and found that developers use MDE techniques to develop key parts of a system instead of generating whole systems.