Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Hartmut Wilms on Sep 11, 2008
As the Professional Developers Conference (PDC) 2008 draws near, Douglas Purdy, Don Box and others are dropping some information about Microsoft Oslo.
Until recently Oslo has been one of the best kept secrets by Microsoft. There have been many rumors about Oslo being Microsoft’s future SOA strategy, distributed application server or Microsoft’s next unified SOA product portfolio. Finally, Douglas Purdy, Product Unit Manager for Oslo, announces, that he will be talking about Oslo and its technology at the PDC. In his announcement he states that “Oslo is just the modeling platform”:
To that end, we have boiled down Oslo to three very simple things:
- A tool that helps people define and interact with models in a rich and visual manner
- A language that helps people create and use textual domain-specific languages and data models
- A relational repository that makes models available to both tools and platform components
That is it. That is all Oslo is.
Although the scope of Oslo seemingly does not live up to expectations, Douglas adds that “the impact of this platform on software development and management will be transformational” and that for him “Oslo is the first step in my vision ‘to make everyone a programmer (even if they don’t know it)’” .
Don Box joins in and explains the goal of Oslo as “to make it possible to build real apps purely out of data”:
We’re building “Oslo” to simplify the process of developing, deploying, and managing software. Our goal is to reduce the gap between the intention of the developer and the actual artifacts that get deployed and executed. The approach we’re taking is to move more of the definition of an application into the world of data, where we (and you) can more easily make queries as to the developer’s original intent.
According to Don all data, which define services, applications and processes, will be available both at development and runtime . Oslo will provide several schemas for target platform components that are ‘instantiated’ by these data. Data will be stored in a relational database by default, but Oslo is not limited to the relational model. Actually Oslo’s modeling language is built against an abstract data model.
In his article on eWeek Darryl Taft interviews Don Box, Steven Lucco and Brad Lovering, Oslo’s technical lead, who explains Oslos emphasis on a data-driven approach and delves into the details of the role of the D (modeling) language in the Oslo effort. Read the details in the eWeek article.
In the dawn of Oslo there might be some uncertainties regarding the future of core components of .NET Framework. Nicholas Allen eases concerns on possibly diminishing support for WCF and WF as these will remain the foundation of Microsoft’s distributed computing platform. In his post on Oslo he says:
What Oslo doesn't change is what your services can actually do. There's nothing forcing you to start modeling your applications to make use of features in the Microsoft frameworks. Modeling is a tool that is supposed to enhance the productivity of developers and IT professionals rather than be the single way to do things.
The first bits of Oslo will be released as a community technology preview (CTP) at the PDC in October 2008.
Right Collaboration Architecture Drives Business Transformation
The 5 Mandates of Software Development Teams - Presto Manifesto
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
... they're making Access all over again
I think Lovering's comparison with Access and Excel is misleading, as he admits himself. The textual DSL approach, and the LISP and ML approach to application development, which have influenced the language D, hint at something that goes beyond "clicky" RAD-Tools ...
A language that helps people create and use textual domain-specific languages and data models
sounds rather as something like Jetbrains MPS.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
3 comments
Watch Thread Reply