<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rtlechow)</title>
    <link>https://pinboard.in/u:rtlechow/public/</link>
    <description>recent bookmarks from rtlechow</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/"/>
	<rdf:li rdf:resource="https://aws.amazon.com/builders-library/implementing-health-checks/"/>
	<rdf:li rdf:resource="https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf"/>
	<rdf:li rdf:resource="https://www.sydney.edu.au/news-opinion/news/2022/11/15/this-new--risky--playground-is-a-work-of-art.html"/>
	<rdf:li rdf:resource="https://thume.ca/2023/01/02/one-machine-twitter/"/>
	<rdf:li rdf:resource="https://crawshaw.io/blog/one-process-programming-notes"/>
	<rdf:li rdf:resource="https://medium.com/airbnb-engineering/avoiding-double-payments-in-a-distributed-payments-system-2981f6b070bb"/>
	<rdf:li rdf:resource="https://www.infoq.com/news/2020/04/microservices-back-again/"/>
	<rdf:li rdf:resource="https://medium.com/@dan_manges/the-modular-monolith-rails-architecture-fb1023826fc4"/>
	<rdf:li rdf:resource="https://shopify.engineering/shopify-monolith"/>
	<rdf:li rdf:resource="https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md"/>
	<rdf:li rdf:resource="https://www.industrialempathy.com/posts/design-docs-at-google/"/>
	<rdf:li rdf:resource="https://github.com/donnemartin/system-design-primer"/>
	<rdf:li rdf:resource="https://eventmodeling.org/"/>
	<rdf:li rdf:resource="https://engineering.shopify.com/blogs/engineering/e-commerce-at-scale-inside-shopifys-tech-stack"/>
	<rdf:li rdf:resource="https://blog.heroku.com/rate-throttle-api-client"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=uBYPqb83C7k"/>
	<rdf:li rdf:resource="https://expeditedsecurity.com/api-security-best-practices-megaguide/"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/data-monolith-to-mesh.html"/>
	<rdf:li rdf:resource="https://engineering.shopify.com/blogs/engineering/shopify-manages-api-versioning-breaking-changes"/>
	<rdf:li rdf:resource="https://engineering.shopify.com/blogs/engineering/building-resilient-graphql-apis-using-idempotency"/>
	<rdf:li rdf:resource="https://engineering.shopify.com/blogs/engineering/deconstructing-monolith-designing-software-maximizes-developer-productivity"/>
	<rdf:li rdf:resource="https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101"/>
	<rdf:li rdf:resource="https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Password_Storage_Cheat_Sheet.md"/>
	<rdf:li rdf:resource="https://pragprog.com/book/atevol/software-design-x-rays"/>
	<rdf:li rdf:resource="https://medium.com/airbnb-engineering/production-secret-management-at-airbnb-ad230e1bc0f6"/>
	<rdf:li rdf:resource="https://ferd.ca/queues-don-t-fix-overload.html"/>
	<rdf:li rdf:resource="http://nicolasgallagher.com/about-html-semantics-front-end-architecture/"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/201701-event-driven.html"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=STKCRSUsyP0"/>
	<rdf:li rdf:resource="https://martinfowler.com/articles/break-monolith-into-microservices.html"/>
	<rdf:li rdf:resource="http://www.jamesshore.com/Blog/Dependency-Injection-Demystified.html"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Embarrassingly_parallel"/>
	<rdf:li rdf:resource="https://medium.com/figma-design/an-alternative-approach-to-rate-limiting-f8a06cf7c94c"/>
	<rdf:li rdf:resource="https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying"/>
	<rdf:li rdf:resource="http://www.theverge.com/2016/8/3/12325104/airbnb-aesthetic-global-minimalism-startup-gentrification"/>
	<rdf:li rdf:resource="https://medium.com/vantage/the-crazy-daring-concrete-bus-stops-of-the-soviet-era-34e09a8a3992#.kfnnug9ys"/>
	<rdf:li rdf:resource="http://www.aisf.or.jp/~jaanus/deta/j/jigokuhozo.htm"/>
	<rdf:li rdf:resource="http://simplicity.laserfiche.com/want-better-programs-do-a-reorg/"/>
	<rdf:li rdf:resource="http://mcfunley.com/choose-boring-technology"/>
	<rdf:li rdf:resource="http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/"/>
	<rdf:li rdf:resource="http://www.infoq.com/presentations/tumblr-services?utm_reader=feedly"/>
	<rdf:li rdf:resource="http://vimeo.com/115154289"/>
	<rdf:li rdf:resource="http://www.prettyvacantproperties.com/"/>
	<rdf:li rdf:resource="http://12factor.net/"/>
	<rdf:li rdf:resource="http://www.undergroundhousing.com/book.html"/>
	<rdf:li rdf:resource="http://nickcraver.com/blog/2013/11/22/what-it-takes-to-run-stack-overflow/"/>
	<rdf:li rdf:resource="http://www.robertgordonarchitect.com/RGA/Paris_Density.html"/>
	<rdf:li rdf:resource="http://en.wikipedia.org/wiki/Byzantine_fault_tolerance"/>
	<rdf:li rdf:resource="http://www.ctlab.org/documents/How%20Complex%20Systems%20Fail.pdf"/>
	<rdf:li rdf:resource="http://highscalability.com/blog/2012/5/21/pinterest-architecture-update-18-million-visitors-10x-growth.html"/>
	<rdf:li rdf:resource="http://www.michaelnielsen.org/ddi/how-to-crawl-a-quarter-billion-webpages-in-40-hours/"/>
	<rdf:li rdf:resource="http://www.free-soft.org/FSM/english/issue01/vim.html"/>
	<rdf:li rdf:resource="http://martinfowler.com/bliki/TechnicalDebtQuadrant.html"/>
	<rdf:li rdf:resource="http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/0172.html"/>
	<rdf:li rdf:resource="https://github.com/raganwald/homoiconic/blob/master/2011/11/COMEFROM.md"/>
	<rdf:li rdf:resource="http://blog.8thlight.com/uncle-bob/2012/02/01/Service-Oriented-Agony.html"/>
	<rdf:li rdf:resource="http://sunnyday.mit.edu/16.355/parnas-criteria.html"/>
	<rdf:li rdf:resource="http://fabiensanglard.net/quake2/index.php"/>
	<rdf:li rdf:resource="http://www.tumbleweedhouses.com/houses/z-glass/"/>
	<rdf:li rdf:resource="http://freecabinporn.com/"/>
	<rdf:li rdf:resource="http://www.aosabook.org/en/index.html"/>
	<rdf:li rdf:resource="http://www.ahousebythepark.com/journal/"/>
	<rdf:li rdf:resource="http://www.loresproject.com/"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/3177361/modelling-a-permissions-system/3177578"/>
	<rdf:li rdf:resource="http://www.sadanduseless.com/image.php?n=658"/>
	<rdf:li rdf:resource="http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html"/>
	<rdf:li rdf:resource="http://labs.google.com/papers/bigtable.html"/>
	<rdf:li rdf:resource="http://www.tobuilt.ca/"/>
	<rdf:li rdf:resource="http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/">
    <title>Timeouts, retries and backoff with jitter</title>
    <dc:date>2025-03-02T14:43:30+00:00</dc:date>
    <link>https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>failure networking architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:61597d321862/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://aws.amazon.com/builders-library/implementing-health-checks/">
    <title>Implementing health checks</title>
    <dc:date>2025-03-02T14:43:10+00:00</dc:date>
    <link>https://aws.amazon.com/builders-library/implementing-health-checks/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>monitoring system amazon architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ac2dbb0999f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:monitoring"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:system"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf">
    <title>cmeiklej_phd_s3d_2024.pdf</title>
    <dc:date>2024-09-26T02:16:16+00:00</dc:date>
    <link>https://christophermeiklejohn.com/publications/cmeiklej_phd_s3d_2024.pdf</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>services architecture software netflix doordash</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:663dd6f68e48/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:doordash"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.sydney.edu.au/news-opinion/news/2022/11/15/this-new--risky--playground-is-a-work-of-art.html">
    <title>This new ‘risky’ playground is a work of art - The University of Sydney</title>
    <dc:date>2024-09-04T17:53:54+00:00</dc:date>
    <link>https://www.sydney.edu.au/news-opinion/news/2022/11/15/this-new--risky--playground-is-a-work-of-art.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>playgrounds architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:cc5a15efce5d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:playgrounds"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://thume.ca/2023/01/02/one-machine-twitter/">
    <title>Production Twitter on One Machine? 100Gbps NICs and NVMe are fast - Tristan Hume</title>
    <dc:date>2023-03-14T21:00:38+00:00</dc:date>
    <link>https://thume.ca/2023/01/02/one-machine-twitter/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[In this post I’ll attempt the fun stunt of designing a system that could serve the full production load of Twitter with most of the features intact on a single (very powerful) machine. I’ll start by showing off a Rust prototype of the core tweet distribution data structure handling 35x full load by fitting the hot set in RAM and parallelizing with atomics, and then do math around how modern high-performance storage and networking might let you serve a close-to-fully-featured Twitter on one machine.]]></description>
