Sudden, unedited and random observations by Greg Pavlik, software technologist and frustrated adventurer.
Wednesday, June 27, 2007
Tuesday, June 26, 2007
SOA Workshop Presentation
Sunday, June 10, 2007
Greetings from Prague
The interesting takeaway for me was the similarity of the views of the presenters and panelists. I believe this reflects a common experience with customer requirements. This is a particularly good thing, since it means that the SOA hype phase may be over, and now we're getting down to the real value proposition: easier, cheaper application integration, flexible business processes, and better alignment with business objectives.
Tomorrow I have a chance to keynote the main conference. I am planning to dwell on these three topics. In addition, Jon Maron and I are doing a three hour presentation for the Oracle field and customers on the next iteration of the SOA platform. Should be a fun, but very long day!
Addendum (a few notes on Prague): beautiful city with architecture going back to the middle ages. Mostly I have been in hotels or meetings, but the city is extremely pleasing to the eyes and a pleasure to walk around. We managed to do just that a bit and see the prague castle, the old town's powder gate tower and the famous astronomical clock. Ironically, the czechs are renowned for the high percentage of atheist citizens: the houses of worship are really amazing. This morning, we had a chance to explore the Jewish quarter, also fascinating (the Spanish synagogue is not to be missed). St. Vitus's Cathedral rivals Notre Dame as a massive, buttressed church: it also houses the tomb of "Good King Wenceslas".
Monday, May 21, 2007
JBI 2.0, does anyone agree?
OK, now some years have passed: JBI hasn't taken off and now a few vendors are back at the table trying to decide what to do next. Since it's unclear what direction folks will try to take this, I thought I'd poney up a few suggestions on what could make the spec relevant and useful. Basically, get rid of a lot of cruft.
First thing to tackle: the "J2EE for integration servers" looks like it will clearly be SCA. So check SCA support as the standard model for service development. (This seems to be in line with where things are going, or so I thought: Out of the blue, my old friend Mark Little suggests that maybe they will support JBI without SCA. What? Invent a closed, Java specific model for composite services? Enter the matrix indeed!)
Once you build one of these things, it's pretty clear that most of JBI 1.0 can go away. Using SCA and OSGI, you really don't need to do much other than have an interface that passes normalized messages to service engines or binding components. In fact, OSGI provides most of the packaging and injection heavy lifting for building plugins to an SCA/JBI runtime model.
Once you boil down to a few interfaces, then the group could focus on simplifying those interfaces further. Add some management hooks and this is something that could really take off. I suspect this is really what the folks in the Eclipse SRP are really after. All of this suggests that the group could do something genuinely useful: explicitly focusing the JSR as the OSGI based plugin model for Java-SCA platforms.
In sum, narrow the scope, align with industry direction and build some real value additions.
Wednesday, May 16, 2007
Monday, May 14, 2007
The Other Dave on SCA
There is no doubt that adding support for imperative programming models is important for SOA composites. This is where the Java/SCA model makes sense.
But does it matter? My argument all along has been that we should not teach a new model around Java. Everyone is already converging on a common model: the whole Java world is moving toward pojo programming stripped free of the framework cruft. In the first SCA f2f I sat with Rod Johnson and watched him implement some of the annotations in the original SCA JCI spec in a few minutes. SCA frameworks will bootstrap Java code. Write it for Spring and it will be useable in SCA. Or vice versa.
Put it another way: we can bootstrap basic BPEL processes into an SCA environment without changing the BPEL definition because you just use the language. We expect to see the same thing for Java platforms moving forward. If anything, this is the ultimate form of industry convergence.
Dave Chappell joins Oracle SOA team
Update: bookmark Dave's blog here: http://blogs.oracle.com/davidchappell
Wednesday, May 02, 2007
Systems Integration 2007 (Prague, Czech Republic)
Monday, April 30, 2007
Jim Gray Tribute Redirect
Wednesday, April 18, 2007
ICSOC 2007 Call for Papers
CALL FOR PAPERS
ICSOC 2007 seeks original papers in the field of service oriented computing, from theoretical and foundational results to empirical evaluations as well as practical and industrial experiences, with the emphasis on results that contribute to solve the many still open research problems that are of significant impact to the field of service oriented applications. Topics include but are not limited to the following:
- Business Service Modeling: Methods and tools for capturing business goals and requirements, decomposition into business services, business processes, business policies, modeling, analysis, and simulation, specification of functional and non-functional quality requirements
- Service Assembly: Development and discovery, model-driven development, service composition architectures, service registries, service discovery mechanisms, semantic matching, methods and tools for service development, governance, verification and validation, deployment strategies
- Service Management: Instrumentation and service-related data aggregation, end-to-end measurement, analysis, modeling and capacity planning, definition of deployment topology, infrastructure configuration, problem determination for SOAs, ITIL processes, change management in live systems
- SOA Runtime: Service bus for mediation, transformation and routing, runtime development and service registries, integration of legacy applications, information services for data access and data integration, scalability, topology and optimization, service-oriented middleware, policy based configuration & workload management
- Quality of Service: Reliable service-oriented computing, security and privacy in service-oriented computing, SLA and policy specification, QoS negotiation, autonomic management of service levels, empirical studies and benchmarking of QoS, performance and dependability prediction in SOA
- Grid Services: Services and architecture for management of infrastructural resources, data and compute intensive applications, execution and resource allocation services for job scheduling, protocols for coordination across multiple resource managers, business-value based allocation, innovative strategies for creation and management of virtual enterprises and organizations, prototype systems and toolkits
RESEARCH AND INDUSTRIAL TRACKS
There are two independent tracks for research and industrial papers, each managed by a different program committee and with a different set of evaluation criteria. Authors must clearly indicate the track to which their paper is being submitted.
- Research Track: ICSOC 2007 solicits original research papers, which should contain results that advance the state of the art in service-oriented computing, either through theoretical or experimental analysis. The paper should clearly articulate the research contribution and innovations, the relevance to service-oriented computing and the relation to prior research. Submitted papers will be judged according to their scientific merits and evaluated on significance, originality, technical quality, and exposition.
- Industrial Track: ICSOC 2007 solicits submissions covering the state of practice and real-world experience in service-oriented computing, including papers that describe innovative service-based implementations, novel applications of service-oriented technology, and insights and improvements to the state-of-practice. Case studies from practitioners emphasizing applications, service technology, system deployment, organizational ramifications, or business impact are especially welcome. Papers should provide sufficient details on the application domain, and the service-oriented techniques used, the issues surrounding actual implementations and applications, and the lessons learned in the field.
FORMATTING GUIDELINES
All papers should be submitted electronically (in PDF) and prepared in accordance with the Springer/LNCS camera-ready format. Both research and industrial-track papers are not to exceed 12 pages, including references. All submissions should include title, authors, and full contact information.
Submissions should indicate at least two main topics and the scientific area (or areas) that best fit the content of the paper. All accepted papers will appear in the ICSOC 2007 proceedings, published by Springer Verlag as a part of its Lecture Notes in Computer Science series, and must be formally presented at the conference.
Submissions must be made electronically through the ICSOC 2007 Online Submissions Site.
Guidelines for authors on using and navigating the submissions site are also provided.
Thursday, April 12, 2007
So It Goes
Thursday, April 05, 2007
Spring-OSGI milestone
Tuesday, April 03, 2007
Rich Friedman blog found
At some point, we need to organize a feed of ex-Bluestone bloggers....
Monday, April 02, 2007
Bob Bickel blog found
Cool to find he has a new blog. Looking forward to reading it on a regular basis.
Tuscany Multiplies
In many cases, the value of these projects are in the experiments and learning experiences that fall out of the development effort. I'm looking forward to seeing where the different teams take the various branches.
Friday, March 30, 2007
Thursday, March 29, 2007
Philly JUG SCA Presentation
I promised I'd post the presentation slides here. Turns out Blogger only allows image uploads. The good news: Dave is loading the ppt on the JUG site. As soon as that is up, I'll post a link back to it from here as well.
In the meantime, feel free to post follow up questions as comments here or send me an email at greg.pavlik@oracle.com. I'm on the west coast now, so bear with me if you don't hear from me right away.