Reply to: Which J2EE gig to choose??

[Mosh]

On what you've listed above, impossible to say.

I wouldn't base my decision on technology alone these days. What "industry" are these in? I'd base my choice much more around the industry segment than the technology, as every tom, dick and harry Indian is selling themselves - cheaply - based on their tech. skills these days (whether they actually have those skills or not.)

Cheers,

Nomadd

Option 1 : Media
Option 2: Utilities

[nomadd]

Hi Guys ,

I have two choices for my next gig.

Option A :
Tech : ESB , App servers , Spring , Hibernate
Paying : £ X
Commute: 20 minutes
Initial duration: 6 months (could be long term)


Option B:
Tech: Web Services , Spring , Hibernate , Struts , JSP
Paying: £ (1.142X)
Commute : 20 minutes
Initial Duration: 6 months (could be long term)

Both of them are big names in the UK. Any comments to help me decide will be much appreciated.

On what you've listed above, impossible to say.

I wouldn't base my decision on technology alone these days. What "industry" are these in? I'd base my choice much more around the industry segment than the technology, as every tom, dick and harry Indian is selling themselves - cheaply - based on their tech. skills these days (whether they actually have those skills or not.)

Cheers,

Nomadd

[basshead]

That quote implies you don't. An ESB essentially boils down to intelligent use of durable message brokers, SOA and async-messaging.

Unless you are fully comfortable with that, I'd suggest you are about to wreck someones project. Designing and implimenting a service bus isn't about a single product and isn't something you learn on the fly.

So, if the role is more architect than development, i'd take option 2 if I were you.

TM

'An ESB' is or can be different to 'ESB' in that 'An ESB' can be an element in your SOA toolkit, a means of achieving a Service Oriented Architecture. 'ESB' is more a concept and architectural pattern, combining asynchronous messaging, message routing, transformation etc. Many vendors label their products as ESB so you can therefore have experience in one or other of them.

Isn't learning on the fly a key capability of any successful contractor?

I would lean toward option 1 on a technology basis if that's your main criteria, although I would also look into the companies themselves and form an opinion based on the people you met at interview and how the environment seemed. But then option 2 is more money

[Mosh]

That quote implies you don't.
TM

Not quite sure how you came to this conclusion. You dont know anything about my skills or background. Further, this comment also seems to suggest that the people who interviewed me (3 rounds) were complete idiots who did not have a clue about the technology or the project.

An ESB essentially boils down to intelligent use of durable message brokers, SOA and async-messaging.
TM

Really !!! So you are saying that we dont need other protocols such as Http/SOAP/Rest?? And we never use sync messaging in SOA solutions???

Anyways , you are entitled to your opinion. Thanks for replying though.

[themistry]

I do have prior experience in Enterprise service bus

That quote implies you don't. An ESB essentially boils down to intelligent use of durable message brokers, SOA and async-messaging.

Unless you are fully comfortable with that, I'd suggest you are about to wreck someones project. Designing and implimenting a service bus isn't about a single product and isn't something you learn on the fly.

So, if the role is more architect than development, i'd take option 2 if I were you.

TM

[SuperZ]

ESB --> Enterprise service bus

Ta for the correction

[d000hg]

Take both, subcontract one to my company and a remote developer will do it.

[Mosh]

are you seriously going to go for a less well paid contract because you get experience in "ESB"..whatever that is..

I am confused because Option 1 project involves lots of middleware and integration tech that I have been wanting to work on for some time now. I do have prior experience in Enterprise service bus (that's why I got the gig !) , it's just that I wanted to build on that.

[minestrone]

Enterprise Server Bean old bean.

OP should take neither, sock puppets can`t develop.

Enterprise Service Bus.

[SuperZ]

Did you check out the coffee and the toilets at each site? Did you find out if the stationary cupboard is locked?

And the girrrlllieeeesss, always a bonus

[swamp]

Did you check out the coffee and the toilets at each site? Did you find out if the stationary cupboard is locked?

[Mosh]

are you seriously going to go for a less well paid contract because you get experience in "ESB"..whatever that is..

ESB --> Enterprise service bus

[SuperZ]

Enterprise Server Bean old bean.

OP should take neither, sock puppets can`t develop.

[RichardCranium]

are you seriously going to go for a less well paid contract because you get experience in "ESB"..whatever that is..

I agree. I am not a fan of Fuller's products. But if they are providing it for free, I might get to like it.

[BlasterBates]

are you seriously going to go for a less well paid contract because you get experience in "ESB"..whatever that is..