OK, there is no "they" and "they" wouldn't care if you knew anyway. After all, this isn't a blog about really important stuff like investing, acne cures, or cheap natural cleansing products.
But the secrets are real. Super cloud scaling consultant Kent Langley has put together a comprehensive checklist to consider when developing for the cloud:
ORM for Data Partitioning and Query Splitting - Split queries between updates and deletes from the start
Monitoring process, resources, and uptime - Process Monitoring, Resource Monitoring, UpTime Monitoring
Performance Testing and Capacity Planning - Can't make good decisions without doing some degree of Performance Testing and Capacity planning.
Static vs. Dynamic Content splitting / CDN - Reverse Proxy, Splitting Static and Dynamic content
Bundling and Compressing JS and CSS - Bundle them, compress, version, and then properly cache those bundles
Logging - Log appropriately and monitor those logs
Pragmatic Caching - Most current web applications will have between 3-5 layers of caching
Functional Decomposition - Decompose your entire application into functional silos
Deployment - It should be efficient, it should have a roll back capability, and it should be almost entirely automated to development
Asynchronous Practices - Most cases work can be queued and done by a separate process
Make sure your application processes are as lean as possible - More efficient code means less servers
Please follow the link to Kent's post for a full explanation. To some this may seem obvious, but that doesn't mean it gets done. Good helpful stuff.
Related Articles
Joyent - Cloud Computing Built on Accelerators by Kent Langley
Reader Comments (7)
Holy jeapers, what sort of asinine title is "Cloud Scale Consultant"? It never ceases to amaze me how many rediculous ways half-cocked engineers will use to dress themselves up to aid in their money grabbing efforts. If someone introduced themselves to me as a "Cloud Scale Consultant" I'd likely laugh in their face and show them the door.
There is nothing surprising about this list, I'd even posit it's all obvious knowledge among the average software engineer that spends even a modicum of time reading tech news.
Lame!
> Cloud Scale Consultant
It's supposed to be funny. Jeesh.
When moving to "Cloud Services", let's say Amazon.. What is the overall performance degradation of the Virtual Machines you will get for that service. I assume you are not just given a physical machine, but some VM..and thus you can't achieve the same IO troughput or CPU utilization as if you were operating "alone" on a standalone physical machine.
You got the title wrong, I think it was called:
"11 ways to re-iterate the obvious in order to drive traffic to obscure blogs".
Honestly, the signal to noise ratio on highscalablity.com is approaching 1:100.
For the future: Could you *please* assume that most of your readers already know all the buzzwords. These "glossary"-posts are getting really old quick. We all know that caching, planning, monitoring, distributing load etc. etc. are all good for scaling.
Focus on posts that tell us HOW to do it and product reviews. That's what we want to read.
We don't care about the 14th content-free enumeration of keywords...
> We don't care about the 14th content-free enumeration of keywords...
Excellent, 8 more to go.
To be more serious than I care to be, there all sorts of people who read this blog at all different phases of a project. So something that strikes you as redundant will strike them as what they need when they need it, especially as horrors, not everyone has read every post here. And in this case Kent goes into more details so there wasn't much for me to do.
Though you are Anonymous, you are clearly a more advanced practitioner and will always be harder to make happy. But I will try. Monday there's a good post from Notify.me coming up. But that doesn't mean there's only one kind of post that's appropriate for everyone.
I've nothing to do with high-scalibility, but I watch this blog to gather new keywords/buzzwords.
This is an excellent site. I have picked up quite a few good pointers. Don't be discouraged by those who choose to complain yet put forth no effort in posting something useful themselves. Thanks for the good work, this is one of my home pages in my browser.