Gene Hughson

Home/Tag:Gene Hughson

Microservices and API Complexity – Inside and Out

The signature benefit of a microservice architecture is that its highly granular nature allows for a great deal of flexibility in composing applications. Components are simplified by virtue of a high degree of focus. The ability to replace individual components is enhanced by the modularity inherent in the style. A very significant drawback to microservice

Design? Security and Privacy? YAGNI

By Gene Hughson Two of my favorite “bumper sticker philosophies” (i.e. short, pithy, and incredibly simplistic sayings) are “the simplest thing that could possibly work” and YAGNI. Avoiding unnecessary complexity and unneeded features are good ideas at first glance. The problem is determining what is unnecessary and unneeded. Just meeting the functional requirements is unlikely

Dealing with “Technical Debt”

By Gene Hughson The term "technical debt" has a tendency to evoke an emotional response.  Some people react puritanically - "technical debt" means sloppy code; sloppy code is sin; failing to call sin "sin" is condoning sin; to the stake with the heretic!  Others will contend that technical debt solely refers solely to conscious trade-offs

Microservices: The Return of SOA?

By Gene Hughson In the early 2000s, Service-Oriented Architecture (SOA) was the hot topic. Much ink was spilled in touting its potential. Effort and money was expended in attempts to secure its promised benefits. Like object-orientation and reuse before it, the reality of SOA was not able to live up to the hype. Unlike them,