<dc:subject>scaling twitter performance architecture programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:cd19b64cf0c8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://crawshaw.io/blog/one-process-programming-notes">
    <title>crawshaw - 2018-07-30</title>
    <dc:date>2022-05-04T20:06:53+00:00</dc:date>
    <link>https://crawshaw.io/blog/one-process-programming-notes</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>sqlite golang go architecture programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:a0ac26293e80/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:sqlite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:golang"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:go"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/airbnb-engineering/avoiding-double-payments-in-a-distributed-payments-system-2981f6b070bb">
    <title>Avoiding Double Payments in a Distributed Payments System | by Jon Chew | The Airbnb Tech Blog | Medium</title>
    <dc:date>2022-03-24T15:43:20+00:00</dc:date>
    <link>https://medium.com/airbnb-engineering/avoiding-double-payments-in-a-distributed-payments-system-2981f6b070bb</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[An idempotency key is passed into the framework, representing a single idempotent request
Tables of idempotency information, always read and written from a sharded master database (for consistency)
Database transactions are combined in different parts of the codebase to ensure atomicity, using Java lambdas
Error responses are classified as “retryable” or “non-retryable”]]></description>
<dc:subject>airbnb distributed architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:efe2e1c93b4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:airbnb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.infoq.com/news/2020/04/microservices-back-again/">
    <title>To Microservices and Back Again - Why Segment Went Back to a Monolith</title>
    <dc:date>2022-03-01T15:52:57+00:00</dc:date>
    <link>https://www.infoq.com/news/2020/04/microservices-back-again/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>engineering architecture monolith</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ea9b76745375/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:monolith"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@dan_manges/the-modular-monolith-rails-architecture-fb1023826fc4">
    <title>The Modular Monolith: Rails Architecture | by Dan Manges | Medium</title>
    <dc:date>2021-09-20T13:12:59+00:00</dc:date>
    <link>https://medium.com/@dan_manges/the-modular-monolith-rails-architecture-fb1023826fc4</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture rails design ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:b6618ddce13b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://shopify.engineering/shopify-monolith">
    <title>Under Deconstruction: The State of Shopify’s Monolith — Development (2021)</title>
    <dc:date>2021-09-20T13:08:42+00:00</dc:date>
    <link>https://shopify.engineering/shopify-monolith</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>rails architecture shopify sorbet engines monolith</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:e85c299d7929/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:shopify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:sorbet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:engines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:monolith"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md">
    <title>rust-analyzer/architecture.md at d7c99931d05e3723d878bea5dc26766791fa4e69 · rust-analyzer/rust-analyzer</title>
    <dc:date>2021-02-08T14:42:28+00:00</dc:date>
    <link>https://github.com/rust-analyzer/rust-analyzer/blob/d7c99931d05e3723d878bea5dc26766791fa4e69/docs/dev/architecture.md</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>rust architecture documentation software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:044c57f554b3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rust"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.industrialempathy.com/posts/design-docs-at-google/">
    <title>Design Docs at Google</title>
    <dc:date>2020-07-28T14:55:47+00:00</dc:date>
    <link>https://www.industrialempathy.com/posts/design-docs-at-google/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Besides the original documentation of a software design, design docs fulfill the following functions in the software development lifecycle:

