The Fourth International Workshop on RESTful Design, WS-REST 2013 REST in Brazil - Industry Keynote On learning REST, and its impact on the design of massive applications in Brazil

1. REST in Brazil
Services and Issues to be fought
Guilherme de Azevedo Silveira

2. Brazil
• huge
• huge custom software development market
• huge software integration issues
• huge cobol, vb, delphi, java, c# legacy systems
• software development and educational
revolution

3. Guilherme Silveira
• Caelum CTO
• Software Development Education
• http://www.caelum.com.br
• http://www.casadocodigo.com.br
• guilherme.silveira@caelum.com.br

4. Guilherme Silveira
• Applied Math (Discrete Dynamic Systems)
• REST (in practice)
• 고려사이버대학교 컴퓨터정보통신학과 (Cyber Korea
University)

5. AGENDA
• brazilian projects
• industry
• industry issues
• adoption issues
• educational issues

6. Alexandria
• engineering.abril.com.br
• Abril Midia
• graphic
• distributor
• education
• CMS
• Luis Cipriani

7. Alexandria: content
• 3 languages types
• 7 databases types
• 9 frameworks
• 207 machines
• 12.5 million pageview/month

8. Alexandria: approach
• Layered System
• Stateless
• Cache
• Code-on-demand
• ...

9. Alexandria: conclusions
• Long term needs
• Documentation need++
• Focus on protocol improvements later

10. Alexandria
• REST: Advanced Research Topics and
Practical Applications, Springer

11. Caelum
• live learning
• enrollments, payments
• alumni
• job postings

12. training
java + vraptor
one system
alumni.caelum.com.b
r
RoR
ondetrabalhar.com
ruby
mysql
mysql
solr

13. Caelum Online
• online: learning environment
• training
• exercises
• videos
• explanations
• experience exchange
• payments

14. training
java + vraptor
one system
alumni.caelum.com.b
r
RoR
ondetrabalhar.com
ruby
gnarus
scala + vraptor
casa do
código
java + RoR
payments
java
metrics
java + octave
interestie
sinatra + sequel
sugest
java
promo
RoR
analyser 1
sinatra
analyser 2
java
exercises
RoR
badges
ruby + rails
mountable
engine
RoR + 6 projects
RoR
+ 1 „pages‟
jsaws tickets
RoR
books
sinatra + sequel
mysql
mysql
mysql
mysql
mysql
redis
redis
solr
github
postgresql postgresql
postgresql
postgresql
postgresql
postgresql

15. Caelum Online
• > 18 systems
• 4 language types
• 5 frameworks
• 5 database types
• < 20 developers

16. training
java + vraptor
one system
alumni.caelum.com.b
r
RoR
ondetrabalhar.com
ruby
gnarus
java + vraptor
casa do
código
java + RoR
payments
java
metrics
java + octave
interestie
sinatra + sequel
sugest
java
promo
RoR
analyser 1
sinatra
analyser 2
java
exercises
RoR
badges
ruby + rails
mountable
engine
RoR + 6 projects
RoR
+ 1 „pages‟
jsaws tickets
RoR
books
sinatra + sequel
mysql
mysql
mysql
mysql
mysql
redis
redis
solr
github
postgresql postgresql
postgresql
postgresql
postgresql
postgresql

17. we study
• advantages
• disadvantages

18. what about others?
• people
• companies
• projects
• schools

19. developers
• know
• GET, POST
• html
• js

20. developers• know
• GET, POST
• html
• js
• no idea
• http
• hypermedia
• code on demand

21. companies
• know
• GET, POST
• html
• js

22. companies• know
• GET, POST
• html
• js
• no idea
• http
• hypermedia
• code on demand

23. schools
• teach
• GET, POST
• html
• js

24. schools• know
• GET, POST
• html
• js
• no idea
• http
• hypermedia
• code on demand

25. companies
looking ahead
academia
the rest of the industry

26. gap
our
study
everyone‟s
practice

27. i feel lost
as industry

28. as a client

29. as a client, how do i?
• service discovery
• in an android environment
• google intents; web intents
• on the web?
• web intents?
• richer? standards? good practices?
• “A Framework for Self-Descriptive RESTful
Services”

30. as a client, i know my
providers

31. # of actions supported?
• web intents scales on providers
• what about # of actions?
• “Distributed Affordance: an Open-world
Assumption for Hypermedia”

32. as a company

33. an existing service
• migration costs x no costs
• how do I publish my service?
• where do I publish my service?
• “A Concept for Generating Simplified
RESTful Interfaces”

34. as a new service
• design?
• json?
• rdf?
• “Model Your Application Domain, Not Your
JSON Structures”

35. as a hammer

36. we see everything as
nails

37. as a learning
environment

38. we see the problem
as an human issue

39. we see the problem as
an human issue

40. we see the problem as an
human issue
• TDD
• test first
• + other software engineering practices
• Mauricio Aniche‟s research
• http://www.aniche.com.br/publications

41. we see the problem as an
human issue
• developers
• solve problems with and without TDD
• analyze the solutions

42. we see the problem as an
human issue
• “No difference between TDD and no
TDD.”
• “Experience and wisdom makes the
difference.”

43. we see the problem as an
human issue
• Lutz Prechelt
• An empirical comparison of C, C++, Java,
Perl, Python, Rexx, and Tcl
• http://page.mi.fu-
berlin.de/prechelt/Biblio/jccpprt_computer
2000.pdf

44. we see the problem as an
human issue
• developers
• solve a problem in different languages

45. we see the problem as an
human issue
• “the differences between languages tend
to be smaller than the typical differences
due to different programmers within the
same language”

46. as a learning
environment

47. we see the problem
as an educational
issue

48. we see the problem as
an educational issue

49. service production chain
school
graduation
industry
academia
we see the problem as an
educational issue

50. academia & industry
• try to bring every company and
developer closer to research ?
• if not researching, trying in practice and
analyzing its results?

51. question:
how can we make
others think about
REST?

52. how can we make others think about REST?
Guilherme Silveira
guilherme.silveira@caelum.com.br
THANK YOU