Chapter 13. Tuscany runtime architecture
This chapter covers
- The architectural building blocks that make up the Tuscany runtime
- The complete flow of how Tuscany processes an SCA application
- The key patterns that make the Tuscany runtime flexible and extensible
Throughout this book we’ve promised that Tuscany handles the complexity associated with integrating various technologies in a distributed environment. You focus on developing your business logic and Tuscany handles the rest. This chapter explains the details of Tuscany’s flexible architecture and reveals how the complexity is handled.
This sounds like a chapter that should appear at the start of the book. But if you’re a user of Tuscany and SCA and you just want to build SCA applications, you don’t necessarily need to know how the Tuscany runtime itself is architected. It’s useful to know, though, if you intend to embed or extend Tuscany for use in your environment. The content of this chapter gives you a high-level understanding of the architecture of the Tuscany runtime but with sufficient enough detail so that in the next chapter we can explain how to build Tuscany extensions.