Early identification of design issues when making changes is still cheap.

Achieving consensus around a design in the organization.

Ensuring consideration of cross-cutting concerns.

Scaling knowledge of senior engineers into the organization.

Form the basis of an organizational memory around design decisions.

Acts as a summary artifact in the technical portfolio of the software designer(s).]]></description>
<dc:subject>design documentation engineering google architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:82297d768648/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/donnemartin/system-design-primer">
    <title>donnemartin/system-design-primer: Learn how to design large-scale systems. Prep for the system design interview. Includes Anki flashcards.</title>
    <dc:date>2020-07-28T14:20:42+00:00</dc:date>
    <link>https://github.com/donnemartin/system-design-primer</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>github system design programming architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6db31afcc005/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:system"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://eventmodeling.org/">
    <title>Event Modeling - Designing Modern Information Systems</title>
    <dc:date>2020-07-21T23:56:50+00:00</dc:date>
    <link>https://eventmodeling.org/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design software architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6d4125be6033/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.shopify.com/blogs/engineering/e-commerce-at-scale-inside-shopifys-tech-stack">
    <title>E-Commerce at Scale: Inside Shopify's Tech Stack - Stackshare.io – Shopify Engineering</title>
    <dc:date>2020-07-17T17:38:54+00:00</dc:date>
    <link>https://engineering.shopify.com/blogs/engineering/e-commerce-at-scale-inside-shopifys-tech-stack</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>engineering architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:1d9b972f6f6f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:engineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.heroku.com/rate-throttle-api-client">
    <title>A Fast Car Needs Good Brakes: How We Added Client Rate Throttling to the Platform API Gem | Heroku</title>
    <dc:date>2020-07-17T14:17:55+00:00</dc:date>
    <link>https://blog.heroku.com/rate-throttle-api-client</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>api architecture ruby heroku</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6bc0e1596719/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:heroku"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=uBYPqb83C7k">
    <title>React.js Conf 2016 - Lightning Talks - Andy Matuschak - YouTube</title>
    <dc:date>2020-01-23T14:52:11+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=uBYPqb83C7k</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>video architecture coding gestures</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:97e1df314e12/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:gestures"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://expeditedsecurity.com/api-security-best-practices-megaguide/">
    <title>API Security Best Practices MegaGuide</title>
    <dc:date>2020-01-21T17:44:06+00:00</dc:date>
    <link>https://expeditedsecurity.com/api-security-best-practices-megaguide/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design security api architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:39b5af082c3f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/data-monolith-to-mesh.html">
    <title>How to Move Beyond a Monolithic Data Lake to a Distributed Data Mesh</title>
    <dc:date>2020-01-21T05:38:33+00:00</dc:date>
    <link>https://martinfowler.com/articles/data-monolith-to-mesh.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>data architecture distributed</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c63e16f50b05/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.shopify.com/blogs/engineering/shopify-manages-api-versioning-breaking-changes">
    <title>How Shopify Manages API Versioning and Breaking Changes – Shopify Engineering</title>
    <dc:date>2019-12-28T16:02:18+00:00</dc:date>
    <link>https://engineering.shopify.com/blogs/engineering/shopify-manages-api-versioning-breaking-changes</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[ME: “How did you retrain the dogs after the legalization of cannabis?”

OFFICER: “We didn’t. We had to retire them all and train new ones. You really can’t teach an old dog new tricks.“

ME: “Wow, seriously? How long did that take?”

OFFICER: “Yep, we needed a full THREE YEARS to retire the previous group and introduce a new generation. It was a ton of work.”]]></description>
<dc:subject>design api architecture versioning shopify</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c9d2c614f6c9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:versioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:shopify"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.shopify.com/blogs/engineering/building-resilient-graphql-apis-using-idempotency">
    <title>Building Resilient GraphQL APIs Using Idempotency – Shopify Engineering</title>
    <dc:date>2019-10-03T16:05:24+00:00</dc:date>
    <link>https://engineering.shopify.com/blogs/engineering/building-resilient-graphql-apis-using-idempotency</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>api architecture graphql</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9d68f049e11f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:graphql"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.shopify.com/blogs/engineering/deconstructing-monolith-designing-software-maximizes-developer-productivity">
    <title>Deconstructing the Monolith – Shopify Engineering</title>
    <dc:date>2019-06-13T00:22:18+00:00</dc:date>
    <link>https://engineering.shopify.com/blogs/engineering/deconstructing-monolith-designing-software-maximizes-developer-productivity</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[We developed a tool called Wedge in-house, which tracks the progress of each component towards its goal of isolation. It highlights any violations of domain boundaries (when another component is accessed through anything but its publicly defined API), and data coupling across boundaries. To achieve this, we wrote a tool to hook into Ruby tracepoints during CI to get a full call graph. We then sort callers and callees by component, selecting only the calls that are across component boundaries, and sending them to Wedge. Along with these calls, we send along some additional data from code analysis, like ActiveRecord associations and inheritance. Wedge then determines which of those cross-component things (calls, associations, inheritance) are ok, and which are violating. Generally:]]></description>
