Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1Wc1nuj. Sadek Drobi talks about the prismic.io API and how to understand the properties and the mechanics of a system, and to partition its different dimensions to avoid a failure cascade. Filmed at qconlondon.com. Sadek Drobi is a software engineer specialized in bridging the gap between the problem domain and the solution domain. As a core Play developer and Play2 co-creator, he works on the design and implementation of the framework.

1. Sadek Drobi
prismic.io CEO & Co-founder
Playframework Co-creator
@sadache
Taming Failures by Partitioning
Time and Space

2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
prismicio

3. Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide
Presented at QCon London
www.qconlondon.com

4. prismic.io, a snappy tour

5. Building a Website with dynamic
content is a pain
No content
management
Use CMS building
blocks and plugins
Use a visual builder
tool
<style>
h1 { font-family: ‘Aller’ }
</style>
<h1>
Change your world now!
</h1>

6. prismic.io is a new way to bring
your website content alive

7. prismic.io is a new way to bring
your website content alive
Simple Web API
to consume
content
Content
management
backoffice

8. Content is Central to Websites

9. Business Wise
● Offer Performance and Reliability
● Excel where every CMS fails

10. First, we need to understand
the impact of system failure.

11. Impact of System Failure
● Writing Room: No edit, save or publish
● API: No end-user website

12. Impact of System Failure
● Writing Room: No edit, save or publish
● API: No end-user website

13. System Requirements From a Macro
Perspective
● Concurrent Write
● Concurrent Read
● Redundant
● Reliable and available
● Consistent

14. System Requirements From a Macro
Perspective

15. CAP says no!

16. Let’s Talk about Time

17. Observe time ticks

18. Observe time ticks

19. Two different universes, two different times

20. Authors write
some content
On Publish,
Content is displayed on
website

21. Writer universe Viewer universe
Two different universes, two different times

22. publish
Data Extraction
API
On publish event, we update API system time

23. publish
Data Extraction
API
If Writing Room goes down, API isn’t affected

24. We Can Do Even Better

25. publish
Data Extraction
API
Clients APIs can be time decoupled too!
publish
Data Extraction
API
publish
Data Extraction
API

26. S3
publish
publish
publish
Infrastructure wise

27. publish
We use Apache Lucene for our API
Ready to download,
zipped Lucene
Index
download

28. S3
Server Failure?

29. Elastic?

30. Do we need
traffic officers or
traffic lights
here?

31. Applying the Same on the
Writing Room

33. Interactive Read/Write
Once a week
to post a blog post
Did not connect
for weeks
Does not connect
anymore
Giant database x100.000
repositories
Two hours a day
to update news

36. Do we really need to keep everything
here in case of?

38. Each repository has it own lifecycle
Databases
Book
Redundent
Cloud storage
Wake up on
demand
Archive when
idle

39. Infrastructure wise
S3
snapshots
logs

40. Clusters
Data Migration
Functionality A/B Testing

41. Observe time ticks

42. Solves
● Scalable space-efficient infrastructure
● Data migration and versioning (avoid
stop-the-world migrations)
● Multiple production environments (with
multiple data versions)
● Testing new functionalities

43. System Requirements From a Macro
Perspective
● Concurrent Write
● Concurrent Read
● Redundant
● Reliable and available
● Consistent

44. Scalability is not a buzzword you can put on a slide
nor
A technology you can purchase

46. Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
prismicio