The document discusses the DCI (Data, Context, Interaction) architecture, emphasizing its benefits in object-oriented programming and its successful implementation in production. Key takeaways include improved testing and fewer objects through role-focused design, along with some limitations encountered in Ruby. It also mentions Marvin, a programming language tailored to support DCI, building on the fundamentals of C#.

1. DCI - the architecture
from the future?
Andrzej Krzywda
Arkency

2. Andrzej Krzywda
• Ruby
• Arkency
• async/remote work
• DDD, Hexagonal, CQRS/ES, Clean Architecture
• used DCI in production 3.years.ago

3. OOP vs FP

4. Use cases!

5. DCI
• Data
• Context
• Interaction

6. The mental model

7. objects

8. function

9. Focus on runtime
interaction

13. http://www.slideshare.net/cosenzaLab/dci-gizmo

14. Examples
• Gaming platform
• Meetup context
• Account example

15. Lessons from production
• Fewer objects
• More roles
• Use-cases == awesome
• great for testing (at use-case level)
• limitations of Ruby (unable to unextend)

16. http://fulloo.info

18. https://www.youtube.com/watch?v=KtHQGs3zFAM
Cope vs Uncle Bob
on TDD

19. Marvin is a programming language that was
designed with DCI in mind. It builds heavily on C#.
The first versions of Marvin can be seen as
extensions to C# where versions in the road map
will most likely reshape some of the fundamentals
to provide even better support for DCI

20. Code examples

21. Is it of practical use?

22. DCI as inspiration

23. How would it look as
DCI?

24. Thanks!