dyad.c

dyad is a lightweight asynchronous server framework in C. Which is pretty neat!

jQuery plugin repository: unheap

Unheap. Nice.

IMAP architectural patterns

Here's an interesting concept in terms of architectural patterns: synchronization between multiple IMAP servers with OfflineIMAP.  Again, yeah, structural database application, yadda yadda.

Hmm. Zapier to move data between dozens of Web apps.

Abstract Persistence Logic

Now here is a thoughtful essay about the use of persistence in your application: design things so you can decide on a specific persistence system as late as possible.  The advantages, as I see them:

• You can scale as needed
• Early on, you have in-memory persistence so testing goes fast and you don't get hung up on infrastructure.
• Maintainability due to segregation of functionality.

What's not to like?

Uses of git

Here's an interesting little post on the many things you can shoehorn git into doing for you. This should be generalized; that hoary old software component database idea again.

Dreadnot for continuous deployment

Rackspace just open-sourced their continuous deployment tool. Interesting move - and it makes me want (again) to start thinking harder about that software component database.

Web testing

There is a hugely vast array of Web testing tools, even free ones. Seriously. BadBoy is an example I can't even remember finding. Somebody oughta do a feature comparison list.

Miscellaneous software-component stuff

Link-dump time. These are pretty much all notes on software components. (Note to self: define somewhere that what I call software components don't seem to be the same thing as everybody else's software components. - Really these are slot fillers for particular roles in a system design or something.)

• WSGI in Python: The Pluggable Pipe Dream. [article]
• LevelDB, Google's key-value store, is now open source. [site]
• Using MySQL as NoSQL. (The circle is complete.) [article]
• Redesigning the Netflix API. [slideshow article] (the Programmable Web)

That's that.

Scaling: HTTP caching

Some good advice. "Varnish".

Underthesite.com

Cool little technology-stack database, apparently derived automatically, that indexes by URL and by technology. A lot of knowledge there. Makes me think I should probably archive it or something.

Similar tools from the HNN peanut gallery: http://lineofthought.com/, https://github.com/jpf/domain-profiler, https://github.com/mitsuhiko/probe, http://wappalyzer.com/, http://builtwith.com/.

Pandoc: universal rich-text converter

Written in Haskell, no less. [about]

API Marketplace

O API Marketplace, where art thou? Very thought-provoking article about APIs and clearinghouses for them, along with a maybe somewhat dubious business model he wishes somebody else had.

Building block database

When looking at an overall system ecology, we see a lot of applications in it that cover certain areas or regions of functionality. To a certain extent, those applications are interchangeable. What I'd like to do is to index some Web apps and open-source apps (see osalt.com for an example of this at a coarser grain than I mean) and reverse-engineer their specifications in some way that facilitates comparison.

Then, when putting together a specification list for a given business process (say), you could choose which elements to plug together, and identify places where interoperability projects might pay off.

I'm still not 100% clear where I'm going with this, but it deserves further thought.