<dc:subject>programming rails ruby architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:2d24cc7b7878/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101">
    <title>Streaming 101: The world beyond batch - O'Reilly Media</title>
    <dc:date>2019-03-30T01:28:35+00:00</dc:date>
    <link>https://www.oreilly.com/ideas/the-world-beyond-batch-streaming-101</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>data architecture streaming bigdata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:621902e461fd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:streaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:bigdata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Password_Storage_Cheat_Sheet.md">
    <title>CheatSheetSeries/Password_Storage_Cheat_Sheet.md at master · OWASP/CheatSheetSeries</title>
    <dc:date>2019-03-15T01:50:19+00:00</dc:date>
    <link>https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Password_Storage_Cheat_Sheet.md</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>programming security architecture best-practices password</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:49a63d1bc96d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:best-practices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:password"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://pragprog.com/book/atevol/software-design-x-rays">
    <title>Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis by Adam Tornhill | The Pragmatic Bookshelf</title>
    <dc:date>2018-10-10T03:46:50+00:00</dc:date>
    <link>https://pragprog.com/book/atevol/software-design-x-rays</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>books architecture book toread</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:d9aff227f03b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:book"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:toread"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/airbnb-engineering/production-secret-management-at-airbnb-ad230e1bc0f6">
    <title>Production Secret Management at Airbnb – Airbnb Engineering &amp; Data Science – Medium</title>
    <dc:date>2018-10-08T19:54:56+00:00</dc:date>
    <link>https://medium.com/airbnb-engineering/production-secret-management-at-airbnb-ad230e1bc0f6</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture configuration deployment airbnb security</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:ee5da2978ab0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:configuration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:airbnb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ferd.ca/queues-don-t-fix-overload.html">
    <title>ferd.ca -&gt; Queues Don't Fix Overload</title>
    <dc:date>2018-08-13T13:33:00+00:00</dc:date>
    <link>https://ferd.ca/queues-don-t-fix-overload.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design architecture queue</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:e300a87dd524/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:queue"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nicolasgallagher.com/about-html-semantics-front-end-architecture/">
    <title>About HTML semantics and front-end architecture – Nicolas Gallagher</title>
    <dc:date>2018-06-07T15:48:26+00:00</dc:date>
    <link>http://nicolasgallagher.com/about-html-semantics-front-end-architecture/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[An alternative is to derive class name semantics from repeating structural and functional patterns in a design. The most reusable components are those with class names that are independent of the content.]]></description>
<dc:subject>architecture css html semantics webdev</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:eba6d04ae8d4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:semantics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:webdev"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/201701-event-driven.html">
    <title>What do you mean by “Event-Driven”?</title>
    <dc:date>2018-06-05T19:44:56+00:00</dc:date>
    <link>https://martinfowler.com/articles/201701-event-driven.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>programming architecture events</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:2b35e4b377a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:events"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=STKCRSUsyP0">
    <title>GOTO 2017 • The Many Meanings of Event-Driven Architecture • Martin Fowler - YouTube</title>
    <dc:date>2018-06-05T19:39:58+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=STKCRSUsyP0</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>video architecture talk microservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:cdd6e9c1e04f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:talk"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:microservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martinfowler.com/articles/break-monolith-into-microservices.html">
    <title>How to break a Monolith into Microservices</title>
    <dc:date>2018-04-26T14:12:12+00:00</dc:date>
    <link>https://martinfowler.com/articles/break-monolith-into-microservices.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Often by default the service extraction or monolith decomposition is imagined as a case of reusing the existing implementation as-is and extracting it into a separate service. Partly because we have a cognitive bias towards the code we design and write. The labor of building, no matter how painful the process or imperfect the result, make us grow love for it. This is in fact known as the IKEA Effect. Unfortunately this bias is going to hold the monolith decomposition effort back. It causes the developers and more importantly technical managers to disregard the high cost and low value of extracting and reusing the code.]]></description>
<dc:subject>architecture microservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:14f8b42c0fa8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:microservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.jamesshore.com/Blog/Dependency-Injection-Demystified.html">
    <title>James Shore: Dependency Injection Demystified</title>
    <dc:date>2018-04-18T13:51:25+00:00</dc:date>
    <link>http://www.jamesshore.com/Blog/Dependency-Injection-Demystified.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>development programming architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:52526f2fceb7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Embarrassingly_parallel">
    <title>Embarrassingly parallel - Wikipedia</title>
    <dc:date>2017-11-15T16:01:34+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Embarrassingly_parallel</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[In parallel computing, an embarrassingly parallel workload or problem (also called perfectly parallel or pleasingly parallel) is one where little or no effort is needed to separate the problem into a number of parallel tasks.[1] This is often the case where there is little or no dependency or need for communication between those parallel tasks, or for results between them.[2]

]]></description>
<dc:subject>concurrency architecture computing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:8c06a5e37107/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:concurrency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:computing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/figma-design/an-alternative-approach-to-rate-limiting-f8a06cf7c94c">
    <title>An Alternative Approach to Rate Limiting – Figma Design – Medium</title>
    <dc:date>2017-04-17T01:28:52+00:00</dc:date>
    <link>https://medium.com/figma-design/an-alternative-approach-to-rate-limiting-f8a06cf7c94c</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>programming algorithms api architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:1ffc51d0d4e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:algorithms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying">
    <title>The Log: What every software engineer should know about real-time data's unifying abstraction | LinkedIn Engineering</title>
    <dc:date>2016-12-15T15:44:34+00:00</dc:date>
    <link>https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>logging architecture distributed log kafka</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:02067c6c8ee7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:logging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:log"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:kafka"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.theverge.com/2016/8/3/12325104/airbnb-aesthetic-global-minimalism-startup-gentrification">
    <title>Welcome to AirSpace | The Verge</title>
    <dc:date>2016-08-25T21:42:49+00:00</dc:date>
    <link>http://www.theverge.com/2016/8/3/12325104/airbnb-aesthetic-global-minimalism-startup-gentrification</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[ The new cafe resembles all the other coffee shops Foursquare suggests, whether in Odessa, Beijing, Los Angeles, or Seoul: the same raw wood tables, exposed brick, and hanging Edison bulbs.

