48 reputation
4
bio website
location United States
age
visits member for 1 year, 10 months
seen Oct 12 '13 at 19:03

Jan
11
accepted Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
Jan
11
comment Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
Well written and extremely helpful! So regarding maintenance of dependencies, especially when it comes to third party software libraries, is your policy to support multiple revisions (versions) of those libraries or does your team make an effort to use your latest build available of those dependencies? For example, if Tomcat needs one version of commons-lang and ActiveMQ needs another. Do you schedule refreshes to update your artifacts from time to time by merging your code with the community or is it more of a "update it when the build or test breaks" thing?
Jan
10
comment Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
@JimmyHoffa oh, I see how you're confused. I certainly don't mean they code everything from bare-metal up from scratch. Not even Microsoft does that. I mean, are there any companies that run a software infrastructure platform that is built (compiled, linked, tested, packaged) in-house from source versus relying on community binary distributions. I do know that Google's servers run their own Linux distribution with kernel patches, which of course they do build from source. All the code is in Perforce along with Gmail code and everything else they write and it's all tested continuously.
Jan
10
revised Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
added 58 characters in body
Jan
10
comment Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
"Software infrastructure stack" = Production application server infrastructure. For example, building an application server, building monitoring tools, building the OS (kernel, userland stuff, etc)
Jan
10
revised Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
added 54 characters in body
Jan
10
comment Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
I understand that Google does this. Are they unique? From what I've researched, it takes a lot of maintenance but it is sustainable because their applications are structured with a level of homogeneity: they are written in either C, Java, Go, JavaScript, and Python and with strict coding guidelines. The infrastructure required to support their applications relies on only a few third party components (even Java).
Jan
10
asked Can an entire software infrastructure stack be built entirely from source in-house? Is it practical and sustainable?
Jan
4
awarded  Editor
Jan
4
revised What can a company do to restrict offsite contract developers from redistributing GPLv2-licensed code modifications?
added 213 characters in body
Jan
4
awarded  Scholar
Jan
4
accepted What can a company do to restrict offsite contract developers from redistributing GPLv2-licensed code modifications?
Jan
4
awarded  Supporter
Jan
4
comment What can a company do to restrict offsite contract developers from redistributing GPLv2-licensed code modifications?
It is this specific answer in the GPL FAQ that raised the concern. Indeed, the contractors are work for hire and we're preparing for discussion with our staff attorneys on the matter, including a recommendation to consult with an attorney with special experience with GPL matters.
Jan
3
awarded  Student
Jan
3
asked What can a company do to restrict offsite contract developers from redistributing GPLv2-licensed code modifications?