<< QCon London : day 5 | Home | Pebble gets Ajax'd >>
Twitter RSS feed for Simon Brown [Twitter] simonbrown: Eating cream cakes in the sun at jersey zoo ... chillin'

Coding the Architecture RSS feed for Simon Brown [Coding the Architecture] Just a short note to plug a handful of sessions that Kevin and I are presenting at the upcoming Software Architect 2008 conference, 3rd-5th June, London. 1. Coding the Architecture : From Developer to Architect The first is a re-run of our ...

Do you need a Java architect?

Yes, I think you do

I've organised a couple of unconference sessions in London over the next few weeks, with the purpose of discussing what it means to be an architect on a Java project. Doing such a session in a traditional presentation style wasn't really an option because there are very few right or wrong answers when you start talking about this stuff. Instead, I want to us (myself and some of the other architects I work with) to share our own *experiences* of doing this type of work in the city.

Having worked with and coached aspiring architects, it's clear to me that many people see the role as a mystical thing that they don't know how to get to. So on the one hand, I want to demystify exactly what I think it means to be an architect. Having said this, I also want to share my experiences about some of the complexities and responsibilities of the role, because they help ensure the success of the project and its chosen architecture.

There's no set agenda for these sessions but I'm hoping that people want to talk about a mix of the technical and non-technical aspects of being an architect. I'm really looking forward to it and if you're looking at a career in software architecture (particularly with a Java focus), I recommend that you come along. Full details can be found at The Pragmatic Architect sessions in London. If you can't make either of these but are interested in us running another session (either publically or privately, inside your company), please do get in touch.

Do you need a Java architect? Yes, I think you do.



Re: Do you need a Java architect?

While I agree that the answer is that you need a Java architect I often wonder what that means about JEE. Many companies are scrambling to put together a cohesive set of tools for enterprise applications. It would seem that the Java community is missing a standard set of tools. I for one see this as an added cost but also as a required feature. I prefer to have the flexibility and choice of architecture as opposed to being crammed into something like the .NET solution.

Re: Do you need a Java architect?

I mentioned this in my talk at QCon a couple of weeks ago. It'll be interesting to see whether the Java world fragments, not at the language level, but the way in which we use it. It seems there are various camps at the moment : standards based (e.g. Java EE, web services), lightweight alternatives (e.g. Spring, Hibernate, REST, etc) and Eclipse (e.g. SWT, RCP, EclipseLink, etc). In effect, you almost have multiple standard sets of tools.

Re: Do you need a Java architect?

I think you rather need an architect than a Java architect. Enterprise architecture should be about the big picture not about a specific technology or even programming language - that's the job of senior developers.

Re: Do you need a Java architect?

I agree with your comments about enterprise architecture - this is more about strategy than technology. I do, however, think there's a need for an application or system level architect. Of course, this is a role and could be performed by a senior developer.

Re: Do you need a Java architect?

I too agree that the term Java 'Architect' is a little misleading. Software and Systems architecture is way beyond the realms of any single programming language. There are two key words here "Java" and "Architect" this would implicate Java as being the platform of choice without any questions asked. Despite personally being a fan of Java I do not like the prospect of having my options being cut from the outset ! I'm very tired of seeing enterprise applications built by 'Architects' with the narrow mindedness to ever consider how a junior Java developer straight out of college will maintain their code.

Re: Do you need a Java architect?

I agree that software and system architects need to have a broader skillset that covers multiple technologies, although I do think that there is a place for a Java architect. By this, I mean an application architect with a specialism in Java.

I think this is perhaps more applicable in a consulting environment. For example, some of our customers have already chosen Java as a core part of their technology strategy going forward, and they do genuinely need architects that specialise in Java. Also, "Java" could now mean anything from standalone JVMs with Spring and Hibernate through to full stack Java EE. It's a vast landscape.

"Java EE architect" ... not any more. "Java architect" ... yes.

Add a comment Send a TrackBack