Riak is an open source, distributed database platform based on the principles enumerated in the DynamoDB paper. It uses a simple key/value model for object storage, and it was architected for high availability, fault tolerance, operational simplicity and scalability. A Riak cluster is composed of multiple nodes that are all connected, all communicating and sharing data automatically. If one node were to fail, the other nodes would automatically share the data that the failed node was storing and processing until the node is back up and running or a new node is added. See the diagram below for a simple illustration of how adding a node to a cluster works within Riak.

We will support both the open source and the Enterprise versions of Riak. The open source version is a great place to start. It has all of the database functionality of Riak Enterprise, but it is limited to a single cluster. The Enterprise version supports replication between clusters across data centers, giving you lots of architectural options. You can use replication to build highly available, live-live failover applications. You can also use it to distribute your application’s data across regions, giving you a global platform that you can update anywhere in the world and know that those modifications will be available anywhere else. Riak Enterprise customers also receive 24×7 coverage, both from SoftLayer and Basho. This includes SoftLayer’s one-hour guaranteed response for Severity 1 hardware issues and unlimited support available via our secure web portal, email and phone.

The business use-case for this flexibility is that if you need to scale up or down, nodes can be easily added or taken down as your requirements change. You can opt for a single-data center environment with a few nodes or you can broaden your architecture to a multi-data center deployment with a 40-node cluster. While these capabilities are inherent in Riak, they can be complicated to build and configure, so we spent countless hours working with Basho to streamline Riak deployment on the SoftLayer platform. The fruit of that labor can be found in our Riak Solution Designer:

The server configurations and packages in the Riak Solution Designer have been selected to deliver the performance, availability and stability that our customers expect from their bare metal and virtual cloud infrastructure at SoftLayer. With a few quick clicks, you can order a fully configured Riak environment, and it’ll be provisioned and online for you in two to four hours. And everything you order is on a month-to-month contract.

Thanks to the hard work done by the SoftLayer development group and Basho’s team, we’re proud to be the first in the marketplace to offer a turn-key Riak solution on bare metal infrastructure. You don’t need to sacrifice performance and agility for simplicity.

For more information, visit SoftLayer.com/Riak or contact our sales team.

-Duke

‘The Cloud’ and Agility

As the CEO of a cloud-enabled application platform for the .NET community, I get the same basic question all the time: “What is the cloud?” I’m a consumer of cloud services and a supplier of software that helps customers take advantage of the cloud, so my answer to that question has evolved over the years, and I’ve come to realize that the cloud is fundamentally about agility. The growth, evolution and adoption of cloud technology have been fueled by businesses that don’t want to worry about infrastructure and need to pivot or scale quickly as their needs change.

Because FatCloud is a consumer of cloud infrastructure from Softlayer, we are much more nimble than we’d be if we had to worry about building data centers, provisioning hardware, patching software and doing all the other time-consuming tasks that are involved in managing a server farm. My team can focus on building innovative software with confidence that the infrastructure will be ready for us on-demand when we need it. That peace of mind also happens to be one of the biggest reasons developers turn to FatCloud … They don’t want to worry about configuring the fundamental components of the platform under their applications.

Our customers trust FatCloud’s software platform to help them build and scale their .NET applications more efficiently. To do this, we provide a Core Foundation of .NET WCF services that effectively provides the “plumbing” for .NET cloud computing, and we offer premium features like a a distributed NoSQL database, work queue, file storage/management system, content caching and an easy-to-use administration tool that simplifies managing the cloud for our customers. FatCloud makes developing for hundreds of servers as easy as developing for one, and to prove it, we offer a free 3-node developer edition so that potential customers can see for themselves.

The agility of the cloud has the clearest value for a company like ours. In one heavy-duty testing month, we needed 75 additional servers online, and after that testing was over, we needed the elasticity to scale that infrastructure back down. We’re able to adjust our server footprint as we balance our computing needs and work within budget constraints. Ten years ago, that would have been overwhelmingly expensive (if not impossible). Today, we’re able to do it economically and in real-time. SoftLayer is helping keep FatCloud agile, and FatCloud passes that agility on to our customers.

Companies developing custom software for the cloud, mobile or web using .NET want a reliable foundation to build from, and they want to be able to bring their applications to market faster. With FatCloud, those developers can complete their projects in about half the time it would take them if they were to develop conventionally, and that speed can be a huge competitive differentiator.

