James Lewis, keynote at I T.A.K.E. Unconference 2015, has a valuable contribution on Microservices Architecture.
Sneak peak:
“In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.”
If interested in this topic, read the full contribution, jointly created with Martin Fowler.
Join I T.A.K.E. Unconference 2015 to hear more in his talk: Microservices – Systems That Are #neverdone.
Meet the speakers – Part 4. Early Bird tickets available
Software craftsmen from more than 15 countries will meet in the heart of Bucharest, 19-20 May, at I T.A.K.E Unconference! For 2 days, more than 30 speakers will share insights, latest trends, and deliver hands-on sessions.
In Meet the Speakers Part I, Part II, and Part III, we shared more about the speakers who will make this year event a one not to be missed. Below, you can read more about other top-notch practitioners who joined the speakers line-up:
Come discover mutation testing and make sure your never forget another assert again.
Alexandru Bolboaca, CTO MozaicLabs, Romania
Intro to Microservices (Talk)
Alexandra Marin, Software developer at crossplatform.io, Romania
C# and NUnit tests are essential, but limited. Let’s make our testing toolkit complete with automated UI acceptance testing for common behaviors like pressing buttons, making swipe gestures, entering text and validating inputs.
Flexibility through immutability (Talk)
Is immutable data just functional programming snobbery? How could it possibly provide more flexibility than a mutable approach?
Houssam Fakih, Software Engineer at Arolla, France
Boris Gonnot, Head of Feature Development Teams at BISAM, France
Metrics For Good Developers (Talk)
Simple and efficient metrics for developers
Want to challenge the current programming practices as these software craftsmen are doing? Want to experience new techniques, debate on the existing ones or even pair program in the I T.A.K.E Unconference space?
Get your Early Bird ticket today!
Stay tuned. We will continue publishing more about the program, speakers and the dynamic learning practices awaiting you.
Thrilled to see you in May!
Chat bots & microservices
Enjoy the following series of interviews with the speakers, top-notch software crafters from across Europe, joining I T.A.K.E Unconference, Bucharest, 19-20 May. Discover the lessons learned and what drives them to challenge the known path in their field.
Yegor Bugayenko, CTO and co-founder Teamed.io, will share in his talk about how chat bots are a more effective way of interaction between web (micro-)services and users than traditional HTML user interfaces.
#1. SHARE TOP 3 THINGS YOU DID THAT HELPED YOU GROW & BECOME THE PROFESSIONAL YOU ARE TODAY
#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2016?
# 3. What else would you like to share with participants at I T.A.K.E Unconference 2016?
Want to join Yegor and many more software crafters from around Europe?
Programming contest @I T.A.K.E Unconference
As for every I TAKE Unconference edition, we want to give a chance to the software crafters from the audience to showcase their skills and learn more in the process. And because we appreciate passion, we offer a prize to those who convince a jury of well-known international developers that they are the most skilled in the room.
This contest is not meant to be easy. It will require you to practice beforehand, so please read the instructions carefully.
It will also require you to register before the event.
Mechanics
- IMPORTANT: Register to the contest latest one day before I TAKE Unconference by sending an email to steliana.moraru@mozaicworks.com
- On the first day of the event, after lunch, you have max 15′ to do a performing kata in front of the jury.
- The winner will be announced at the end of the second day
Constraints
To simplify the jury’s decision, the performing kata has to conform to the following constraints:
- Only the following programming languages are accepted: Java, C, C++, C#, Python, Visual Basic .NET, PHP, Javascript, Swift or Ruby
- Only solo contestants are accepted. Sorry, no pair programming this time
- The kata has to showcase refactoring skills.
- The kata has to last max. 15′
How we will judge
The jury will judge your refactoring skills.
The ideal kata looks like this – you will get maximum point if you:
- clearly state the smells you see in the code
- pick one of the smells
- clearly state your plan to fix the smell
- fix it in small, safe steps
- run tests after each step to prove you didn’t break anything
- commit after each step with a clear message explaining why you made the change
- fix as many smells as possible within the time constraint
You will loose points if you:
- make big or unsafe changes to the code
- break the behaviour after changing the code
- don’t improve the code a lot
- don’t improve the design by the end of the kata (hint: we judge design using SOLID principles and the four elements of simple design)
Recommendations
To help you, we’ve thought out what we would do if we participated to such a contest. Here’s what we recommend.
1) Use one of the following codebases for the kata:
- https://github.com/emilybache/GildedRose-Refactoring-Kata
- https://github.com/emilybache/Tennis-Refactoring-Kata
- https://github.com/emilybache/Yatzy-Refactoring-Kata
- https://github.com/emilybache/Parrot-Refactoring-Kata
2) Practice beforehand on the structure we presented for the ideal kata. Ideally find someone to practice with.
3) Watch other people refactoring. YouTube has many videos on the topic, including using the recommended code bases.
Glossary
A programming kata is a repeatable exercise used to practice specific skills.
Performing kata means doing a kata in front of an audience.
Refactoring means changing the internal structure of the code without changing its behaviour.