Some weeks ago I joined a handful of ThoughtWorkers invited to test the new Google AppEngine’s Java API. Unfortunately I had a project requiring a lot of attention during most of this period but once back on the beach I found some time to play around with it.
Cloudy Skies
Google AppEngine (GAE) is Google’s shot in […]
Archive for the 'soa' Category
Getting Cloudy: Clojure on Google App Engine
Published by April 8th, 2009 in business, case study, clojure, cloud computing, components, groovy, java, lisp, soa, software architecture, software design, thoughtworks, trends and web. 8 CommentsGödel and Testing
Published by March 14th, 2009 in agile, books, clojure, components, layers, lisp, soa, software architecture, software design and web. 12 CommentsFor some months now I’ve being playing around the idea of writing a testing framework for Clojure. It started as just a more extensible fork of the fact library but now I’m trying to explore some funny ideas in the testing semantics.
Although this project is progressing too slowly it already spawned some other pet […]
What Is a Service?
Published by February 24th, 2009 in business, components, domain driven design, layers, soa, software architecture, software design, trends and web. 8 CommentsMore and more people are deploying Services, APIs and all kinds of distributed components. Major content providers are finally finding out that exposing their features to developers not only keep them relevant but also creates a nice ecosystem around their business.
When someone decides to expose a piece of software to others –being internal users in […]
Clouds: Solo and the Department Store
Published by January 23rd, 2009 in business, cloud computing, rails, ruby, soa, software architecture, trends and web. 0 CommentsI really like Amazon WebServices. I think they provide great and innovative features with an affordable price. I also like Engine Yard. Their plans are too expensive for most users but their commitment to a better open-source platform is remarkable. And I think they made a pretty interesting move in their new Solo offering.
Solo […]
Trying to Write Architecture Specs that Don’t Suck (much) - Part I: The Spec
Published by November 7th, 2008 in agile, object orientation, soa, software architecture, software design and web. 4 CommentsEven when working for an agile software development company you may be required to write an architecture spec. It may be a strong client requirement that you can’t bypass or may be something required in an RFP; once in a while you have to write something like this.
The first thought of someone in this […]
The Theory we Forget: Proper Packaging
Published by September 16th, 2008 in books, components, layers, object orientation, soa, software architecture and software design. 7 CommentsIn a recent development project the team has decided to create two versions of the same generated artifact -a JAR file containing a message-processing framework that other systems will use. The full JAR would depend on weblogic.jar, a 50+MB gorilla, but as the features that create this dependency are not used by all our […]
Johnny Chung Lee, the Wii and Domain-Specific Languages
Published by June 2nd, 2008 in Uncategorized, domain driven design, domain specific languages, fluent interfaces, java, language adaptation, language oriented programming, object orientation, ruby, soa, software design, thoughtworks and trends. 0 CommentsI’m attending JAOO in Sydney. Today’s most interesting presentation was by Johnny Chung Lee, a Internet Celebrity(tm) with some of the most viewed videos in youtube and a researcher in human-computer interaction.
Johnny gave a brilliant talk and stressed the fact that although we have better graphics nowadays we still suck at how to interact […]
Australian Architecture Forum Slides
Published by June 2nd, 2008 in case study, soa, software architecture, software design and thoughtworks. 1 CommentI’ve presented at the Australian Architecture Forum a couple of weeks ago. It was a very nice opportunity to get an overview of what the Australian software development market looks like outside ThoughtWorks.
The presentation was a case study on a previous project where we changed a legacy architecture from a completely ad-hoc structure to a […]
