The document outlines the evolution of software development practices at Globo from 2008 to 2017, specifically focusing on the transition from Ruby on Rails to Elixir. It highlights key projects, performance metrics, and strategies employed to improve system throughput and response times, emphasizing the importance of risk-taking and adaptation in technology. The author shares insights on fostering trust and collaboration within teams to drive innovation and deliver value effectively.

1. Beyond your daily coding
Emerson Macedo
@emerleite

7. 2008

8. 2008
Some guys created a project
using Ruby on Rails when
Orkut Apps were cool

9. 2008
Some guys created a project
using Ruby on Rails when
Orkut Apps were cool

10. 2008
Some guys created a project
using Ruby on Rails when
Orkut Apps were cool

11. 2008
Ruby on Rails receive a
big red flag from lots of
influencers inside the
company.

12. 2009

13. 2009
I was working in a Fotolog web
application created using Java
J2EE , before Facebook killed
all these photo websites

14. 2009
I was working in a Fotolog web
application created using Java
J2EE , before Facebook killed
all these photo websites

15. 2009
Inside Big companies, it
was very popular to use a
Reference Architecture
for all applications

16. 2009
Reference
Architecture

17. 2009
In the end of 2009 a project to
create a sing in system for
reality shows came to our
team

18. 2009
In the end of 2009 a project to
create a sing in system for
reality shows came to our
team

19. 2009
We all knew that Ruby on
Rails development lifecycle
was faster and this project
could be a good fit

20. 2009
Sometimes you have to take
risks to achieve important
goals and generate high
impact

21. 2009
Sometimes you have to take
risks to achieve important
goals to generate high
impact

22. 2009
I spend my after work time
teaching my coworkers how
to program in Ruby and
Rails

23. 2010

24. 2010
In may, we put again a Ruby
on Rails project in
production

25. 2010
The expectation was to deliver
in July ,but we delivered the
application two months
early

26. 2016

27. 2017
What about 2010 to 2016?
You did nothing?

28. 2016
After 2010, lots of projects
at globo.com were written
using Ruby on Rails

29. 2016
After 2010, lots of projects
at globo.com were written
using Ruby on Rails
Mission
Accomplished

30. Video User Profile
Service

31. CONTEXT
User Profile Service was developed in
2012. It’s a well written Ruby on Rails
application , responsible for track
logged user actions

32. CONTEXT
Our Video Player POST Watched
Percentage to our Endpoint so we can
provide Keep Watching Percentage
to our Logged Users. It does it
every 10 secondsx
x

33. CONTEXT
Globo is making
Binge Watching
experiments combined
with Online First for
new TV Shows
TV Shows

34. CONTEXT
Prepare all Video
Applications for the
Olympics

35. Online First
Binge Watching

36. THE PROBLEM
2013
10k
The throughput increased
between 2013 and 2016

37. 2013 2016
10k
60k
THE PROBLEM
The throughput increased
between 2013 and 2016 ~600%

38. 2013 2016
10k
60kTHE PROBLEM
It was hard to predict the new
Appication Throughput
2016 / 2
?

39. INFRASTRUCTURE
2 bare metals, each one
with 24 CPUs and 64GB
of RAM

40. THE PROBLEM
The average response time
was good, but percentiles
were hurting the application
Avg
70ms

41. 70ms
THE PROBLEM
The average response time
was good, but percentiles
were hurting the application
99
2.5s
95
1s
Avg

42. FIRST CHANGE
We increased the
computational resources
from 2 to 4 bare metals

43. FIRST CHANGE
We increased the
computational resources
from 2 to 4 bare metals Each one with
24 CPUs and
64GB of RAM

44. 70ms
99
2.5s
95
1s
Avg
FIRST CHANGE
This change improved
metrics by ~32%

45. FIRST CHANGE
This change improved
metrics by ~32%
9995
1.7s
0.7s
Avg
47ms
~32%
better

46. SECOND CHANGE
We decided to try a deployment with
Tsuru containers with auto scaling, each
one with 1-4 vCPU and 2GB of RAM

