Why do another startup? Why put in all the hours? Why go without pay for long periods?Frankly, we’re not done.
A decade after rolling out the first cloud platform (yes, AppLogic predated EC2), a lot of the changes we’d hoped to enable with cloud still remain elusive. It’s true that it’s become much easier to deal with provisioning. Few startups now raise money just to rent a cage and buy servers. APIs have put infrastructure in the hands of engineers. In addition, modern startups don’t have to add system administrators at the same rate as engineers. Actually, I’ve encountered many companies over the last few months with a single devops engineer responsible for all operations. Moreover, cloud API’s have made it commonplace to be able to start and stop entire services easily. So what’s missing? The answer to the question starts with a story.
At 3tera we designed our cloud platform, AppLogic, to allow users to allocate virtual machine resources in exacting detail. Memory could be assigned in 1MB increments, CPU was controlled to 1% of a core and bandwidth in 1Mbps. Our belief was that utilizing resources efficiently would be important to customers. We were wrong. AWS offered a few predefined virtual machines sizes, and customers greatly preferred that simplicity. We learned from that experience that engineers lacked tools to determine how to allocate resources in minute detail. Our users struggled because we actually offered them too much flexibility – in essence we created extra complexity for them.
We believe the complexity we first encountered in the cloud era is a hundred fold greater today. CI/CD has enabled more frequent releases and DevOps has completely automated moving code to product, but the combination has only added to the uncertainty of how to set resource assignments and parameters. With applications now bigger than ever, the need for efficiency is only growing.
Opsani was founded with the mission to act on that need.