YOW! 2012: Fred George - Programmer Anarchy

Description

Fred George is a consultant with over 44 years experience in the industry including over twenty years doing object programming and over a dozen years doing Agile/XP. He counts at least 70 languages with which he has written code. A veteran of the IBM-Microsoft wars, Fred did early work in computer networking, LAN's, GUI's and objects for IBM.

Here, we dig into programmer anarchy, beginning with what it actually means! Tune in. Very interesting and fresh perspectives within... Certainly, Fred's ideas are a little controversial, but they are being vetted and proved in the real world, especially in the financial industry, where software updates happen thousands of times per day.

The Discussion

How does the end-to-end scenario performance look like in a large micro service architecture? The service orientation allow great flexibility to plug n play but then incur non-trivial latency impact.

How well does the maintenance of the system work? As mentioned in the video, the services are not and cannot really be orthogonal, which mean there will be likely be chain of dependencies, and satisfying a single requirement could lead to ripple through changes to multiple services. That defeats the flexibility coz multiple services will necessary deploy together and maintained together, not so micro anymore.

That ultimately also lead to the question of scale. If I have a 5M lines of code system that I want to move towards a micro service architecture, that will be something like 50,000 services if the services are truly micro (100 lines), the maintainence problem will not be the services itself but more the graph of them, how the dependencies of them goes, and which impacts which... that complexity cannot be underestimated.