The document summarizes a presentation by Şenol Taş at the Apache Sling tech meetup, focusing on 'restful transactions' in web development. It discusses the evolution of websites from simple platforms to complex applications that require reliable transaction management, highlighting the principles of ACID (Atomicity, Consistency, Isolation, Durability) and how REST principles can complicate transactions. The presentation emphasizes adapting the approach to transactions and utilizing tools like Adobe CQ and event-driven architecture to enhance functionality.

1. APACHE SLING & FRIENDS TECH MEETUP
BERLIN, 23-25 SEPTEMBER 2013
“RESTful transactions” with Apache Sling
Şenol Taş

2. About
adaptTo() 2013 2
§ My Name is Şenol Taş
§ Senior Computer Scientist
§ Adobe in Basel, Switzerland
@thelabertasch

3. adaptTo() 2013 3
Why such a boring Topic?

4. Because websites are…
adaptTo() 2013 4
§ No longer simple advertisement
platforms
§ Not only “online Business cards”
§ Not a “nice to have” medium
§ Not a “Playground”
§ …..

5. Because websites are…
adaptTo() 2013 5
§ Serious business
§ Make $$$
§ Complex
§ MUST have
§ “Real” Applications

6. adaptTo() 2013 6
Your Website IS THE Application

7. Let’s….
adaptTo() 2013 7
§ Find out “what is a transaction?”
§ Quick reminder about REST
§ How do this two concepts work
together?

8. adaptTo() 2013 8
What are Transactions?

9. What are Transactions?
adaptTo() 2013 9

10. adaptTo() 2012 10
“An input message to a computer system
that must be dealt with
as a single unit of work”

11. What are Transactions?
adaptTo() 2013 11
§ begin transaction
§ debit checking account
§ credit savings account
§ update history log
§ commit transaction

12. What are Transactions?
adaptTo() 2013 12
§ Late 70s: Jim Gray defined the
semantic of reliable transactions
§ Early 80s: Andreas Reuter and Theo
Härder defined the acronym “ACID” in
their paper “Principles of Transaction-
Oriented Database Recovery”

13. ACID
adaptTo() 2013 13
§ Atomicity
§ Consistency
§ Isolation
§ Durability

14. How do tools like hybernate help?
adaptTo() 2013 14

15. adaptTo() 2013 15
What is REST?

16. What is REST?
adaptTo() 2013 16
§ Representational State Transfer
§ Stateless
§ Client-server
§ Cachable
§ Scalable
§ …..

17. What is REST?
adaptTo() 2013 17
§ So? How does this work together with
transactions?

18. adaptTo() 2013 18
REST and transaction is a oxymoron

19. REST and transactions
adaptTo() 2013 19
§ Atomicity
§ Consistency
§ Isolation
§ Durability

20. What are the challenges?
adaptTo() 2013 20
§ HTTP REQUEST – RESPONSE
PATTERN
§ STATELESS
§ …..?

21. Change your mindset…
adaptTo() 2013 21
§ Not everything has to be done in one
request
§ If you are using POST.jsp or similar in
Sling, most likely something is wrong
§ Events and Observations are your
friends
§ Use the full power of the Sling Default
Post and GET Servlet

22. Remember the cheat sheet from Lars?
adaptTo() 2013 22

23. Example
adaptTo() 2013 23
§ Resource: /home/senol/profile
§ Begin transaction
§ change interests
§ Commit transaction

24. Begin Transaction
adaptTo() 2013 24
§ Copy the node /home/senol/profile to
/home/senol/transactions/profile/*

25. Change interests
adaptTo() 2013 25
§ Update with regular post request

26. Commit transaction
adaptTo() 2012 26
§ With observation or events
§ Directly

27. Things of interest
adaptTo() 2012 27
§ Communicating with services layer
§ Distributed transactions
§ Nested transactions
§ Locking…
§ Using Adobe CQ?
§ Have a look at the Workflow Launcher!

28. adaptTo() 2013 28
Thank you and have a RESTful Day!