Diary of a Fence Sitting SOA Geek
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
- SOA,
Tracking change and innovation in the enterprise software development community
Posted by Floyd Marinescu on Jul 05, 2006 10:14 AM
Released today, JRuby 0.9 can now run RubyGems, the WEBrick Ruby HTTP server, and Ruby on Rails (on WEBrick). JRuby co-lead Thomas Enebo told InfoQ that Rake also recently started to work. JRuby 0.9 also includes a number of bug fixes, an improved YAML parser thanks to JvYAML and RbYAML projects, and all non-native standard libraries are bundled in the JRuby distribution.We want to have another release near the end of this summer (end of August). We made a promise at JavaOne that we would completely support Ruby on Rails and we want to:
1. Fix more incompatabilities so Rails runs better.
2. Speed up JRuby to make it more attractive as a Rails environment
3. Provide a JEE-backed deployment option for Rails. This will start with a servlet acting like a fast-CGI.
Offshore software development: Making it a success with Agile Practices
Spring App Platform, Java Concurrency/Multicore, Eclipse Mylyn and more @ QCon SF Nov 19-21
The Future of Software Delivery According to visionaries Grady Booch & Erich Gamma
Five Ways to Fail When You Scale
Ruby VMs, Scaling Rails, YellowPages.com on Rails, Merb @ QCon SF Nov 19-21
I think this is great news. I've been writing Java apps for years and have recently started looking at RoR for a few small applications (in-house and external) and it's nice to get that productivity shot-in-the-arm for crud apps at the very least. I've held back on doing too much in the past because I found that I missed a lot of the functionality that I'm accustomed to in Java, but I'll definitely be investigating this further.
Over the past year I've fallen in love with Ruby. While I haven't done much with Rails yet, I've fallen in love with the Ruby Way. One thing that has always seemed problematic was the very "native" approach used for the Ruby database integration (typically achieved via the 'DBI' library and associated 'DBD' drivers). While vendors are very likely to produce JDBC drivers for their databases, I'm unaware of any "big players" (Oracle, SQL*Server, Informix, DB2, Cache, Sybase, etc.) providing direct Ruby DBI/DBD support. While ODBC helped a bit here, I found getting ODBC (and drivers) to work on non-Windows platforms to be less than trivial.
With the advent of JRuby, we have the option of using the JDBC API to access virtually any database platform. I think it would be very beneficial if the JRuby project came up with some sort of transparent DBD-to-JDBC driver that would allow Ruby code to transparently use any JDBC driver just like a "regular" DBI/DBD driver.
Congratulations everyone... This is a very exciting development!!
In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.
Platforms need interoperability. In this article Flex interoperability with JSON and XML is explored including direct mapping to chart and grid components.
Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.
In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.
David Laribee discusses the purpose of ALT.NET, its mission and future.
Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.
Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.
Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.
2 comments
Reply