This document discusses microservices architecture for building a social network application. It covers why microservices are useful for performance, scalability and quick development. It then discusses specific microservices for authorization using Amazon Cognito, storing social relationships as a graph database in Neo4j, implementing a news feed with different feed types, and approaches for microservices communication including request-reply, pub-sub and queues.

2. Nazariy Hazdun
● Co-Owner & CTO of Geniusee
● 8+ years of experience in IT industry
● 4+ years of team leading experience
● Co-founder of 2 startups: LimpidArmor (AR/MR/IoT),
UALight (IoT)
About me

3. Agenda
1. Why microservices?
2. Authorization
3. Graph social relationships
4. News feed
5. Microservices
communication

4. Why
microservices?
1

5. Why microservices (1/3)
● Authorization
● Feed
● Groups
● Friendships
● Messenger
● Search
● Notifications
Basic Social Network
Components

6. Why microservices (2/3)
● Performance
● Team scalability
● Quick time to market
Non-functional
requirements

7. Why microservices (3/3)
CONS PROS
● Each microservice is simple
● Scalability
● Each unit can use own stack
● Many cooperation units
● Network latencies
● No transactions
● Slower time to market

8. Authorization2

9. Authorization (1/5)
AaaS

10. Authorization (2/5)
● Integration with API Gateway
● Clients SDK (Web, iOS, Android)
● Social sign-in with Facebook, Google, and possibility to
extend drivers.
● User directory management and user profiles.
● Security features such as multi-factor authentication
(MFA), checks for compromised credentials, account
takeover protection, and phone and email verification.
Amazon Cognito
advantages

11. Authorization (3/5)
Cognito authorization
life cycle

12. Authorization (4/5)
SDK AWS SDK for PHP
Wrappers

13. Authorization (5/5)
You pay based on your monthly active users (MAUs) only. A
user is counted as a MAU if, within a calendar month, there is
an identity operation related to that user, such as sign-up,
sign-in, token refresh, or password change.
Cost
Pricing Tier (MAUs) Price per MAU
First 50,000 Free
Next 50,000 $0.00550
Next 900,000 $0.00460
Next 9,000,000 $0.00325
Greater than 10,000,000 $0.00250

14. Graph social
relationships
3

15. Graph social relationships (1/8)
Classification of
graph databases

16. Graph social relationships (2/8)
Friendships graph

17. Graph social relationships (3/8)
RDBS friendship
tables
id name
1 Nazar
2 Pavlo
3 Taras
4 Alex
5 Oksana
6 Taya
7 Roman
user_id friend_id
1 2
2 5
1 7
7 4
... ….
users friendships

18. Graph social relationships (4/8)
Neo4j vs RDBS
300xfaster

19. Graph social relationships (5/8)
● Creating friendship request
● List of requests
● Request approving
● Request cancellation
● List of friends. Depth from 1 to N.
● Friends suggestions
● Suggestions based on Facebook Graph
Use Cases

20. Graph social relationships (6/8)
Neo4j ORM drivers NeoEloquent
Neo4j PHP OGM

21. Graph social relationships (7/8)
Managed Neo4j

22. Graph social relationships (8/8)
Books

23. News feed4

24. News feed (1/3)
Timeline Feeds
● Basic feeds contain a simple list
of chronologically sorted
activities from the topics or
people you follow.
Ranked Feeds
● Ranking allows you to take
control over how activities are
sorted. Ranking activities can
help improve engagement.

25. News feed (2/3)
EdgeRank

26. News feed (3/3)
Aggregated Feeds
● Aggregation enables you to
group activities together based
on rules. This help keeps the
feed relevant when there is a
lot of activity.
Notification Feeds
● Notification feeds add the
concept of “seen” or “read” to
the activities. Commonly used
with Aggregation.
Personalized Feeds
● Leverage machine learning to further
improve the relevancy of your feed. Top
companies such as YouTube, Etsy, Linkedin
and Instagram all leverage personalization.

27. Microservices
Сommunication
5

28. Microservices Сommunication (1/5)
Request-Reply

29. Microservices Сommunication (2/5)
Push-Pull:
Amazon SQS

30. Microservices Сommunication (3/5)
● Mails sending
● Facebook invites sending
● Push notifications
● Files processing
Use Сases

31. Microservices Сommunication (4/5)
Pub/Sub Messaging:
Amazon SNS

32. Microservices Сommunication (5/5)
● Microservices communication
● Write data into ElasticSearch
● Messenger
Use Сases

33. On completion...

34. On completion (1/3)
Bicycles as a
service

35. On completion (2/3)
BIG BALL OF MUD

36. On completion (3/3)
Q&A