D4mations.com

IOC + Javascript



Recorded at SpringOne 2GX 2012 in Washington, DC
Speakers: Brian Cavalier and John Hann
Thicker web clients and server-side JavaScript create complexity that must be managed through architectural patterns. JavaScript hasn’t yet embraced lessons learned from other platforms, like Java+Spring. Existing JavaScript MVC frameworks are too rigid and lack sufficient architectural plumbing. Javascript needs flexible architectural infrastructure for building bigger, better apps.

In this talk, Brian and John will introduce several concepts, including JavaScript Modules and Inversion of Control, and demonstrate how they alleviate many of the dominant problems encountered when building large JavaScript apps. Attendees will gain a firmer understanding of new architectural patterns and witness tangible examples of how these patterns improve testability, refactorability, composability, division of work, and team scalability.

Original source

d4mer

, , , , , , ,

6 responses to “IOC + Javascript”

  2. Hey Karolis! That's a very valid question. In general, yeah, we've found that doing composition testing at one or more levels above unit testing is a good approach. We've done that with custom test harnesses, but also with Selenium for functional testing. We're also working on some features that will allow mocking components in the IOC environment, to make composition testing using IOC easier.

  3. Awesome talk and cujo is an exciting project!

    I have one question regarding the IOC containers. It seems you've moved a lot of logic into the IOC container. But now those IOC containers contain very intricate configuration details about how the components work. You can now more easily unit test leaner modules, but how do you make sure the IOC configuration is right. I suppose, it comes down to writing higher level acceptance tests that test the entire wired component.

Leave a Reply