After nearly 3 years of building micro-services systems, you learn a few things. This is an empirical report on the good, the bad, and the ugly.

1. nearForm ❤️ micro-services.
Richard Rodger @rjrodger
4 years of Node.js
50+ projects
startups to gorillas
1 user to 1 000 000
every kind team
all skill levels

2. What do you think micro-services
are made of?

3. You write less code,.
You’re a happy camper.

4. You run lots of little processes,
on many machines.

5. You use messages to communicate.

6. You can use plain old web services.

7. Or, you can get fancy with
message broadcasting.

8. Your system will scale.

9. You deploy. You smile.

10. You get real software components.
Finally!

11. Stuff we got wrong. Misery.
💩
PILE OF POO
U+1F4A9

12. You can never get away
from some anti-patterns.

13. You can use any language!
What could possibly go wrong?

14. You’ll discover more services
than you’ll design.

15. You’ll need practice.
Micro-services break a lot of things.

16. Stuff we got right. Awesome!
🚀
ROCKET
U+1F680

17. You can swap databases mid-project!
Or anything else. Infinite Power!

18. You should use a framework.
There’s lots of housekeeping.

19. You need to use Docker.

20. You need to automate deployment.
We’re open-sourcing our deployer.
Go to the deployment workshop!

21. Thanks!
Richard Rodger
@rjrodger