It’s not that these generic cafes are part of global chains like Starbucks or Costa Coffee, with designs that spring from the same corporate cookie cutter. Rather, they have all independently decided to adopt the same faux-artisanal aesthetic. Digital platforms like Foursquare are producing "a harmonization of tastes" across the world, Schwarzmann says. "It creates you going to the same place all over again."]]></description>
<dc:subject>design architecture culture style</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f3a2a1ded35f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:style"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/vantage/the-crazy-daring-concrete-bus-stops-of-the-soviet-era-34e09a8a3992#.kfnnug9ys">
    <title>The Crazy-Daring, Concrete Bus Stops of the Soviet Era — Vantage — Medium</title>
    <dc:date>2015-11-02T18:21:07+00:00</dc:date>
    <link>https://medium.com/vantage/the-crazy-daring-concrete-bus-stops-of-the-soviet-era-34e09a8a3992#.kfnnug9ys</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[These are not your standard photo subject and Soviet-era bus stops can be bloody hard to find. They may be visible from the road, but these bus stops sit on some very remote roads! That’s why photographer Christopher Herwig spent 12 years, covering over 18,000 miles by car, bike, bus and taxi to find these Communist relics.]]></description>
<dc:subject>architecture soviet russia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c886f65aab2d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:soviet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:russia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.aisf.or.jp/~jaanus/deta/j/jigokuhozo.htm">
    <title>JAANUS / jigokuhozo　地獄ほぞ</title>
    <dc:date>2015-09-14T15:13:33+00:00</dc:date>
    <link>http://www.aisf.or.jp/~jaanus/deta/j/jigokuhozo.htm</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[
Lit. hell tenon. So named because once it is inserted, it is impossible to withdraw. A blind tenon joint with wedges *kusabi 楔 inserted tightly into slots made on its end. It is important first to place the wedges loosely into the slots to inhibit premature horizontal spreading of the tenon. The base of the tenon is large enough to fit the dovetail-like, tapered shape of the mortise *hozoana ほぞ穴. When the tenon with wedges is pounded into the mortise, the wedges cause the tenon to expand to fit the sides of the mortise. Only the wedges extend the depth of the mortise. The tenon itself does not. Wedges may also be placed on each side of the tenon. The jigokuhozo joint is used where it is necessary that it be hidden, for example on bracket complexes under the eaves of a building, in furniture and cabinet making, and especially in joinery used in the shoin style *shoin-zukuri 書院造. ]]></description>
<dc:subject>architecture joints woodworking craftsmanship</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9748f2a2fb99/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:joints"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:woodworking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:craftsmanship"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://simplicity.laserfiche.com/want-better-programs-do-a-reorg/">
    <title>Want Better Programs? Do a Reorg - Laserfiche</title>
    <dc:date>2015-04-28T05:10:46+00:00</dc:date>
    <link>http://simplicity.laserfiche.com/want-better-programs-do-a-reorg/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[“Their study found that the often co-located, focused product teams created software that tended more towards tightly-coupled, monolithic codebases,” writes Sam Newman of ThoughtWorks. “Whereas, the open source projects resulted in more modular, decomposed code bases.”]]></description>
<dc:subject>programming culture management architecture organisation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:722a0079603a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:organisation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mcfunley.com/choose-boring-technology">
    <title>Dan McKinley :: Choose Boring Technology</title>
    <dc:date>2015-03-31T19:58:58+00:00</dc:date>
    <link>http://mcfunley.com/choose-boring-technology</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Polyglot programming is sold with the promise that letting developers choose their own tools with complete freedom will make them more effective at solving problems. This is a naive definition of the problems at best, and motivated reasoning at worst. The weight of day-to-day operational toil this creates crushes you to death.