The expensive “scale up” approach of buying and upgrading powerful machines for something like SQL Server is out-of-date now. The new kid in town is the “scale out” approach of using low-cost servers to expand infrastructure horizontally. You’ll never run into those “scale up” hardware limitations, and you can build a dynamic, scalable and elastic application much more economically. You can be agile.

If you have questions about how FatCloud and SoftLayer make cloud-enabled .NET development easier, send us an email: sales@fatcloud.com. Our team is always happy to share the easy (and free) steps you can take to start taking advantage of the agility the cloud provides.

-Ian Miller, CEO of FatCloud

The question everyone asks is why this kind of thing still happens. To a certain extent, the reality is that most entrepreneurs don’t know what they don’t know. I spoke with an woman who was going to be featured on BBC’s Dragons’ Den, and she said that the traffic from the show’s viewers crippled most (if not all) of the businesses that were presented on the program. She needed to safeguard from that happening to her site, and she didn’t know how to do that.

Fortunately, it’s pretty easy to keep sites and applications online with on-demand infrastructure and auto-scaling tools. Unfortunately, most business owners don’t know how easy it is, so they don’t take advantage of the resources available to them. Preparing a website, game or application for its own success doesn’t have to be expensive or time consuming. With pay-for-what-you-use pricing and “off the shelf” cloud management solutions, traffic-caused outages do NOT have to happen.

First impressions are extremely valuable, and if I wasn’t really interested in that conference or the new product Dutch Cowboys blogged about, I’d probably never go back to those sites. Most Internet visitors would not. I cringe to think about the potential customers lost.

Businesses spend a lot of time and energy on user experience and design, and they don’t think to devote the same level of energy on their infrastructure. In the 90′s, sites crashing or slowing was somewhat acceptable since the interwebs were exploding beyond available infrastructure’s capabilities. Now, there’s no excuse.

If you’re launching a new site, product or application, how do you get started?

The first thing you need to do is understand what resources you need and where the potential bottlenecks are when hundreds, thousands or even millions of people want to what you’re launching. You don’t need to invest in infrastructure to accommodate all of that traffic, but you need to know how you can add that infrastructure when you need it.

One of the easiest ways to prepare for your own success without getting bogged down by the bits and bytes is to take advantage of resources from some of our technology partners (and friends). If you have a PHP, Ruby on Rails or Node.js applications, Engine Yard will help you deploy and manage a specialized hosting environment. When you need a little more flexibility, RightScale‘s cloud management product lets you easily manage your environment in “a single integrated solution for extreme efficiency, speed and control.” If your biggest concern is your database’s performance and scalability, Cloudant has an excellent cloud database management service.

Invest a little time in getting ready for your success, and you won’t need to play catch-up when that success comes to you. Given how easy it is to prepare and protect your hosting environment these days, outages should go the way of the 8-track player.

-@jpwisler

About a year ago, we kicked off a huge effort to give back to the startup community. We jumped headfirst into the world of startups, incubators, accelerators, angel investors, venture capitalists and private equity firms. This was our new ecosystem. We started to make connections with the likes of TechStars and MassChallenge, and we quickly became a preferred hosting environment for their participants’ most promising and ambitious ideas. This ambitious undertaking evolved into our Catalyst Program.

When it came to getting involved, we knew we could give back from an infrastructure perspective. We decided to extend a $1,000/mo hosting credit to each Catalyst company for one full year, and the response was phenomenal. That was just the beginning, though. Beyond the servers, storage and networking, we wanted to be a resource to the entrepreneurs and developers who could learn from our experience, so we committed to mentoring and making ourselves available to answer any and all questions. That’s not just lip service … We pledged access to our entire executive team, and we made engineering resources available for problem-solving technical challenges. We’re in a position to broker introductions and provide office space, so we wanted didn’t want to pass up that opportunity.

