Service Component Architecture (SCA) is the marriage of these two things. It essentially recognizes that some of your building blocks are going to be local, others are going to be external, all of them need to be as reusable as possible, and their internal/external exposure may change over time. In other words, it’s a SOA orchestration of services that is a fluid hybrid between the two worlds. Your code will periodically use a @Service tag to declare a service dependency. And some XML configuration file will help map out the ESB-specifics of (a) exposing necessary services or service compositions to the outside and (b) getting access to outside service dependencies that you’ll need.
Over the past several years I’ve become wildly enthusiastic about certain “trends” in software development that promote clean, agile, distributable code. The primary buzzwords I’m referring to are “SOA” (Service Oriented Architecture) and “Dependency Injection”. Heck, I’ll even throw “SOAP” into the mix, even though that’s a more specific protocol.
If I talk to other developers about these things, they look at me funny or they show disinterest or suspicion. I think some people think I’ve gone crazy over some trendy buzzwords (i.e. pointy-haired-manager syndrome) and am just trying to evangelize some lame trend that will come and go. Or there’s the classic “SOAP? Oh yeah, I tried to do something with that and got so confused and just hated it. *shiver*”
(By the way, SOAP may have some hard-to-parse standards, and the WSDL can be daunting and confusing, but it’s really simple: you are taking your XML request and wrapping it in a simple envelope that is often nothing more than a single parent <soap> tag! There are some provisions for allowing messaging meta-data to be added in a header section, but all that stuff is optional. Anyway, if you are one of those people who is afraid of SOAP, take a second look; it’s not all that bad.)
Dependency Injection and Service Oriented Architecture are interesting topics in that they really should be easier to explain. I’ve read so many books and articles, and authors have written a lot of insightful material, but I haven’t run into anyone who has been able to expose the inherent simplicity behind these things. Well, I might my hand at the task someday, but not in this blog posting. My purpose is a bit more specific… to share an insight about Service Component Architecture. Continue reading “What’s special about SwitchYard? It’s SCA.”
Switchyard takes Web Services to the next level. Whereas JAXB2 and JAX-WS (and JAX-RS) have brought the development and deployment of Web Services to the necessary level of maturity for clean, easy and practical development, Switchyard let’s us take things to the next step: it makes Web Service Composition similarly clean and easy. And with Web Service Composition comes the entire arsenal of SOA Design Patterns.
I’m sure everyone right now thinks the biggest advances in the computer industry today are Social Media and the iPad. Or maybe they were last year’s big news and there’s something I don’t know (or yet care) about that just appeared in SXSW this year. Well, as much as I’m still chomping at the bit to do a little iOS development (I still watch the Stanford class lectures from iTunes U on my iPhone while I run the elliptical at the gym at 5:30am every morning!) I’m actually really the most excited about something else. And when I mean excited, I mean that first thing every morning I’ve been checking the JIRA “open tickets” report to see how the countdown is going. I’m talking “kid counting the days to Christmas” sort of behavior.
The countdown to what? Well, I’m glad you asked. I’ve been waiting since about November for the countdown to the release of the 0.4 version of JBoss Switchyard. Continue reading “Dependency Injection + ESB = SwitchYard (Coolest New Thing This Year)”