Mindful choice of technology gives engineering minds real freedom: the freedom to contemplate bigger questions. Technology for its own sake is snake oil.]]></description>
<dc:subject>programming advice architecture management technology</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9489edf1811f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:advice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:technology"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/">
    <title>An Incremental Migration from Rails Monolithic to Microservices</title>
    <dc:date>2015-01-26T03:13:23+00:00</dc:date>
    <link>http://blog.carbonfive.com/2014/05/29/an-incremental-migration-from-rails-monolithic-to-microservices/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>legacy migration rails ruby architecture microservices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:7ca9afc1b6a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:legacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:migration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:microservices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.infoq.com/presentations/tumblr-services?utm_reader=feedly">
    <title>Tumblr - Bits to Gifs</title>
    <dc:date>2014-12-30T18:19:34+00:00</dc:date>
    <link>http://www.infoq.com/presentations/tumblr-services?utm_reader=feedly</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>tumblr architecture towatch</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:8cb6e1dba97a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tumblr"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:towatch"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vimeo.com/115154289">
    <title>The Humane Representation of Thought on Vimeo</title>
    <dc:date>2014-12-22T20:56:54+00:00</dc:date>
    <link>http://vimeo.com/115154289</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design video architecture career english</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:22c9be8900f6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:career"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:english"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.prettyvacantproperties.com/">
    <title>PRETTY VACANT Properties: Home</title>
    <dc:date>2014-12-10T04:23:42+00:00</dc:date>
    <link>http://www.prettyvacantproperties.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture california travel hotel</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:7c1d4f6c1d9f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:california"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:travel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hotel"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://12factor.net/">
    <title>The Twelve-Factor App</title>
    <dc:date>2014-07-28T17:43:34+00:00</dc:date>
    <link>http://12factor.net/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>programming architecture development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f3f2edb0821b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.undergroundhousing.com/book.html">
    <title>$50 and Up Underground House Book – Underground Housing and Shelter</title>
    <dc:date>2014-03-28T22:13:12+00:00</dc:date>
    <link>http://www.undergroundhousing.com/book.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>books architecture home housing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:cb6af6834fab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:home"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:housing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nickcraver.com/blog/2013/11/22/what-it-takes-to-run-stack-overflow/">
    <title>What it takes to run Stack Overflow « Nick Craver</title>
    <dc:date>2014-02-12T19:47:46+00:00</dc:date>
    <link>http://nickcraver.com/blog/2013/11/22/what-it-takes-to-run-stack-overflow/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[I like to think of Stack Overflow as running with scale but not at scale.  By that I meant we run very efficiently, but I still don’t think of us as “big”, not yet.  Let’s throw out some numbers so you can get an idea of what scale we are at currently.  Here are some quick numbers from a 24 hour window few days ago – November 12th, 2013 to be exact.  These numbers are from a typical weekday and only include our active data center – what we host.  Things like hits/bandwidth to our CDN are not included, they don’t hit our network.]]></description>
<dc:subject>architecture devops hardware infrastructure stackoverflow</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:0dbd636a1941/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:hardware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:stackoverflow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.robertgordonarchitect.com/RGA/Paris_Density.html">
    <title>Paris Density</title>
    <dc:date>2013-08-06T13:58:35+00:00</dc:date>
    <link>http://www.robertgordonarchitect.com/RGA/Paris_Density.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[The city of Paris is often cited by architects and planners as their favorite place to visit. Parisians and visitors alike never tire of walking her narrow, winding streets, with continuous ground level boutiques and cafes. They enjoy the quiet gardens and public places. They may not take into consideration that most of the old city has a uniform building height. During the Haussmann era, the nineteenth century, architects were required to build “immeubles”, (apartment buildings), no higher than the tower of Notre Dame, or about 100’. This typically produces a six-story building with “Rez-de-chaussee” (ground level) and “combles” (attics). The population of Paris is approximately 2,156,190, covering an area of 41 square miles, 52,590 people per square mile. The result is a certain density and a certain proportion of street to building. This density is found to be ideal for supporting continuous retail space, and therefore a walkable city. It has also been found to be a human scale, not too tall to be alienating to the dwellers or the passers-by. ]]></description>
<dc:subject>paris planning architecture cities</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:e877ca2e50fc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:paris"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:planning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cities"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://en.wikipedia.org/wiki/Byzantine_fault_tolerance">
    <title>Byzantine fault tolerance - Wikipedia, the free encyclopedia</title>
    <dc:date>2013-03-25T14:19:48+00:00</dc:date>
    <link>http://en.wikipedia.org/wiki/Byzantine_fault_tolerance</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA["A Byzantine fault is an arbitrary fault that occurs during the execution of an algorithm by a distributed system. It encompasses both omission failures (e.g., crash failures, failing to receive a request, or failing to send a response) and commission failures (e.g., processing a request incorrectly, corrupting local state, and/or sending an incorrect or inconsistent response to a request). When a Byzantine failure has occurred, the system may respond in any unpredictable way, unless it is designed to have Byzantine fault tolerance.
For example, if the output of one function is the input of another, then small round-off errors in the first function can produce much larger errors in the second. If the second function were fed into a third, the problem could grow even larger, until the values produced are worthless. Another example is in compiling source code. One minor syntactical error early on in the code can produce large numbers of perceived errors later, as the parser of the compiler gets out-of-phase with the lexical and syntactic information in the source program. Such failures have brought down major Internet services. For example, in 2008 Amazon S3 was brought down for several hours when a single-bit hardware error propagated through the system.[2]"]]></description>
<dc:subject>programming architecture cluster distributed software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:fcbc8574b410/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cluster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ctlab.org/documents/How%20Complex%20Systems%20Fail.pdf">
    <title>www.ctlab.org/documents/How Complex Systems Fail.pdf</title>
    <dc:date>2013-02-28T14:53:22+00:00</dc:date>
    <link>http://www.ctlab.org/documents/How%20Complex%20Systems%20Fail.pdf</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture complexity failure systems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f716f5c33624/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:systems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://highscalability.com/blog/2012/5/21/pinterest-architecture-update-18-million-visitors-10x-growth.html">
    <title>High Scalability - High Scalability - Pinterest Architecture Update - 18 Million Visitors, 10x Growth,12 Employees, 410 TB of Data</title>
    <dc:date>2012-11-06T20:51:48+00:00</dc:date>
    <link>http://highscalability.com/blog/2012/5/21/pinterest-architecture-update-18-million-visitors-10x-growth.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[80 million objects stored in S3 with 410 terabytes of user data, 10x what they had in August. EC2 instances have grown by 3x.  Around $39K fo S3 and $30K for EC2.