47. SECOND CHANGE
We decided to try a deployment with
Tsuru containers with auto scaling, each
one with 1-4 vCPU and 2GB of RAM
93 containers

48. SECOND CHANGE
9995
1.7s
0.7s
Avg
47ms
Migrate to containers improved
metrics by ~12%

49. SECOND CHANGE
9995
1.5s
0.5s
Avg
41ms
Migrate to containers improved
metrics by ~12%
~12%
better

51. 2013 2016
10k
60kELIXIR VERSION RESULTS
After the Olympics and with
Binge Watching, the
throughput increased ~50%

52. 2013 2016
10k
60kELIXIR VERSION RESULTS
After the Olympics and with
Binge Watching, the
throughput increased ~50%
2016 / 2
90k

53. ELIXIR VERSION RESULTS
From 4 bare metals, using
24 CPUs and 64GB of
RAM to 33 containers,
using 1-4 vCPU and 2GB
of RAM
3 containers30 containers
ElixirRuby

54. ELIXIR VERSION RESULTS
9995
1.5s
0.5s
Avg
41ms
Elixir version improved
metrics by ~95%

55. ELIXIR VERSION RESULTS
9995
30ms
15ms
Avg
4ms
Elixir version improved
metrics by ~95%
~95%
better

56. ELIXIR VERSION RESULTS
I presented the Elixir
version to the Globo
Technology Committee

57. 2017

58. 2017
This year we delivered
mission critic projects in
production at globo.com
using Elixir

59. 2017
This year we delivered
mission critic projects in
production at globo.com
using Elixir
Mission
Accomplished

60. HOW TO DO THE SAME?
What the story about Ruby
on Rails and the story about
Elixir have in common?

61. HOW TO DO THE SAME?
First, we have to understand
how the game works. It’s
simple, we just need to
accept it

62. HOW THE GAME WORKS
Your boss wants profit. He pays
you a good salary because his
expectation is that you will make
his company more profitable

63. HOW THE GAME WORKS
You’re paid to deliver value.
Your company is not
expecting you to write
code like a monkey.

64. HOW THE GAME WORKS
Value is recognized with
perception. It’s not always
fair, but’s the game. Again, we
just need to accept it

65. HOW THE GAME WORKS
If your employer trusts you, he’ll be
have a better perception about
your job and also be more open to
your ideas that challenges the
status-quo

66. HOW THE GAME WORKS
Start doing your daily job
the best you can, so the trust
will came. Do not challenge
the status-quo before this.

67. HOW TO DO THE SAME?
What the story about Ruby
on Rails and the story about
Elixir have in common?

68. HOW TO DO THE SAME?
In 2009, Ruby on Rails was
probably in the Early
Adopters group. Java was
for the Laggards

69. HOW TO DO THE SAME?
In 2009, Ruby on Rails was
probably in the Early
Adopters group. Java was
for the Laggards

70. HOW TO DO THE SAME?
In 2016, Ruby on Rails was in
the Laggards group and
Elixir in the Early Adopters
group.

71. HOW TO DO THE SAME?
People may think Globo is
always in the Early Adopters
group, but it’s not true.

72. HOW TO DO THE SAME?
We’re often between the
Early Adopters and Early
Majority groups, but be
Early Adopter is good for us

73. HOW TO DO THE SAME?
What is the pattern from Ruby
on Rails and Elixir story at
globo.com?

74. HOW TO DO THE SAME?
Find the opportunities.
They’re everywhere.
Sometimes it’s not easy to
find then, but they’re there.
x
x
x
x
1

75. HOW TO DO THE SAME?
Create pet projects or do
some freelancer or
experiments with the tool
you want to introduce in your
company
2

76. HOW TO DO THE SAME?
Sell it to your coworkers. You will
not have success alone. People
often work at a team, so it will be
good if they buy your solution
3

77. HOW TO DO THE SAME?
Create a POC with the
solution you thought to solve
the problem you have
identified
4

78. HOW TO DO THE SAME?
Present your results to the
stakeholders. They will be
the engine to support you
spread the solution
5

80. YouÊre paid to
deliver value not code

82. That’s all folks
Emerson Macedo
@emerleite
https://blog.emerleite.com