One of the superstars and soon-to-be graduates of Catalyst is MODX, and they have an incredible story. MODX has become leading web content management platform (#4 open source PHP CMS globally) by providing designers, developers, content creators and Unix nerds with all the tools they need to manage, build, protect and scale a web site.

Back in December 2011, the MODX team entered the program as a small company coming out of the open source world, trying to figure out how to monetize and come up with a viable commercial offering. Just over 10 months later, the company has grown to 14+ employees with a new flagship product ready to launch later this month: MODX Cloud. This new cloud-hosting platform, built on SoftLayer’s infrastructure, levels the playing field allowing users to scale and reach everyone with just a few clicks of a mouse and not need to worry about IT administration or back-end servers. Everything associated with managing a web site is fully automated with single-click functionality, so designers and small agencies can compete globally.

We’re proud of what the MODX team has accomplished in such a short period of time, and I would like to think that SoftLayer played a significant role in getting them there. The MODX tag line is “Creative Freedom,” and that might be why they were drawn to the Catalyst Program. We want to “liberate” entrepreneurs from distractions and allow them to focus on developing their products – you know, the part of the business that they are most passionate about.

I can’t wait to see what comes out of Catalyst next … We’re always looking to recruit innovative, passionate and creative startups who’d love to have SoftLayer as a partner, so if you have a business that fits the bill, let us help!

-@gkdog

I use the word “model” intentionally there because it’s important to note that cloud computing is not a “thing” or a “product.” It’s a way of doing business. It’s an operations model that is changing the fundamental economics of writing and deploying software applications. It’s not about a strict definition of some underlying service provider architecture or whether multi-tenancy is at the data center edge, the server or the core. It’s about enabling new technology to be tested and fail or succeed in blazing calendar time and being able to support super-fast growth and scale with little planning. Let’s try to keep that in mind as we look at how NIST and Gartner define cloud computing.

The National Institute of Standards and Technology (NIST) is a government organization that develops standards, guidelines and minimum requirements as needed by industry or government programs. Given the confusion in the marketplace, there’s a huge “need” for a simple, consistent definition of cloud computing, so NIST had a pretty high profile topic on its hands. Their resulting Cloud Computing Definition describes five essential characteristics of cloud computing, three service models, and four deployment models. Let’s table the service models and deployment models for now and look at the five essential characteristics of cloud computing. I’ll summarize them here; follow the link if you want more context or detail on these points:

• On-Demand Self Service: A user can automatically provision compute without human interaction.
• Broad Network Access: Capabilities are available over the network.
• Resource Pooling: Computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned.
• Rapid Elasticity: Capabilities can be elastically provisioned and released.
• Measured Service: Resource usage can be monitored, controlled and reported.

The characteristics NIST uses to define cloud computing are pretty straightforward, but they are still a little ambiguous: How quickly does an environment have to be provisioned for it to be considered “on-demand?” If “broad network access” could just mean “connected to the Internet,” why include that as a characteristic? When it comes to “measured service,” how granular does the resource monitoring and control need to be for something to be considered “cloud computing?” A year? A minute? These characteristics cast a broad net, and we can build on that foundation as we set out to create a more focused definition.

For our next stop, let’s look at Gartner‘s view: “A style of computing in which scalable and elastic IT-enabled capabilities are delivered as a service using Internet infrastructure.” From a philosophical perspective, I love their use of “style” when talking about cloud computing. Little differentiates the underlying IT capabilities of cloud computing from other types of computing, so when looking at cloud computing, we really just see a variation on how those capabilities are being leveraged. It’s important to note that Gartner’s definition includes “elastic” alongside “scalable” … Cloud computing gets the most press for being able to scale remarkably, but the flip-side of that expansion is that it also needs to contract on-demand.

All of this describes a way of deploying compute power that is completely different than the way we did this in the decades that we’ve been writing software. It used to take months to get funding and order the hardware to deploy an application. That’s a lot of time and risk that startups and enterprises alike can erase from their business plans.

How do we wrap all of those characteristics up into unified of definition of cloud computing? The way I look at it, cloud computing is as an operations model that yields seemingly unlimited compute power when you need it. It enables (scalable and elastic) capacity as you need it, and that capacity’s pricing is based on consumption. That doesn’t mean a provider should charge by the compute cycle, generator fan RPM or some other arcane measurement of usage … It means that a customer should understand the resources that are being invoiced, and he/she should have the power to change those resources as needed. A cloud computing environment has to have self-service provisioning that doesn’t require manual intervention from the provider, and I’d even push that requirement a little further: A cloud computing environment should have API accessibility so a customer doesn’t even have to manually intervene in the provisioning process (The customer’s app could use automated logic and API calls to scale infrastructure up or down based on resource usage).

Last week, I had the opportunity to speak at Cloud Connect Chicago, and I shared SoftLayer’s approach to cloud computing and how it has evolved into a few distinct products that speak directly to our customers’ needs:

The session was about 45 minutes, so the video above has been slimmed down a bit for easier consumption. If you’re interested in seeing the full session and getting into a little more detail, we’ve uploaded an un-cut version here.

-Duke

If you’ve ever looked at building your own private cloud in the past, the “days, weeks or months” timeline isn’t very surprising — you have to get the hardware provisioned, the software installed and the network configured … and it all has to work together. Hearing that SoftLayer Private Clouds can be provisioned in “hours” probably seems too good to be true to administrators who have tried building a private cloud in the past, so I thought I’d put it to the test by ordering a private cloud and documenting the experience.

At 9:30am, I walked over to Phil Jackson‘s desk and asked him if he would be interested in helping me out with the project. By 9:35am, I had him convinced (proof), and the clock was started.

When we started the order process, part of our work is already done for us:

To guarantee peak performance of the CloudPlatform management server, SoftLayer selected the hardware for us: A single processor quad core Xeon 5620 server with 6GB RAM, GigE, and two 2.0TB SATA II HDDs in RAID1. With the management server selected, our only task was choosing our host server and where we wanted the first zone (host server and management server) to be installed:

For our host server, we opted for a dual processor quad core Xeon 5504 with the default specs, and we decided to spin it up in DAL05. We added (and justified) a block of 16 secondary IP addresses for our first zone, and we submitted the order. The time: 9:38am.

At this point, it would be easy for us to game the system to shave off a few minutes from the provisioning process by manually approving the order we just placed (since we have access to the order queue), but we stayed true to the experiment and let it be approved as it normally would be. We didn’t have to wait long:

At 9:42am, our order was approved, and the pressure was on. How long would it take before we were able to log into the CloudStack portal to create a virtual machine? I’d walked over to Phil’s desk 12 minutes ago, and we still had to get two physical servers online and configured to work with each other on CloudPlatform. Luckily, the automated provisioning process took on a the brunt of that pressure.

Both server orders were sent to the data center, and the provisioning system selected two pieces of hardware that best matched what we needed. Our exact configurations weren’t available, so a SBT in the data center was dispatched to make the appropriate hardware changes to meet our needs, and the automated system kicked into high gear. IP addresses were assigned to the management and host servers, and we were able to monitor each server’s progress in the customer portal. The hardware was tested and prepared for OS install, and when it was ready, the base operating systems were loaded — CentOS 6 on the management server and Citrix XenServer 6 on the host server. After CentOS 6 finished provisioning on the management server, CloudStack was installed. Then we got an email:

At 11:24am, less than two hours from when I walked over to Phil’s desk, we had two servers online and configured with CloudStack, and we were ready to provision our first virtual machines in our private cloud environment.

We log into CloudStack and added our first instance:

We configured our new instance in a few clicks, and we clicked “Launch VM” at 11:38am. It came online in just over 3 minutes (11:42am):

I got from “walking to Phil’s desk” to having a multi-server private cloud infrastructure running a VM in exactly two hours and twelve minutes. For fun, I created a second VM on the host server, and it was provisioned in 31.7 seconds. It’s safe to say that the claim that SoftLayer takes “hours” to provision a private cloud has officially been confirmed, but we thought it would be fun to add one more wrinkle to the system: What if we wanted to add another host server in a different data center?

From the “Hardware” tab in the SoftLayer portal, we selected “Add Zone” to from the “Actions” in the “Private Clouds” section, and we chose a host server with four portable IP addresses in WDC01. The zone was created, and the host server went through the same hardware provisioning process that our initial deployment went through, and our new host server was online in < 2 hours. We jumped into CloudStack, and the new zone was created with our host server ready to provision VMs in Washington, D.C.

Given how quick the instances were spinning up in the first zone, we timed a few in the second zone … The first instance was online in about 4 minutes, and the second was running in 26.8 seconds.

By the time I went out for a late lunch at 1:30pm, we’d spun up a new private cloud infrastructure with geographically dispersed zones that launched new cloud instances in under 30 seconds. Not bad.

Don’t take my word for it, though … Order a SoftLayer Private Cloud and see for yourself.

-@khazard

To make sure we’re all on the same page, as we continue to talk about “cloud,” our definition is pretty straightforward:

• It’s an operations model.
• It provides capacity on demand.
• It offers consumption-based pricing.
• It features self-service provisioning.
• It can be accessed and managed via an API.

Understanding those characteristics, when you hear about cloud in the hosting industry, you’re usually hearing about cloud computing instances in a public cloud environment. An instance in a public cloud is one of many instances operating on a shared cloud infrastructure alongside other similar instances that aren’t managed by you. Your data is still secure, and you can still get good performance in a public cloud environment, but you’re not managing the cloud infrastructure on which your instance resides … You’re using a piece of a cloud.

What we announced at Cloud Expo East is the next step in the evolution of technology in our industry … We’re providing a turnkey, on-demand way for our customers to provision their own Private Clouds with Citrix CloudPlatform, powered by Apache CloudStack.

You don’t get a piece of the cloud. You have your own cloud, provisioned in a matter of hours on a month-to-month contract.

For those who have looked into building a private cloud for their business in the past, it’s probably worth reiterating: With SoftLayer and CloudStack, you can have a geographically distributed, secure, private cloud environment provisioned in a matter of hours (not months). Given the complexity of a private cloud environment — involving a management server, private cloud zones, host servers and object storage — this is no small feat.

Those unbelievable provisioning times are only part of the story … When that cloud infrastructure is deployed quickly, it’s fully integrated into the SoftLayer platform, so it leverages our global private network alongside your existing bare metal, dedicated and virtual servers. Want to add public cloud instances to your private cloud as web heads? You’ll log into one portal or use a singular API to have that done in an instant.

Your own cloud infrastructure, fully integrated into SoftLayer’s global infrastructure. If you’re chomping at the bit to try it out for yourself, email us at privateclouds@softlayer.com, and we’ll get you on the “early access” list.

Before I sign off, I want to be sure to thank everyone at SoftLayer and Citrix who worked so hard to make SoftLayer Private Clouds such an amazing new addition to our platform.

-@nday91

That’s pretty intimidating … Even for tech businesses.

Shifts in technology don’t have to be as drastic and obvious as a “printed newspaper v. social news site” comparison for them to be disruptive. Even subtle advances can wind up making or breaking a business. In fact, many of today’s biggest and most successful tech companies are scrambling to adapt to two simple “game changers” that seem terribly significant:

• IPv6
• “The Cloud”

IPv6

A quick search of the SoftLayer Blog reminds me that Lance first brought up the importance of IPv6 adoption in October 2007:

ARIN has publically announced the need to shift to IPv6 and numerous articles have outlined the D-Day for IPv4 space. Most experts agree, its coming fast and that it will occur sometime in 2010 at the current pace (that’s about two years for those counting). IPv6 brings enough IP space for an infinite number of users along with improved security features and several other operational efficiencies that will make it very popular. The problem lies between getting from IPv4 to IPv6.

When IPv4 exhaustion was just a blip on the horizon, many businesses probably thought, “Oh, I’ll get around to it when I need to. It’s not a problem yet.” When IANA exhausted the IPv4 pool, they probably started picking up the phone and calling providers to ask what plans they had in place. When some of the Internet’s biggest websites completed a trial transition to IPv6 on World IPv6 Day last year, those businesses started feeling the urgency. With today’s World IPv6 Launch, they know something has to be done.

Regardless of how conservative providers get with IPv4 space, the 4,294,967,296 IPv4 addresses in existence will not last much longer. Soon, users will be accessing an IPv6 Internet, and IPv4-only websites will lose their opportunity to reach those users. That’s a “game changer.”

“The Cloud”

The other “game changer” many tech businesses are struggling with these days is the move toward “the cloud.” There are a two interesting perspectives in this transition: 1) The challenge many businesses face when choosing whether to adopt cloud computing, and 2) The challenges for businesses that find themselves severing as an integral (sometimes unintentional) part of “the cloud.” You’ve probably seen hundreds of blog posts and articles about the first, so I’ll share a little insight on the second.

