The document discusses microservices and splitting a web application into smaller independent services. It provides examples of how a web application could be split into services for the main web, mobile, community, ads, images, and comments. It describes advantages of smaller services including being easier to maintain, deploy, and test in isolation. Challenges of microservices like service interaction, failures, and maintaining backwards compatibility are also covered.

1. Symfony
e micro (mica tanto)
servizi

2. A bit of history…

4. Peaks on gen - jun - aug up to 70 M pg/mth
Peaks during big matches

6. PaaS Platform as a Service
(almost) Zero configuration
Put the code “on the cloud” and you’re done

8. In the beginning there was…

10. Hard limits on resource (e.g 50 db con)
Deploy via ftp (sf cache mess)
Blackbox: No realtime log, no access
PHP 5.3

11. Microservices FTW!

15. micro vs macro?
orchestration?
maintenance?
security?
test?

16. micro vs macro

17. How many ways can you split
an app?

19. Web: the main web (sf1)
Mobile: mobile version (sf components)
Vxl: community site (sf2 v2.8)

20. Talk: api for comments, votes, ratings (sf2 v2.8)
Adv: api for ads serving (sf2 v2.8)
Media: api for images mgnt (sf2 v2.8)

22. Talk api

23. /queue
/comments
/comments/totals
/comments/{idComment}
/comments/publish
/comments/{idComment}/votes
/comments/{idComment}/votes/{idVote}
/comments/best-users
/comments/week-best-users
/comments-with-replies
/users/{userId}/statistic
/users/{userId}/comments
/articles/most-commented-today

24. Media api

25. /collections
/collections/{idCollection}
/files
/files/multiple
/files/{idFile}
/files/{idFile}/publish

26. Why small is better?

28. Lines Of Code

29. Fits in my head
https://www.infoq.com/presentations/microservices-replaceability-
consistency

31. How services can interact?

32. Client Side

33. S1
S2
S3
Page
UI1 UI2
UI3

36. Client knows the endpoint
Endpoints are public (caching!)
Async loading, progressive enhancement

37. Server Side

38. S1
S2
S3
ProxyUI

42. Client knows only one endpoint
Do not expose the underlying architecture

43. Provide high level apis

45. What if something goes wrong?

47. All services are on subdomains
vxl.calciomercato.com
www.calciomercato.com

48. Login set cookie on .calciomercato.com

49. web
vxl
login Cookie
PHPSESSID: b22j6…
Domain: .calciomercato.com

50. Api services are token based
talk.calciomercato.com
adv.calciomercato.com
media.calciomercato.com
token expires with session

51. Deploy

52. How can we deploy a feature
involving a single service?

53. How can you deploy a feature
involving n services?

54. Keep Backward Compatibility!

55. What if you are removing an endpoint?

56. What if you are adding an endpoint?

57. What if you are modifying an endpoint?

58. Maintenance

59. n smaller app to keep updated

60. MicroKernelTrait

61. Testing

62. Test a service in isolation

65. Test interaction of several
services?

66. S1
S2
S3
SUT

67. What we learned so far?

68. Michele Orselli
CTO@Ideato
_orso_
micheleorselli / ideatosrl
mo@ideato.it
Thank you!
https://joind.in/talk/92907

69. https://electric-cloud.com/blog/author/ecloud/page/5/
http://www.magnasoma.com/content/images/Magnasoma-Monolith-3-01.jpg
https://sudo.hailoapp.com/assets/posts/journey-to-microservices/wheel-of-doom-
highlighted.png
http://www.arabamerica.com/wp-content/uploads/2016/05/20160422-the-wire-so-and-so-
animated-gif-1.gif
http://blogs.versionone.com/agile-development/wp-content/uploads/sites/4/2013/04/
ContextMap2.png
https://cdn.infoq.com/statics_s1_20161011-0321_2/resource/articles/qcon-london-2015/en/
resources/8-a.jpg
http://www.uqasar.eu/wp-content/uploads/2014/05/Metrics.jpg
http://pad1.whstatic.com/images/thumb/8/8c/Cheat-at-Card-Games-Step-3.jpg/728px-Cheat-
at-Card-Games-Step-3.jpg