Agility, SOA, Virtual Extended Enterprise, Swarming Tactics, and Architecture

Agility and the Virtual Extended Enterprise

In the 1990s, The Agility Forum of
Lehigh University defined Agility as “The ability to successfully respond to
unexpected challenges and opportunities.” The
forum chartered a technical commi…

Agility, SOA, Virtual Extended Enterprise, Swarming Tactics, and Architecture

Agility and the Virtual Extended EnterpriseIn the 1990s, The Agility Forum of Lehigh University defined Agility as “The ability to successfully respond to unexpected challenges and opportunities.” The forum chartered a technical committe…

Monolithic Applications and Enterprise Gravel

It’s been almost a year since I’ve written anything about microservices, and while a lot has been said on that subject, it’s one I still monitor to see what new pops up. The opening of a blog post that I read last week caught my attention: Coined by Melvin Conway in 1968, Conway’s Law states: […]

Roger Evernden – Enterprise Architect 2016-08-09 08:49:58

It’s always interesting to look at the agenda for EA conferences – it’s a good indicator of what architects are actually doing, and the type of concerns they are actually addressing. Here are some of the things that struck me when looking at the agenda for the forthcoming iCMG Architecture World summit, being held in Bangalore on…

API Design: Compartments

I’ve been reviewing the FHIR (Fast Healthcare Interoperability Resources, http://www.hl7.org/fhir) specification and they have an interesting concept called a compartment.  Per the spec: Each resource may belong to one or more logical compartments. A compartment is a logical grouping of resources which share a common property. Compartments have two principal roles: Function as an access […]

API Design Challenges: Competing Demands

Working inside an enterprise is constantly a challenge to balance competing demands and chart the best course forward.  Unfortunately, typical corporate IT culture is one where everything is ruled by project delivery metrics: on time and on budget.  Based on behaviors I’ve observed, this results in two common things: Efforts to minimize the teams involved. […]

Dynamic Data in REST

I had an interesting conversation with some colleagues around resource design that I thought would be helpful to share.  The starting point was a simple question: Should price generation be a HTTP POST or HTTP GET? There’s solid reasoning for either of them.  Let’s start with HTTP GET. From a consumer’s perspective, a GET probably […]