When you hear all of the hype about cloud computing and cloud storage offering a hardware-agnostic Utopia of scalable, reliable power, it’s easy to forget that the building blocks of a cloud infrastructure will usually come from vendors that provided a traditional hosting resources. When a computing instance is abstracted from a hardware device, it’s opens up huge variations in usage. It’s possible to have dozens of public cloud instances using a single server’s multi-proc, multi-core resources at a given time. If a vendor prices a piece of software on a “per server” basis, how do they define a “server” when their users are in the cloud? It can be argued that a cloud computing instance with a single core of power is a “server,” and on the flip-side, it’s easy to define a “server” as the hardware object on which many cloud instances may run. I don’t know that there’s an easy way to answer that question, but what I do know is that applying “what used to work” to “what’s happening now” isn’t the right answer.

The hardware and software providers in the cloud space who are able to come up with new approaches unencumbered by the urge to continue “the way we’ve always done it” are going to be the ones that thrive when technology “game changers” emerge, and the providers who dig their heels in the dirt or try to put a square peg into a round hole will get the short end of the “adapt or die” stick.

We’ve tried to innovate and take a fresh look at every opportunity that has come our way, and we do our best to build relationships with agile companies that we see following suit.

I guess a better way to position the decision at the beginning of this post would be to add a little tweak: “Innovate, adapt or die.” How you approach technology “game changers” will define your business’s success.

