The attendees of my #mircoservices workshop thought free choice of technology is the least interesting feature of microservices...
7
2
5
@ewolff In those cases, I tend to stress the liberty to change libraries or language versions independently from everyone else.
2
1
@stilkov Good point - but I still think this aspect is maybe not the most important one...
2
@ewolff @stilkov teams prefer familiar technology stacks. No need to change something, if the known stack does it's job
1
1
2
@thjanssen123 @stilkov Not my expierence. If what they try on the weekend does the job better they do want to use it.
2
@ewolff @stilkov even with a looming deadline and the knowledge they have to support the system for years? Sounds risky...
1
1
Replying to @thjanssen123
@thjanssen123 @ewolff Very risky, yes. Also, the basis of innovation. We’d all be programming 360 Assembler if no-one took risksz

May 2, 2015 · 8:00 AM UTC

3
1
Replying to @stilkov
@stilkov @thjanssen123 compilers etc are prooducts by themdelves - not byproducts of some project.
Replying to @stilkov
@stilkov @ewolff completely agree! But in my experience, teams avoid all unnecessary risks, if they need to get things done. Doesn't mean
Replying to @stilkov
@stilkov @ewolff they don't try something new, if pressure is low