Recently a friend discovered this blog. She asked me why do I write so much about Expressive Design. This is not the first time I’m asked this so I decided to write down my answer. I will try to give some overview of the topic and link to the many articles in this blog about […]
Archive for the 'soa' Category
Expressiveness Omnibus
Published by December 19th, 2010 in abstractions, books, components, domain driven design, domain specific languages, enterprise architecture, layers, object orientation, soa, software architecture, software design, systems integration and trends. 2 CommentsSome Thoughts on Database Integration and Domain-Driven Design
Published by October 4th, 2010 in case study, components, domain driven design, enterprise architecture, layers, object orientation, soa, software architecture, software design and systems integration. 3 CommentsLetting two systems share a single database is one of the worst, most heavily coupled methods for systems integration. Unfortunately it’s also one of the most popular. It is very usual for a developer to have to talk to someone else’s database and quite commonly this accidental complexity cannot be removed as there’s often too […]
ThoughtWorks Australia TeamHug 2010: Why Enterprise Architectures Suck
Published by September 12th, 2010 in abstractions, components, domain driven design, enterprise architecture, events, layers, management, object orientation, soa, software architecture, software design, systems integration, thoughtworks and web. 3 CommentsWe just had our ThoughtWorks Australia Team Hug. It’s some sort of internal conference where everyone from Sydney, Melbourne, Perth and Brisbane get together with some guests from overseas to get drunk (by the way, we are hiring). We also have presentations and many other work-related sessions.
This year I’ve held a session on a quite […]
Thoughts on Abstractions: Part 2 – Abstractions in Your Domain
Published by September 6th, 2010 in abstractions, books, components, domain driven design, layers, object orientation, soa, software architecture and software design. 2 CommentsAs we saw in Part I, abstractions are everywhere. Unfortunately, even though everyone is more than happy to reuse abstractions provided by someone else I often see people failing to identify those in their own code.
Most people tend to create abstractions found using Russ Abbott’s method of using the textual description of a problem to […]
Agile Anti-Patterns: Democratic Design
Published by May 9th, 2010 in agile, components, java, layers, object orientation, ruby, soa, software architecture and software design. 5 CommentsWeeks ago, some people in the Ubuntu community got a bit disappointed with the distribution’s core team:
> We are supposed to be a community, we all use Ubuntu and contribute
> to it, and we deserve some respect regarding these kind of decisions.
> We all make Ubuntu together, or is it a big lie?
We all make […]
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 CommentsSome 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 […]
Gö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. 9 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. 5 CommentsEven when working for an agile software development company you may be required to write an architecture spec. It may be a client requirement 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 situation is that she needs […]
