Skip to content

Instantly share code, notes, and snippets.

@gravesm
Last active July 25, 2017 15:11
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gravesm/74127543343681be98467f64fba760b3 to your computer and use it in GitHub Desktop.
Save gravesm/74127543343681be98467f64fba760b3 to your computer and use it in GitHub Desktop.
<section>
<h1>You are in a maze of twisty containers, all unversioned.</h1>
</section>
<section>
<h2>Kubernetes</h2>
<div>
<ul>
<li>6 pods (adit api, elasticsearch, fedora, nginx, pit, postgres)</li>
<li>Container images stored in google cloud</li>
<li>There's no builtin versioning, so it can be hard to figure out what version of what you have deployed</li>
<li>The build-test-debug cycle can be frustrating</li>
<li>When properly used by a trained professional, kubernetes can be great</li>
</ul>
</div>
<p>Verdict: Would use again, as long as I don't have to deal with it.</p>
</section>
<section>
<h2>Fedora</h2>
<div>
<ul>
<li>I hate JSON-LD. Just get things into RDF as soon as possible.</li>
<li>Documentation lacking</li>
<li>Performance problems while indexing, though PCDM likely culprit</li>
</ul>
</div>
<p>Verdict: Would use again.</p>
</section>
<section>
<h2>Elasticsearch</h2>
<div>
<ul>
<li>Mostly just worked</li>
<li>Feature parity with SolrCloud, but ES is much easier to set up</li>
<li>Nice features: CRUD on indices and index aliases, all over HTTP</li>
</ul>
</div>
<p>Verdict: Would use over Solr.</p>
</section>
<section>
<h2>Asyncio</h2>
<div>
<ul>
<li>pit was written using asyncio</li>
<li>More straightforward concurrency than threading?</li>
<li>Making a graceful exit is difficult</li>
</ul>
</div>
<p>Verdict: Would use again in another year.</p>
</section>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment