How To Become a Match Maker For Your Backend by Deden Fathurahman (Setipe)
![About
• geekdad()
• current("VP Engineering SETIPE”)
• before(['Erafone', 'Wayang Force', ‘Qeon’])
elsewhere ->
@dedenf
github.com/dedenf](https://image.slidesharecdn.com/setipe-techinasia-160516060325/85/how-to-become-a-match-maker-for-your-backend-by-deden-fathurahman-setipe-2-320.jpg?cb=1463392152)
How To Become a Match Maker For Your Backend by Deden Fathurahman (Setipe)
Deden Fathurahman is a VP Engineering at Setipe, an online matchmaking service for singles to have a private, safer and more effective place to meet other compatible singles. They curate and introduce matches for you using demographic, preference, psycho-graphic and social-economic factors. This slide was shared on TIA Dev Talk: "Road to Developer Stage – Tech in Asia Jakarta 2015" on 15 October 2015. TIA DevTalk is a monthly event of TIA Dev Community-- a community for all developers and/ or engineer to create collaborative things that advanced the tech community and ecosystem. Get updates about our dev events delivered straight to your inbox by signing up here: http://bit.ly/tia-dev !. Be the first to know when new information is available!
Recommended
More Related Content
Viewers also liked
More from Tech in Asia ID
More from Tech in Asia ID(20)
Recently uploaded
Recently uploaded(20)
How To Become a Match Maker For Your Backend by Deden Fathurahman (Setipe)
- 1. how to become a match maker for your backend
- 2. About • geekdad() • current("VP Engineering SETIPE”) • before(['Erafone', 'Wayang Force', ‘Qeon’]) elsewhere -> @dedenf github.com/dedenf
- 4. SETIPE
- 5. • A Match Maker • currently 450k registered users • Mashed up between (psychology + technology) = #love • 31 married couple who met at SETIPE • yang jadian?
- 9. Let’s break it down inside out
- 10. Load balancer
- 11. Nginx to the rescue
- 12. act as load balancer, http proxy there are other solution, like HAProxy, node-http-proxy …
- 15. Monolithic App single codebase call every library on the run single bug could ruin all your system hard to scale one request could involved all the system Easy to manage but
- 16. Microservices Architecture separate codebase if there’s a bug in a service only that service affected minimal resource support for event driven arch Hard to manage but sometimes…
- 17. Distributed system is hot right now
- 18. pub-sub
- 19. we use it a lot queue messaging session store introducing redis and we make cluster of it
- 20. Matchmaking Engine we use redis to holds our job queue to matchmaking people and worker will took care of it
- 21. consistency
- 22. Eventual consistency is a consistency model used in distributed computing to achieve high availability that informally guarantees that, if no new updates are made to a given data item, eventually all accesses to that item will return the last updated value. https://en.wikipedia.org/wiki/Eventual_consistency
- 23. 99% Consistency is good enough
- 24. know your tools - load balancing (haproxy, nginx, …) - webserver (nginx, …) - always use compression - Static assets (CDN)
- 25. Monitoring
- 26. you can’t optimize what you don’t measure
- 29. things to watch ‣is the app running? ‣is the app overloaded? ‣how many errors do we have ‣how your cluster are doing ‣app performance ‣database(s) (this is down to your app perf)
- 31. Thank you