OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Modern Software Infrastructures Revisited

Igor Bogicevic (igor.bogicevic@sbgenomics.com)

January 29, 2011

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Introduction and Axiomatics

I Complexity of a software does not reduce over a time.

I Features, robustness of code, scalable architecture are indeed increasing thequality of software, but are also increasing complexity.

I Refactoring, as a good practice, does not reduce complexity, but it merely paysfor a technical debt.

I In environment where multiple components mutually depend complexity canexplode.

I Moreover, complexity is not related to a sandbox of mutual dependencies, butalso on the production environment as well.

I Embracing and controlling the complexity might be a better way.

I Integration complexity != Code complexity

I Integration complexity � Code complexity

I Infrastructure complexity != Code complexity

I Infrastructure complexity � Code complexity

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

What is the ”Software Infrastructure”

I infrastructure - noun: the basic, underlying framework or features of a system ororganization.

I software - noun: ...

I Yes, I made up this one...

I In my defense, I needed a glue term that will somehow connect softwarearchitecture, infrastructure, build and deploy process

I ... configuration distribution, monitoring/alerting

I ... dispatching of system updates, server orchestration

I No, that’s not ”Information System”.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scope Of The Problem

I Hardware didn’t became cheap, however it became cheap enough.

I Operating system became a commodity.

I What was sometimes a privilege of the few, became approachable to a largeraudience.

I An organic transformation - with more traffic and content, there was more dataavailable to use.

I After certain point, you need to re-think how are you storing and processing yourdata.

I Once you get to the ”internet scale” of data, this becomes inevitable.

I Scaling up the data processing heavily depends on the both nature andoperations on top of data.

I That also applies to information retrieval, search on top of data, etc.

I This problem was not new, and concepts and solutions existed on the market -but not as a commodity.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Paradigm Shift

I Complexity moved from the code and software architecture to the infrastructureas a whole.

I New resources are driving both new patterns and paradigm shift.

I Instead of infrastructure being driven by business requirements, in last couple ofyears we have an opposite situation:

I Products and business are starting to be driven by available capacity.

I On-demand infrastructure, in the matter of minutes.

I Dynamic allocation of resources - AWS, Google App Engine, Rackspace Cloud,Joyent SDC, etc.

I As proven again - when you have a hammer, everything looks like a nail.

I Paradigm shift also leads to a new set of pointy-hair semantic and yugioh gradeconversations with appropriate keywords (Cloud, SaaS, PaaS, ...).

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Comic Relief

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Infrastructure Specialization

I We’ve got to the point where we have multitude of paradigms to choose from.

I Many theoretical CS paradigms in distributed computing got to a stage oftransformation to a production ready software.

I Many of them are open.

I To number some: distributed map/reduce, distributed stream computing,distributed analytical search, distributed graph databases, distributedsynchronization.

I Distributed everything?

I Maybe you don’t need to distribute your problem after all.

I In reality we’re struggling with infrastructure design as we’re pioneering goodpractices in the various scenarios.

I This means we have various tools, platforms, paradigms at our disposal, yet we’rehitting various nails with various hammers.

I And this is a call for infrastructure specialization.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Scaling Up

I Scaling should be avoided if possible (as premature optimization).

I ... and in ideal world you would be able to ”throw some money on it” and solvethe problem with vertical scaling.

I ... however that scales only up to certain level.

I Horizontal scaling imposes a new set of problems.

I Horizontal scaling is completely driven by the domain of the problem and data.

I Some of the problems and datasets are trivial to scale (sharding), most of themare not - especially from the standpoint of fault tolerance.

I We are living victims of CAP theorem...

I And large corpus of papers on distributed computing in general.

I Design for a failure - you’ll appreciate when you see your system running.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

Organizational Changes

I No-Product, this is a red area for Product Management.

I Engineering should be empowered to drive the core product.

I Product Management should move back to where it started - driving businessrequirements and articulating BizDev requests.

I ”We can’t hire sufficiently good engineers” is a lousy excuse.

I Either you can’t attract great engineers, or you can’t build them.

I Problem is always in you - figure out what you’re doing wrong.

I No-Ops - BOFH syndrome has no place in an environment with complexinfrastructures.

I Same standards should apply for System Engineers/DevOps as for Engineers.

I What is traditionally considered to be Engineering and Operations should be oneorganizational group.

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

We are hiring!

I We are fresh and well funded startup from Boston, MA.

I We are building a first open on-demand scalable platform for distributed genomicdata processing.

I We’re in a BigData business (10GB-2Tb per genome).

I We have an ambition of becoming a de-facto platform for Bioinformatic dataprocessing.

I We are looking for a talent across several categories:

I - Core Engineering

I - Frontend Application Engineers (python/django)

I - Frontend Developers (html5/js/css)

I - System Engineers/DevOps

I If you’d like to work on a problems of large scale genomics data processing, pleaseshoot me an email: igor.bogicevic@sbgenomics.com

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited

OutlineIntroduction and Axiomatics

What is the ”Software Infrastructure”Scope Of The Problem

Paradigm ShiftComic Relief

Infrastructure SpecializationScaling Up

Organizational ChangesWe are hiring!

We are hiring!

I We are fresh and well funded startup from Boston, MA.

I We are building a first open on-demand scalable platform for distributed genomicdata processing.

I We’re in a BigData business (10GB-2Tb per genome).

I We have an ambition of becoming a de-facto platform for Bioinformatic dataprocessing.

I We are looking for a talent across several categories:

I - Core Engineering

I - Frontend Application Engineers (python/django)

I - Frontend Developers (html5/js/css)

I - System Engineers/DevOps

I If you’d like to work on a problems of large scale genomics data processing, pleaseshoot me an email: igor.bogicevic@sbgenomics.com

Igor Bogicevic (igor.bogicevic@sbgenomics.com) Modern Software Infrastructures Revisited