This is an article written as a series of subtopics, covering the design of a smart grid application. It does a lot of meandering, talking about architecture and why you’d make choices (or, rather, why I made choices), hopefully exposing some of the thought processes one should go through while designing a good application.
There are two things to note, going in:
The numbering. I get bored easily, so I started using odd numbers as part of the numbering scheme. Thus, you get Spanish, French, binary, hexadecimal, base 11, mathematics…
It isn’t finished! It was part of my job to write a detailed series about how to design a smart grid. As a result, there’s a slight lean towards Red Hat products and infrastructure (although none of it’s Red Hat-specific)… and, more severely, I got pulled off of the project to work on some other things, so the actual smart grid implementation never actually got written.
Finishing it will be in two steps:
First, I plan to describe what it was I was building, in terms of the messaging infrastructure.
Second, I want to flesh it out, showing how you’d actually deploy and configure such an infrastructure.
There’s still a lot of useful information here, though, and presented for convenience, here’s the table of contents as it stands right now:
- Smart Grids, Part I
- Smart Grids, Part Deux
- Smart Grids, part tres: Data!
- Smart Grids, part vierte: a simple data store
- Smart Grids, part he: JNDI resource refs
- Smart Grids, part 110: one of the presentation layers
- Smart Grids, part seacht: jQuery and Java2D
- Smart Grids, part bā: Submitting live data
- Smart Grids, part dyevit: Android!
- Smart Grids, part A: Wrapping a data transport
- Smart Grids, Part 10: The Android Application, rounded out
- Smart Grids, part [x=2;y=6;x·y]: Moving to Android 4.0