4 ms·

That cuts both ways. It's a great reason for government to want microservices, but it's also a great reason for contractors to never even present them with that

That cuts both ways. It's a great reason for government to want microservices, but it's also a great reason for contractors to never even present them with that option.

Jtsummers 6y ago
I once worked on a project (US DOD) that was basically a conversion from monolith to SOA. The contractors did, in fact, fight tooth and nail to keep it from happening because it would reduce their apparent value and necessity. USAF totally fucked up the management of it (at the time I was involved), other services had similar projects which had much better transitions. And for them it substantially reduced costs and decreased time-to-feature. USAF just seems dead set on using the old block release style (big bang releases every 12-60 months) which was at odds with the attempted conversion and helped the contractors persist their miserably awful architecture that practically ensured another few billion in revenue for them.
- datavirtue 6y ago
  Nearly every substantive function with defense departments is conducted by contractors. Hence, all they know is waterfall because, precisely as you mention, it is easy for them to game more revenue. A LOT more revenue. Now picture one of these contractors being Boeing. They don't just sell military hardware. They sell the software and systems used to get ANY data out of that hardware. Wartime decisions are made based on that data.
nonameiguess 6y ago
Yeah, totally. I'm anonymous enough here and not going to out my former employer, but one of the things that turned me off and a reason I'm not there any more was finding email trails intentionally suppressing findings from trade studies suggesting the government could get applications deployed faster and cheaper if they didn't use the ridiculous giant framework we'd managed to rope them into years earlier.

4 ms·

That cuts both ways. It's a great reason for government to want microservices, but it's also a great reason for contractors to never even present them with that

by mumblemumble 6y ago

That cuts both ways. It's a great reason for government to want microservices, but it's also a great reason for contractors to never even present them with that option.

Jtsummers 6y ago
I once worked on a project (US DOD) that was basically a conversion from monolith to SOA. The contractors did, in fact, fight tooth and nail to keep it from happening because it would reduce their apparent value and necessity. USAF totally fucked up the management of it (at the time I was involved), other services had similar projects which had much better transitions. And for them it substantially reduced costs and decreased time-to-feature. USAF just seems dead set on using the old block release style (big bang releases every 12-60 months) which was at odds with the attempted conversion and helped the contractors persist their miserably awful architecture that practically ensured another few billion in revenue for them.
- datavirtue 6y ago
  Nearly every substantive function with defense departments is conducted by contractors. Hence, all they know is waterfall because, precisely as you mention, it is easy for them to game more revenue. A LOT more revenue. Now picture one of these contractors being Boeing. They don't just sell military hardware. They sell the software and systems used to get ANY data out of that hardware. Wartime decisions are made based on that data.
nonameiguess 6y ago
Yeah, totally. I'm anonymous enough here and not going to out my former employer, but one of the things that turned me off and a reason I'm not there any more was finding email trails intentionally suppressing findings from trade studies suggesting the government could get applications deployed faster and cheaper if they didn't use the ridiculous giant framework we'd managed to rope them into years earlier.