12 employees as of last December. Using the cloud a site can grow dramatically while maintaining a very small team. Looks like 31 employees as of now.
Pay for what you use saves money. Most traffic happens in the afternoons and evenings, so they reduce the number of instances at night by 40%. At peak traffic  $52 an hour is spent on EC2 and at night, during off peak, the spend is as little as $15 an hour.
150 EC2 instances in the web tier
90 instances for in-memory caching, which removes database load
35 instances used for internal purposes
70 master databases with a parallel set of backup databases in different regions around the world for redundancy
Written in Python and Django 
Sharding is used, a database is split when it reaches 50% of capacity, allows easy growth and gives sufficient IO capacity
ELB is used to load balance across instances. The ELB API makes it easy to move instances in and out of production.
One of the fastest growing sites in history. Cites AWS for making it possible to handle 18 million visitors in March, a 50% increase from the previous month, with very little IT infrastructure.
The cloud supports easy and low cost experimenation. New services can be tested without buying new servers, no big up front costs.
Hadoop-based Elastic Map Reduce is used for data analysis and costs only a few hundred dollars a month.]]></description>
<dc:subject>amazon architecture aws scalability pinterest</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:eee8798aabb6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:pinterest"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.michaelnielsen.org/ddi/how-to-crawl-a-quarter-billion-webpages-in-40-hours/">
    <title>How to crawl a quarter billion webpages in 40 hours | DDI</title>
    <dc:date>2012-10-31T18:32:05+00:00</dc:date>
    <link>http://www.michaelnielsen.org/ddi/how-to-crawl-a-quarter-billion-webpages-in-40-hours/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture crawler datamining web crawling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:43a691c62342/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:crawler"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:datamining"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:crawling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.free-soft.org/FSM/english/issue01/vim.html">
    <title>vim: the popular text editor</title>
    <dc:date>2012-10-10T14:27:24+00:00</dc:date>
    <link>http://www.free-soft.org/FSM/english/issue01/vim.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA["Vim uses many different data structures to store information. There is a trade-off between using a generic kind of structure and using a structure specifically tailored to an application. For example, a string can be stored in a fixed size array on the stack, a fixed sized chunk of allocated memory or a dynamically sized chunk of allocated memory. Which one to use depends on the type of string to be stored:

For strings that have a known maximum size, using the stack has the advantage that the time consuming malloc() and free() don't have to be used. This can usually be done with file names, but Vim tries not to restrict the user, thus other strings can be of any length and the stack is not suitable.
A fixed size of allocated memory can be used for items that don't change often. This is used for option values, for example. It doesn't waste memory and the overhead of malloc()/free() is not important.
For strings that change often, calling malloc()/free() often consumes a lot of time. This is especially true for strings and lists that can grow in size. In Vim a dynamically allocated piece of memory is used for this - a "struct growarray". The memory allocation is made in large steps, so that a certain number of items can be appended without reallocating.
I have ended up creating quite a few data structures in Vim. The disadvantage is that this has taken a lot of time, it adds to the complexity and makes maintenance more work. The advantage is that Vim works very fast and efficient. Compare this with Emacs, where the main complaint is that it's slow and consumes a lot of resources. I have the impression that Emacs uses generic constructs and depends on the computer to be fast. In my opinion I have made the right choice. A text editor is used all day by many people; it is worth investing time and effort in making it work well."]]></description>
<dc:subject>design programming architecture vim</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f5f16a11820d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:vim"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://martinfowler.com/bliki/TechnicalDebtQuadrant.html">
    <title>TechnicalDebtQuadrant</title>
    <dc:date>2012-09-14T13:54:57+00:00</dc:date>
    <link>http://martinfowler.com/bliki/TechnicalDebtQuadrant.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>design programming agile architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c3a2bb81c45e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/0172.html">
    <title>HTTP/2 Expression of luke-warm interest: Varnish from Poul-Henning Kamp on 2012-07-12 (ietf-http-wg@w3.org from July to September 2012)</title>
    <dc:date>2012-07-21T18:46:38+00:00</dc:date>
    <link>http://lists.w3.org/Archives/Public/ietf-http-wg/2012JulSep/0172.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>protocol http architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:eb7efba72b6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:protocol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/raganwald/homoiconic/blob/master/2011/11/COMEFROM.md">
    <title>2011/11/COMEFROM.md at master from raganwald/homoiconic - GitHub</title>
    <dc:date>2012-02-27T19:38:54+00:00</dc:date>
    <link>https://github.com/raganwald/homoiconic/blob/master/2011/11/COMEFROM.md</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>agile architecture development programming solid</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:b3d71e9dde19/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:solid"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.8thlight.com/uncle-bob/2012/02/01/Service-Oriented-Agony.html">
    <title>Service Oriented Agony | 8th Light</title>
    <dc:date>2012-02-01T22:01:47+00:00</dc:date>
    <link>http://blog.8thlight.com/uncle-bob/2012/02/01/Service-Oriented-Agony.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[So what’s the solution? First of all, I question whether the system needed to be partitioned into services. Services are expensive and complicated, you should only create them if you absolutely need to. It’s always easier to live in a single process. Remember Martin Fowler’s first law of distributed objects: Don’t distribute your objects.]]></description>
<dc:subject>srp solid ccp systems software programming services architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:856ea6ab2430/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:srp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:solid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ccp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sunnyday.mit.edu/16.355/parnas-criteria.html">
    <title>On the Criteria To Be Used in Decomposing Systems into Modules</title>
    <dc:date>2011-11-23T03:58:13+00:00</dc:date>
    <link>http://sunnyday.mit.edu/16.355/parnas-criteria.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture design development modularity programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:50cf29790463/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:modularity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://fabiensanglard.net/quake2/index.php">
    <title>Quake 2 Source Code Review</title>
    <dc:date>2011-09-23T21:57:37+00:00</dc:date>
    <link>http://fabiensanglard.net/quake2/index.php</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>code c games programming quake software development architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:512997cccb00/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:games"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:quake"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tumbleweedhouses.com/houses/z-glass/">
    <title>Z-Glass</title>
    <dc:date>2011-08-30T14:33:08+00:00</dc:date>
    <link>http://www.tumbleweedhouses.com/houses/z-glass/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[The Z-Glass house is not designed as a portable house; yet at only 14? wide it can be trucked down the road with a wide load permit. The house shown above is pictured with rolled hot steel siding. This is just one idea for a durable exterior finish that would match the modern design of the Z-glass, but since you build it yourself, the choice is yours! Unfortunately, at this time we do not have interior pictures. This house is 370 square feet and 9’6″ tall from floor to roof top.]]></description>