-@gkdog

Before I get too far, I should probably back up give you a little context for what the show is all about if you aren’t familiar with it. In his opening keynote, Citrix CEO Mark Templeton explained:

“We call it ‘Citrix Synergy,’ but really it’s ‘Synergy’ because this is an event that’s coordinated by us across a hundred sponsors, our ecosystem partners, companies in the industry that we work together with to bring you an amazing set of solutions around cloud, virtualization, networking and mobility.”

Given how broad of a spectrum those areas of technology represent, the short four-day agenda was jam-packed with informational sessions, workshops, demos and conversations. It goes without saying that SoftLayer had to be in the mix in a BIG WAY. We had a booth on the expo hall floor, I was lined up to lead a breakout session about how business can “learn how to build private clouds in the cloud,” and we were the proud presenting sponsor of the huge Synergy Party on Thursday night.

Our partnership with Citrix is unique. We incorporate Citrix NetScaler and Citrix XenServer as part of our service offerings. Plus, Citrix is also a SoftLayer customer, using SoftLayer infrastructure to offer a hosted desktop solution. Designed and architected from the ground up to run in the cloud, the Citrix Virtual Demo Center provides a dashboard interface for managing Citrix XenDesktop demo environments that are provisioned on-demand using SoftLayer’s infrastructure.

