I have tried for the last couple of days to overcome some of the transaction management problems I was having with Rails, and the more I look at it, the more I am convinced Rails is not right for my trading application. Rails has its sweet spot, and for me, there won’t be anymore PHP.
I was reading yesterday the tutorial for the Globus Toolkit 4 (GT4), especifically this and this page. It highly disturbs me. Something is not right. It reminds me of the CORBA, and early day’s of EJBs. 90% systems programming, for 10% application programming. Thankfully AOP, Spring, Hibernate and friends kicked in to help, and introduced Inversion of Control to the masses. Hollywood’s principle for everybody.
Scarcity is a requirement for a good to be economic. However, http://www.onethousandpaintings.com/ offer something that could be offered by thousands of artists out there. So, it is not scarce. Or is it?
Transactions in Rails are starting to bother me, and quite a lot. Once in a while I dive into my latest application,booki.es, a web application for trading long-term futures using play money.
SOA means a lot of different things to different people. Now, if I go by the W3C’s definition, it’s about processes that assemble services and an organisation that owns the processes and the services.