Let's go all out:
Prefix Symbol Size Example
yocto y 1 bit Theoretical minimum
zepto z 1 byte (close enough to 10 bits) Really small APL program
atto a 10 chars nc -l 8080
femto f 1 line (roughly 100 chars) netcat piped into something else
pico p 10 lines tiny python service
nano n 100 lines small python service
micro μ 1000 lines typical "smallish" service
milli m 10,000 lines about as big as "microservices" would go these days, or a small monolithic app
centi c 100,000 lines decent-sized monolithic app
deci d 1 million lines large monolitihic app
none n/a 10 million lines roughly OS-level app
deca da 100 million lines god help you beyond here
hecto h 1 billion lines
kilo k 10 billion lines
mega M 100 billion lines
giga G 1 trillion lines
tera T 10 trillion lines
peta P 100 trillion lines
exa E 1 quadrillion lines
zetta Z 10 quadrillion lines
yotta Y 100 quadrillion lines
Re:Introduction to Microservices
by VikingCoder on Thursday July 09, 2015 @02:14PM
(#9859692)
googol NYSE:GOOG ??? lines GoogleIt's obviously Googol lines.
This is excellent. Upvoted, obviously, but I also just wanted to reply to say I laughed out loud and also thought, "Yeah, that does seem about right."
Perhaps the nanoservice manifesto would just be to use vanilla erlang. One process per module, each module less than 100 LOC. Would that be small enough?
It's just a matter of time until someone writes a "nano-service" manifesto...