My biggest thrill at the conference came when I was asked to speak and share a little of our expertise in a keynote address on simplifying cloud networking. I like to tell people I have a great face for radio, but that didn’t keep me off the stage. The hall was packed to capacity and after defeating a few “demo gremlins,” I got to show off how easy SoftLayer makes it for our customers to take advantage of amazing products like Citrix Netscaler VPX:

In my “Learn How to Build Private Clouds in the Cloud” breakout session, I had a little more time to speak to the larger question of how SoftLayer is approaching the shift to cloud-specific architectures and share some best practices in moving to a private cloud. Private clouds are a great way to provide real-time service delivery of IT resources with a single-tenant, customized, secure environment. However, the challenge of scaling and managing physical resources still exists, so I tried to explain how businesses can leverage an Infrastructure-as-a-Service provider to add scalability to a private cloud environment.

Thanks to SynergyTV, that presentation has been made available for all to see:

As I joked at the beginning of the breakout session, an attendee at Citrix Synergy was probably bombarded by “the cloud” in presentations and conversations at the show. While it’s important to demystify the key terms we use on a daily basis, a few straight days of keynotes and breakout sessions about the cloud can get you thinking, “All work and no play makes Jack a dull boy.” Beyond our capabilities as a cloud infrastructure provider, SoftLayer knows how to have a good time, so after we took care of the “work” stuff in the sessions above, we did our best to help provide a little “play” as well. This year, we were the proud sponsor of the Synergy Party, featuring Lifehouse!

Citrix Synergy 2012 was a blast. As a former rocket scientist, I can say that authoritatively.

-@nday91

Cutting out the Middleman with Nexmo

These days, optimizing mobile messaging deliverability comes at a price. Businesses must connect to multiple carriers, operate heavy infrastructure, and build their own data analytics. On top of that, many third-party SMS solutions require contracts, price negotiations and significant up-front costs.

