InfoQ Homepage Presentations Micro Services: Java, the Unix Way
The next QCon is in London, UK, March 2-6, 2020. Save an extra £75 with INFOQ20!
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 Sponsored Content
-
Related Sponsor
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?