<dc:subject>architecture design tinyhouse</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:fe23d8cea762/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:tinyhouse"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://freecabinporn.com/">
    <title>Cabin Porn</title>
    <dc:date>2011-06-24T20:00:14+00:00</dc:date>
    <link>http://freecabinporn.com/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture cabin photography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:c377513e1134/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cabin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:photography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.aosabook.org/en/index.html">
    <title>The Architecture of Open Source Applications</title>
    <dc:date>2011-06-12T15:45:31+00:00</dc:date>
    <link>http://www.aosabook.org/en/index.html</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture books opensource programming software toread</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6b71223930c1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:books"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:toread"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ahousebythepark.com/journal/">
    <title>A House by the Park</title>
    <dc:date>2011-05-19T19:11:40+00:00</dc:date>
    <link>http://www.ahousebythepark.com/journal/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture design house inspiration timelapse photography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6a6fc960944b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:house"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:inspiration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:timelapse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:photography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loresproject.com/">
    <title>United Nude - Lo Res Project</title>
    <dc:date>2010-08-30T13:40:53+00:00</dc:date>
    <link>http://www.loresproject.com/</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[1. Wireframe an object (building, shoe, chair)
2. Remove polygons / smooth / lo-res-ify
3. PROFIT (simplify manufacturing)
]]></description>
<dc:subject>3d animation architecture art computer design digital form idea inspiration model resolution modelling</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:7077cd380a9b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:3d"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:animation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:computer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:form"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:idea"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:inspiration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:model"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:resolution"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:modelling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/3177361/modelling-a-permissions-system/3177578">
    <title>Modelling a permissions system - Stack Overflow</title>
    <dc:date>2010-08-11T01:20:01+00:00</dc:date>
    <link>http://stackoverflow.com/questions/3177361/modelling-a-permissions-system/3177578</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture security modeling stackoverflow permissions</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:401246744c85/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:stackoverflow"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:permissions"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.sadanduseless.com/image.php?n=658">
    <title>American City of Future (1925) #2</title>
    <dc:date>2010-08-06T14:29:58+00:00</dc:date>
    <link>http://www.sadanduseless.com/image.php?n=658</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA["How You May Live and Travel in the City of 1950… SPIRAL ESCALATORS"
]]></description>
<dc:subject>architecture city art culture design future history magazine retro technology 1950</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:6d345010f956/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:city"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:magazine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:retro"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:1950"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html">
    <title>Amazon's Dynamo - All Things Distributed</title>
    <dc:date>2010-07-19T03:18:40+00:00</dc:date>
    <link>http://www.allthingsdistributed.com/2007/10/amazons_dynamo.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Giuseppe DeCandia, Deniz Hastorun, Madan Jampani, Gunavardhan Kakulapati, Avinash Lakshman, Alex Pilchin, Swami Sivasubramanian, Peter Vosshall and Werner Vogels, “Dynamo: Amazon's Highly Available Key-Value Store”, in the Proceedings of the 21st ACM Symposium on Operating Systems Principles, Stevenson, WA, October 2007.
]]></description>
<dc:subject>amazon architecture cloud cluster database data development nosql dynamo s3 scalability programming research web aws</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:659b39004bf2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cluster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:dynamo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:research"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://labs.google.com/papers/bigtable.html">
    <title>Google Research Publication: BigTable</title>
    <dc:date>2010-07-19T03:16:05+00:00</dc:date>
    <link>http://labs.google.com/papers/bigtable.html</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA[Bigtable: A Distributed Storage System for Structured Data
Fay Chang, Jeffrey Dean, Sanjay Ghemawat, Wilson C. Hsieh, Deborah A. Wallach, Mike Burrows, Tushar Chandra, Andrew Fikes, and Robert E. Gruber
]]></description>
<dc:subject>architecture cloud database data cluster databases development distributed filesystem google paper pdf programming scalability bigtable</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:9e835a1fbd91/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cluster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:filesystem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:paper"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:bigtable"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.tobuilt.ca/">
    <title>TOBuilt: A Database of Buildings in Toronto, Canada</title>
    <dc:date>2010-05-04T03:22:25+00:00</dc:date>
    <link>http://www.tobuilt.ca/</link>
    <dc:creator>rtlechow</dc:creator><dc:subject>architecture art buildings canada database design data ontario toronto urban reference photography photos community local</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:379deb0f0083/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:buildings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:canada"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:ontario"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:toronto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:urban"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:photography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:photos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:local"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king">
    <title>Cassandra @ Twitter: An Interview with Ryan King « myNoSQL</title>
    <dc:date>2010-03-18T01:25:59+00:00</dc:date>
    <link>http://nosql.mypopescu.com/post/407159447/cassandra-twitter-an-interview-with-ryan-king</link>
    <dc:creator>rtlechow</dc:creator><description><![CDATA["ome side notes here about importing. We were originally trying to use the BinaryMemtable[2] interface, but we actually found it to be too fast — it would saturate the backplane of our network. We’ve switched back to using the Thrift interface for bulk loading (and we still have to throttle it). The whole process takes about a week now. With infinite network bandwidth we could do it in about 7 hours on our current cluster."
]]></description>
<dc:subject>twitter nosql database scalability opensource distributed development architecture cassandra</dc:subject>
<dc:identifier>https://pinboard.in/u:rtlechow/b:f9d9183aae0e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:nosql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rtlechow/t:cassandra"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>