Nexmo was created to eliminate the need for a business to connect to carriers or complex third party protocols through simple, powerful RESTful and SMPP APIs. Our scalable infrastructure allows you to send and receive SMS in high volumes to over 5 billion users around the world. This is a market need that hasn’t been addressed, and we approached it with a few ideas in mind. If you were going to replicate the functionality of Nexmo on your own, these are the key areas you’d have to look at:

Direct to Carrier Model

With every hop, the quality of a connection has the potential to degrade, and cost inflates. Adding intermediaries in the chain also impact the granularity of collected data, such as delivery reports and reasons of failure. By reducing the number of hops to the final subscriber you’ll see:

• An improved delivery ratio and lower latency
• Enhanced security
• Fewer single points of failure
• Reduced cost, less fat in the chain

With a closer position to the final carrier, a business can access more “Telco” data like phone status, whether it is ported to another network, or if it’s roaming abroad. With that information, you can also make better routing decisions and ultimately see higher delivery ratios.

Get Your own SMS-Enabled Phone Numbers

We’ve seen in the last two years the emergence of “Over the Top” (OTT) messaging apps such as Google Voice and TextPlus. Those apps provide a virtual phone number to each user, and Nexmo behaves similarly by enabling apps to behave like a “super virtual carrier” without the need for heavy Telco infrastructure. North America is the most mature market with OTT players generating significant SMS traffic, and now these models are going abroad. We pinpointed a unique need in the value chain:

• Source virtual phone numbers from global carriers
• Build the business models that protect carriers’ interests without eliminating the opportunity for innovative apps
• Provide the elastic and scalable cloud infrastructure for high volume two-way transactions

Nexmo approached those needs with APIs that enabled app developers to search for available phone numbers, provision new numbers and cancel numbers they weren’t using any more. It doesn’t take days or weeks to launch in a new market … Apps can launch in a new market in a matter of hours with minimal upfront investment!

Improve and Track Deliverability

Enterprises and developers have shifted the focus in the buying process. They are looking for more transparency and accountability, so tracking and monitoring hundreds, thousands or even millions of messages can be of utmost importance.

For every SMS sent, the Nexmo API provides a detailed report of delivery. We push this data into the cloud in real time, displayed in two ratios:

• The Success Ratio: The percentage of message received by the phone. This ratio measures how well traffic is performing.
• The DLR Ratio: The percentage of messages with a delivery receipt. This ratio tracks infrastructure and route performance.

Follow the Life of a Message from the Cloud

Most B2C services and resellers that send millions of SMS for things like alerts, phone verifications and access codes can get swarmed when it comes to user support. We know that’s an intimidating prospect for any business looking to add SMS functionality to their app or platform, so we let our customers follow the life of a message from the cloud and gather more information about it. Some of the information we’ve found most helpful to track:

• How fast was the message was delivered?
• Was the phone available for receiving SMS?
• Did the user enter the correct phone number?

Keeping an eye on these basic kinds of stats reduces the pain of supporting a large user base and enables your support staff to answer questions quickly because they have a good foundation of information.

Receive Outstanding Support

Building a customer centric culture is a sustainable competitive advantage. It is even more meaningful in a commoditized, price-driven industry like wholesale telecom. If you’re going to approach the world of SMS messaging and deliverability, the need for outstanding support is even more urgent because, given the nature of SMS messaging, results are expected immediately.

When we started Nexmo, we knew that, and I’m proud to report that we constantly score over 95% in customer satisfaction, and we’ve noticed a few tricks that have helped us maintain that level of support:

• Hire the right people: Empathy and service mindset are more important than technical skills
• Provide self-help tools and open knowledge bases: Customers appreciate finding solutions by themselves
• Measure help-desk performance and constantly improve: KPI includes first meaningful reply time, resolution time and satisfaction ratio.

We hope these tips can help you build on your existing support or give you a jumping-off point if you’re just getting started.

There is so much more I could tell you about our experience in building Nexmo into the platform it is today, but it’s a lot easier for you to just see for yourself. If you’re interested in learning more about Nexmo, visit http://nexmo.com, sign up, and be ready to go live with us in a matter of minutes … And to make it even easier, you can use the free credits we provide to give the platform a test drive.

If you’ve been intimidated by the daunting task of knocking on the doors of telcos and carriers to get easy-to-use and easy-to-track SMS functionality in your app, Nexmo can save you a lot of headaches.

-Tony Jamous, Nexmo