xtreme deployment
Post on 16-May-2015
1.391 Views
Preview:
DESCRIPTION
TRANSCRIPT
/
Xtreme Deployment
develop in production; push to dev
Tuesday, October 2, 12
Who are we?
Brian ClapperCTO of CirconusWhipping boy of the modern SaaS stack.
Theo SchlossnagleCEO of CirconusRepeat denier of reality.
Tuesday, October 2, 12
How the world used to look (less xtreme)
Architectures driven by user interaction:(e.g. web page load ➠ web page response)
Tuesday, October 2, 12
How the world used to look (less xtreme)
isolateduser A’s page load doesn’t effect user B.
latentuser A’s affect shows up “later” in user B’s view.
Tuesday, October 2, 12
How the world used to look (less xtreme)
Problem reproducibility is achievable(even if sometimes painful)
Tuesday, October 2, 12
How the world looks now (more xtreme)
Architectures driven byhigh volume data and users
Tuesday, October 2, 12
How the world looks now (more xtreme)
every piece of data entering the architecture can effect a user’s subsequent experience.
Tuesday, October 2, 12
How the world looks now (more xtreme)
sometimesthe data must effect a user’ssubsequent experience.
Tuesday, October 2, 12
How the world looks now (more xtreme)
Social systems cause indirect impactvia user action eroding isolation.
Tuesday, October 2, 12
How the world looks now (more xtreme)
A more responsive web is erodingusers’ acceptance of latent state.
Tuesday, October 2, 12
How the world looks now (more xtreme)
Highly distributed systems(due to complexity and scalability) meansno single world state
Tuesday, October 2, 12
How the world looks now (more xtreme)
Highly distributed systems(due to complexity and scalability) meansdifficult repeatability of state and failures
Tuesday, October 2, 12
How the world looks now (more xtreme)
Highly distributed systems(due to complexity and scalability) meanstreacherous debugability
Tuesday, October 2, 12
Despair all ye’ who debug here
I studied distributed systems long enoughto understand “the suck” you do not wish to have in your lives.
Tuesday, October 2, 12
Despair all ye’ who debug here
Expedient debugging requires a quick realization of a precipitating state of failure.
Tuesday, October 2, 12
Despair all ye’ who debug here
In distributed systems,post-mortem techniques are less useful because recreating possible global state is amind-bending (or brain-damaging) exercise.
Tuesday, October 2, 12
Despair all ye’ who debug here
Applying older techniquesto small controlled distributed systemsis still feasible,but complex, asynchronous architecturescan be nearly impossible.
Tuesday, October 2, 12
Some context about us
Circonus ingests telemetry dataacross an entire business
Tuesday, October 2, 12
Some context about us
alerting • correlation • visualization • analytics
Tuesday, October 2, 12
How we see the world today
High velocity non-user-generated data inflow.
Tuesday, October 2, 12
How we see the world today
Users expect sub-second reflection ofall input data and drawn-conclusions.
Tuesday, October 2, 12
How we see the world today
Users expect extremely high availability(100%, you can only disappoint)
Tuesday, October 2, 12
How we see the world today
I was surprised howimpatient and demanding users are...
until I used the tool...and felt exactly the same way.
Tuesday, October 2, 12
Circonus architecture
Voltron
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
• distributed data ingestion (via aggregators)
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
• distributed data ingestion (via aggregators)
• distributed data distribution! (via message queueing)
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
• distributed data ingestion (via aggregators)
• distributed data distribution! (via message queueing)
• distributed data storage (via snowth)
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
• distributed data ingestion (via aggregators)
• distributed data distribution! (via message queueing)
• distributed data storage (via snowth)
• distributed streaming fault detection (via muppet love)
Tuesday, October 2, 12
Circonus architecture
Voltron• distributed data collection (via brokers)
• distributed data ingestion (via aggregators)
• distributed data distribution! (via message queueing)
• distributed data storage (via snowth)
• distributed streaming fault detection (via muppet love)
• ... distributed nightmare.
Tuesday, October 2, 12
Despair actualized
I shall not memorialize this in slides.
Tuesday, October 2, 12
Despair actualized
I shall only cry in front of you now.
Tuesday, October 2, 12
Hope (keys to the city)
• Leveraging• stream mirroring and• idempotent behavior.
Tuesday, October 2, 12
Hope
Allows for the recklessness that we all appreciate in a no-consequences development environment...
Tuesday, October 2, 12
Hope
withproduction data,production volume, andproduction “personality.”
Tuesday, October 2, 12
Hope actualized
Development In Production
Tuesday, October 2, 12
Hope actualized
Ex #1: Dual storage backends
Tuesday, October 2, 12
EXPLORATION
PostgreSQLTuesday, October 2, 12
EXPLORATION
SnowthTuesday, October 2, 12
EXPLORATION
{Safety & Happiness
Tuesday, October 2, 12
EXPLORATION
Safety & HappinessTuesday, October 2, 12
Hope actualized
Ex #2: Dual streaming analysis tools
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hell
Tuesday, October 2, 12
Hope actualized
Ex #3: Dual messages queueing systems
Tuesday, October 2, 12
The Future
This is the foundation ofreal responsive designgoing forward.
Tuesday, October 2, 12
Thank You
Questions?
Tuesday, October 2, 12
top related