InfoQ Homepage Presentations Micro Services: Java, the Unix Way
Micro Services: Java, the Unix Way
43:30
Summary
James Lewis tells the story of building a resource oriented, event driven system out of applications about 1000 lines long.
Bio
James Lewis is a Principle Consultant for ThoughtWorks based in the UK and a member of the ThoughtWorks Technical Advisory Board. Most recently he has been helping to introduce Agile at various blue chip companies: Investment Banks, Publishers and media organizations. Most recently, James has been spending his time helping ThoughtWorks' clients develop enterprise software as a coding architect.
About the conference
Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.
Jan 04, 2013
-
Related Sponsor
/filters:no_upscale()/sponsorship/topic/5ac9c2f1-65f3-41c4-b48a-7c2b04e4e240/CamundaLogoRSB-1627035881977.jpg)
Community comments
Good tips, questionable results
by Fred Amiter,
Re: Good tips, questionable results
by Paolo Perrotta,
Good tips, questionable results
by Fred Amiter,
Your message is awaiting moderation. Thank you for participating in the discussion.
Interesting talk. To me it demonstrates that good tips don't necessarily lead to good results. The team re-invented many tried and proven solutions (a.k.a. NIH syndrome).
My Tip 10: don't re-invent the wheel. Understand and apply best practices.
Nonetheless, I'd prefer to see more architecture- and design-oriented talks like this instead of the fluffy Agile stuff that is occupying infoq lately.
Re: Good tips, questionable results
by Paolo Perrotta,
Your message is awaiting moderation. Thank you for participating in the discussion.
How is this NIH syndrome? They used common, well-supported standards (AtomPub, JSON, HTTP, the monitoring stuff) that are way less likely than any enterprise standard to fall out of fashion soon. I wish many companies I consulted with could buy into this philosophy, rather than looking for the silver bullety, bloated, big-bang solution du jour, like ESBs.
What kind of wheel do you think they reinvented?