|
|
Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs
Page 2 of 3
6. Revision control: If you need private or public repositories, GitHub and Bitbucket are your friends. These services have been tested and proven reliable by scores of developers. Your self-hosted repository has been sucking valuable development hours away from billable work for far too long.
7. Issue tracking/project management: There are plenty of tools for these activities -- and there really isn't a compelling reason to host your own JIRA (for instance).
8. HR management: As enjoyable as email and calendars are for vacation requests and other HR juiciness, you eventually need HR management software. This stuff can cloud pretty easily unless you're a gigantic organization with some massive customized Peoplesoft thing (in which case you have fun with that, I'll be enjoying my nice Web interface).
Stuff to think about, then cloud
Not everything will be effortlessly cloudable. Some things require more thought and planning. Consider the following:
9. Identity: We went Google. If it's good enough for the NSA, it's good enough for us! This may actually be a crucial choice before going all-in cloud, since the cloud offerings you select need to work with your identity provider.
10. Database: Scale in concurrency, scale in size, reliability, recoverability, and all of that juicy stuff. Especially if you are considering newer databases like MongoDB or HBase. These are available as utility offerings from your PaaS or IaaS provider.
11. Application servers: Do you enjoy installing and maintaining infrastructure around Tomcat or PHP or Node, etc.? Do you love waiting for WebSphere to start up? Maybe you won't be sending existing, complicated legacy apps to the cloud soon, but you can at least observe the first law of holes and stop digging.
12. Telecommunications: Why have a PBX onsite? Why have video or conferencing stuff? All of this can be maintained for you. If you have extensive legacy infrastructure, this is a little harder to do overnight.
13. Office suites: Seriously, you too can learn Google Docs or something that allows you to do attachmentless sharing and collaborative editing. Let's not understate the effort -- graphics and other things don't translate well, and there is still a feature gap. Granted, most people don't use those features, and many can be "done without" in exchange for better collaboration features (not having conflicting edits) but it took a relatively young and small company over a year to effect this change. Rome wasn't burned in a day.
14. Load testing: You're going to be hearing about this a lot in the next few months. Frankly, the traditional load test tool, Mercury, sucks majorly. Sure, it's very powerful, customizable, etc., but quite often you need some geometric multiplier of your server farm's horsepower in order to test with it. Moreover, it requires a lot of care and feeding. Also, people with sufficient expertise in it are hard to come by. Watch for some interesting new players in this field.
15. Continuous integration: Jenkins is the powerhouse here, and if your PaaS provider hasn't integrated it like Cloudbees has, I expect it will soon (or in the case of Google App Engine, through a partnership with Cloudbees). I'd throw this in the "thoughtless and now" category except for the number of dependencies. You could cloud your internal CI, but certainly it is easier once your source control and application server are clouded.