Posts Tagged: Development

Cloud Services Estimator: Now Open Source for the Channel

February 24, 2015
By Nathan Young, Creative Director

CenturyLink Cloud Price Estimator

The advent of cloud computing has brought about one of the largest business opportunities in decades for managed services providers, system integrators and VARs many of whom have adapted their business models to offer the agility provided by elastic infrastructure.

CenturyLink has been a popular destination for enterprises and partners alike, with some of our partners choosing to white label and resell our product. The capabilities that enable this are a major differentiator of our platform. We constantly look for ways to enable our partners to pass value onto their customers and today we are happy to add another tool to their belt.

We are pleased to announce that we are contributing our Cloud Cost Estimator tool to the open-source community under the Apache 2 license. This web app makes it easy to estimate a monthly bill for a customized set of resources on the CenturyLink Cloud service.

As we’ve marketed cloud to our own end user customers, this estimator has been an invaluable tool to help buyers understand the costs associated with building and managing apps in the cloud. Deep visibility and monitoring coupled with showback and chargeback capabilities extend the value once resources are up and running.

Now, our channel partners can...

Read on...

PaaS First; IaaS Second: Five Reasons to Select Your PaaS First

April 1, 2014
Originally Posted On AppFog.com

Are you building your cloud application directly on the Infrastructure-as-a-Service (IaaS) provider vs. using a Platform-as-a-Service (PaaS)? In recent conversations with dozens of cloud application developers I’ve found many developers are still choosing to build their application using services offered by the IaaS (Infrastructure-as-a-Service) provider, e.g., Amazon (AWS), Rackspace or other IaaS providers vs. using a PaaS between the application and the infrastructure. In nearly every instance I find the primary reason for selecting an IaaS first was that the development team didn’t fully understand the benefits of a PaaS or didn’t know how to evaluate one.

We recommend to our clients that they select their PaaS first and then select the IaaS provider that best supports their selected PaaS. By developing your application using a PaaS, you can lower the total cost of ownership of your application by 30% or more. With the right PaaS, you also gain the freedom to change cloud infrastructure providers over-time and avoid infrastructure vendor lock-in by making your application portable to any IaaS provider.

We see five primary reasons for using a PaaS:

Reduced Operations Cost – we generally find that 30% or greater of development time can be consumed in DevOps functions. A PaaS will...

Read on...

New horizons in Node.js: App.js and WebRTC

September 4, 2013
Originally Published On AppFog

New horizons in Node.js: App.js and WebRTC

It’s hopeless trying to keep up with developments in the Node.js community. Believe me, I’ve tried.

Once upon a time, I held out hope that I would be able to keep my finger on the pulse of Node-related discourse, but it all turned out to be in vain. New modules are added and updated to npmjs.org on an almost minute-by-minute basis. It’s enough to make your head spin (in a good way, if that makes sense). However, there have been a few big and bold movements in the Node.js space that have caught my attention recently that I think are incredibly promising and that I just couldn’t keep to myself: desktop client creation with App.js and WebRTC.

Make some room, Qt: App.js is the new kid in town

Did you ever want to use JavaScript to construct a rich UI experience in a non-browser setting? Well, now is your chance. Did it never even occur to you to try such a thing? Well, that’s okay, too, because I always assumed that I would have to learn C++ to ever accomplish such a thing. But playing around with App.js, which is available as an NPM module, has convinced...

Read on...

Traditional vs PaaS hosting

August 4, 2013
Originally Published On AppFog

Traditional vs PaaS hosting

Comparing a platform-as-a-service (PaaS) to traditional hosting like VPS/shared hosting (e.g. DreamHost, Host Gator, GoDaddy) or infrastructure-as-a-service hosting (e.g. Amazon Web Services, Linode, CenturyLink Cloud) is like comparing apples and oranges. One must look beyond hardware and price to get a true cost/value when picking a hosting provider.

Shopping for traditional hosting is too much like shopping for breakfast cereal: many mediocre options, little differentiation, annoyances for up-sell.

Traditional hosting… (aka “do it yourself”)

With traditional hosting developers have many responsibilities before they can even touch a line of code. Lets look at some of these responsibilities…

Set up the application server (e.g. Apache, Nginx, etc.) Set up MySQL database Setting up the run-time platform like PHP, Ruby, etc Something isn’t working. Diagnose, re-configure/re-setup, try again. Dependencies… right, have to setup those up too. Setup FTP to deploy your code. Setup security and firewall. It worked on localhost, why isn’t it working now!!!

As you can see, before you get to the code, you’ll have to spend hours getting your production environment in a state which is just barely good enough to host your application. If you want your application to be reliable, scalable, and resilient against various failures, you’ll have to deal with additional issues like setting...

Read on...

Putting the MOVE framework in proper perspective

August 4, 2013
Originally Published On AppFog

Putting the MOVE framework in proper perspective

In a recent post, on data models and persistence, I made what I now realized to be a pretty fundamental mistake: I talked about the use of data models in web development, but I restricted my discussion to MVC-style frameworks alone and should have said more about alternative design patterns.

I restricted my discussion in this way more for the sake of brevity than anything else, but I’ve learned a lot in the last few weeks about alternative architectures and want to begin weighing in. Next week, I will discuss Knockout.js’s MVVM (model-view-view model) front-end architecture and the abstraction gains associated with it. But first, I want to discuss another alternative to MVC that’s been getting a lot of traction on the webs in the last few days: the MOVE framework, as outlined by Conrad Irwin.

MOVE is an (admittedly quite clever) acronym for Models-Operations-Views-Events. What the term seeks to capture is an emerging way of structuring applications that doesn’t rely on an explicitly defined and coded controller. The problem, according to Irwin, is that quite often “you end up stuffing too much code into your controllers, because you don’t know where else to put it.”

A...

Read on...

Optimizing JavaScript for the V8 Engine

August 4, 2013
Originally Published On AppFog

Optimizing JavaScript for the V8 Engine

For those of you like myself that didn’t have the good fortune of going to Google I/O, I hope you caught this video, “Breaking the JavaScript Speed Barrier:”

As an aspiring developer, this was far and away the most intriguing and helpful video from the conference. This talk, delivered by Google’s Daniel Clifford, provides a number of essential guidelines for writing JavaScript that is better optimized for running on Google Chrome’s V8 JavaScript Engine. Google has been doing pretty incredible things in the last few years with JavaScript, improving benchmarks and narrowing the speed gap between JavaScript and other languages that was once thought to be unbridgeable.

We should be grateful that Google has invested so much time and energy into optimizing JavaScript performance. It has never been more important as a language, and its star is unlikely to fade anytime soon. For Clifford, optimizing JavaScript performance not only helps us do the same old things faster and better. It also broadens our development horizons and transforms the kinds of things that are possible, especially in the sphere of front-end development.

I won’t give a fully fleshed-out summary of the talk, as I would recommend watching it on...

Read on...

The developer’s toolkit: Swagger

August 4, 2013
Originally Published On AppFog

The developer’s toolkit: Swagger

I know what you’re probably thinking: I’ve written this post to recommend developers to add swagger (note the small “s”) to their existing set of skills and attributes. While I certainly do not disrecommend swagger as a character trait, my purpose today is instead to talk about the Swagger (note the big “S”) API documentation and exploration tool.

Swagger enables you to transform your API into a sleek UI that makes it vastly easier for third-party users to see an exhaustive list of what your API offers, how requests are matched with URLs, and what the server will return in response to specific requests.

Swagger also provides a sandbox UI for experimentation with APIs. Have a look at the demo UI. What you find there is an API for a hypothetical pet store. If you click on “/pet” for example, this will open up a menu of all of the HTTP requests associated with that directory.

If I want to see what pets are available with the ID “Fido,” I simply need to open up the menu bar associated with GET /pet.json/{petId} requests, insert “Fido” into the text field, and hit the “Try it out!” button to get the API’s...

Read on...

Twitter Bootstrap and the rise of total front-end frameworks

August 4, 2013
Originally Published On AppFog

Twitter Bootstrap and the rise of total front-end frameworks

It’s no secret that there’s lots and lots going on in back-end web development these days. As an example, debates surrounding node and asynchronicity, to give just one example, have reached a fever pitch and have occasionally felt more like philosophical arguments than technical arguments.

The same has been true for debates between “thick” frameworks like Rails and Django versus “thin” frameworks like Sinatra, Flask, and Express. On top of these issues, we’re also witnessing an explosion of creativity in the world of full-stack frameworks (Padrino for Sinatra, Tower.js for node, etc.). (More on this very soon, so be sure to hit a subscribe link on the right)

But what has surprised me recently is that similar developments are afoot in the world of front-end development. The shining example par excellence: Twitter Bootstrap.

Bootstrap was essentially a big, juicy bone thrown to the web development community by Mark Otto and the folks in the design department at Twitter. The purpose is to allow third-party developers to easily lend some much-needed aesthetic consistency to the world of Twitter-related web apps, which now number in the hundreds of thousands (see this article by Drew Heatley, which gives...

Read on...

Why Cloud Foundry matters to Hackers

August 4, 2013
Originally Published On AppFog

Why Cloud Foundry matters to Hackers

Unless you live under a rock, you have heard of Cloud Foundry. However there is still a lot of skepticism out there about PaaS in general and Cloud Foundry in particular.

I’ve been an open source hacker for over a decade. Compiling linux kernels, hacking MySQL, and generally getting my hands into every system that I could. I have also authored over a dozen open source libraries, some being used widely.

When I saw PaaS in the early days, with EngineYard and Heroku, I thought it was really cool and inspiring. Like many hackers though, it is hard to trust something or fully enjoy it when you can not get under the hood.

Why does Cloud Foundry matter?

EDIT — It is a great PaaS. As the first commentator noted, none of this matters if the technology sucks. Cloud Foundry is a great, easy to use technology that works reliably, simply, and smartly. It supports many languages and many services. To a hacker and tinkerer, it is a haven for fun.

It is well designed. Example: A message bus acts as a nerve center to various components via pub/sub. For example, when a new app server comes online, it subscribes...

Read on...

The developer’s toolkit: HTTPie

August 4, 2013
Originally Published On AppFog

The developer’s toolkit: HTTPie

Make no mistake: for people who hack on UNIX-based systems, curl is a really powerful command. It enables you to extract the client-side content of any web page in an instant and also to do all kinds of things with the result, like dumping it into a .txt file (a trick which has been extremely useful to me in learning web development).

But the curl command doesn’t always function all that intuitively on the input side, and the output always comes out monochromatic, making it difficult to immediately discern what’s going on in the stream of text you’re presented with in the CLI.

HTTPie, in the words of its creator, was built “out of frustration with existing tools.” It provides the capacity to make both more intuitive requests and polychromatic output. Using it couldn’t be any more simple. The commands underlying an HTTPie request look like this in generic form:

http [flags] [METHOD] URL [items] Let’s have a look at a sample POST request (taken from HTTPie’s GitHub readme):

http --form POST api.example.org/person/1 name=’John Smith’ email=[email protected] The equivalent request done with the curl command:

curl --data “name=John+Smith&email=john%40example.org” api.example.org/person/1 Requests in HTTPie aren’t necessarily significantly less verbose than curl requests. But that’s not their primary function....

Read on...

Two reasons why PaaS is so much more than automation

August 4, 2013
Originally Published On AppFog

Two reasons why PaaS is so much more than automation

Bruno Terkaly is a heck of an interesting and intelligent guy. I suggest you check out his many videos and writings. As a fellow developer evangelist, I look up to Bruno a lot. And like him, I’m heavily invested in the platform-as-a-service (PaaS) paradigm. And so when I came across this piece of his from a while back, I couldn’t help but devour it and ruminate on it for several days. It’s an impressive bit of thinking but I feel that there are some serious problems with his understanding of PaaS.

The argument of the piece, titled “Why Platform as a Service (Robotics) will rule the world,” is essentially this: PaaS will rule the (cloud) world because the principle behind PaaS is automation, and automation is the core of a “radical technology revolution” that is slowly but surely making our global digital architecture more efficient. Terkaly even goes as far as to equate PaaS and “robotics” in the very title of the piece. The premise is that PaaS essentially roboticizes cloud infrastructure and thereby makes it vastly more efficient and easier to use.

How does this roboticized system work? The answer lies in...

Read on...

The magic of not-even-rendering: on Knockout.js

July 4, 2013
Originally Published On AppFog

The magic of not-even-rendering: on Knockout.js

In a number of casual–and sometimes not-so-casual (!)–discussions about client-side JavaScript libraries, I’ve noticed that people have an unfortunate tendency to lump them all into a single amorphous blob. Backbone? Ember? Angular? Knockout? They all do something-or-other involving structuration on the front end; they’re all more or less the same thing.

WRONG!!!

There are indeed deep similarities between these libraries in terms of what they offer developers, but understanding their differences means understanding which use cases they’re best suited for. Here, I’ll make a foray into this discussion by outlining some of the basic characteristics of Knockout.js I’ve discussed Backbone previously, and I’ll discuss the others in a future post.

According to Knockout creator Steve Sanderson in this video, Knockout, like many other libraries, was meant to provide “rich client-side interactivity.” HTML and the DOM are never ever ever going to provide you this on their own. What you see is what you get. In 1992, that was just fine. In 2012 we expect a whole lot of interactivity on the client side, but this kind of interactivity can’t be built on sand. Doesn’t a library like jQuery get us there? Well, not quite.

Binding jQuery to an underlying

...

Read on...

What is NoOps anyhow

July 4, 2013
Originally Published On AppFog

What is NoOps anyhow?

Since having our infographic published on GigaOm, there has been a lot of controversy and FUD around “NoOps”. Paul Graham recently wrote about schlep blindness. NoOps is a response to the schlep blindness of developers doing SysOps.

What does NoOps mean:

NoOps means developers can code and let a service deploy, manage and scale their code NoOps means automated systems like CloudFoundry managing app lifecycles, not SAs “the point isn’t that ops are going away, but they’re going away for developers” – Derrick Harris at GigaOm

What does NoOps NOT mean:

NoOps doesn’t mean that operations are dead and nobody will do them (like this tweet thinks) NoOps isn’t a job role (like this tweet and this tweet thinks) NoOps isn’t blissful ignorance (like this tweet thinks) NoOps isn’t marketing fluff made up by non-technical idiots (like this tweet and this tweet thinks) This is the true spirit of NoOps:

“Netflix runs NoOps … Netflix is a much larger example of a PaaS based NoNops organization … We claim a competitive advantage from the agility and automation of a PaaS based product and a NoOps organization.” – Adrian Cockcroft, Cloud Architect at Netflix (read more)

The growth of the SysOps movement has been driven mainly by developers who...

Read on...

AngularJS: the beauty of concision

June 4, 2013
Originally Published On AppFog

AngularJS: the beauty of concision

Some of you might remember a Backbone blogging engine I made a while back. It certainly wasn’t the most advanced use case for Backbone, but I think that it did a decent job of elucidating some of Backbone’s features: event-driven responsiveness, templating, collections, and so on. It was also a great learning experience and my first foray into thick client-style development.

But then a few weeks ago, a number of trusted friends and colleagues began raving about AngularJS. Curious about what the fuss was about, I began doing some exploring, looking at sample apps, reading the API docs, and watching a few videos, and it became abundantly clear that Angular is an almost shockingly powerful library. I was surprised by the kinds of heavy lifting that can be accomplished with little effort. And so I set out to see how concisely I could re-implement my Backbone project in Angular.

I was quite pleased with the result.

Getting started

The first thing you need to do is specify within your <html> tag itself–I know, crazy, right?–that your HTML page is going to be staging an Angular app. Instead of the typical <html> tag, you need to insert a <html ng-app> tag...

Read on...

Highly-Available, Region-Specific, Elastic Storage – “Out of the Box”

May 19, 2013
By Richard Seroter, Senior Product Manager. Find Richard on Twitter

We generate massive amounts of data every day. Research firm IDC estimates that 90% of the world’s data was created in the last two years, and the volume of data worldwide doubles every two years. Enterprises are a key contributor to this data explosion as we produce and share digital media, create global systems that collect and generate data, and retain an increasing number of backup and archive data sets. This rapid storage growth puts pressure on IT budgets and staff who have to constantly find and allocate more usable space. CenturyLink Cloud wants to help make that easier and just launched a new Object Storage service to provide you a secure, scalable destination for business data.

What is Object Storage from CenturyLink Cloud? It’s a geo-redundant, elastic storage system for public and private digital data. Based on the innovative Riak CS Enterprise platform, Object Storage infrastructure is being deployed across three global regions: Canada, United States, and Europe. Each region consists of a pair of CenturyLink Cloud data centers that run Riak CS Enterprise on powerful, bare-metal servers. The Object Storage nodes are deployed in a “ring” configuration where data is evenly distributed across the nodes, thus assuring that your...

Read on...

Codenvy Cloud IDE Now Directly Supports CenturyLink Cloud Platform as a Service PaaS

April 6, 2013
By Richard Seroter, Senior Product Manager. Find Richard on Twitter

Just a couple weeks ago, we looked at how Platform-as-a-Service (PaaS) helps developers rapidly build and deploy applications to the cloud. We also covered a new breed of cloud-based development environments (IDE) that developers can use to create and publish their web applications. Since then, the cloud-based IDE we featured – called Codenvy – has updated their product to support the CenturyLink Cloud Platform as a Service. In this post, we’ll walk through how to quickly and easily deploy and manage Platform as a Service applications from your web browser.

To start with, when users of Codenvy start a new web application project, they are asked which technology they want to use, and then which PaaS to deploy to. At this moment, the CenturyLink Cloud Platform as a Service is available for Java Web Application (WAR), Java Spring, and Ruby on Rails projects. Note that Platform as a Service works with more environments than these three, but these are the technologies supported via Codenvy.

Codenvy Cloud IDE

Once the user chooses the technology and corresponding PaaS, they choose a simple project template (if one exists for that technology), and are then asked for the management API endpoint of the Platform as a Service environment.

Codenvy Cloud IDE

The project...

Read on...

Quite possibly the best Rails tutorial in existence

April 4, 2013
Originally Published On AppFog

Quite possibly the best Rails tutorial in existence

One of the best things about learning Rails has been the community. It’s amazing to see how many great tutorials and guides and forms of documentation have been created out there for beginners, even absolute beginners (as I very, very recently was).

The guides section of the Ruby on Rails website itself was, of course, very helpful in walking me step by step through installing rails and walking me through the various files and folders associated with the directory of any Rails app. I highly recommend it. And this video from Jeffrey Way is the best resource I’ve found so far for making the jump from just feeling your way around Rails into actually doing something with it (a chasm that I’m hoping to cross very soon).

But the very best thing that I’ve found so far, which will be useful for both beginners and those entering a more intermediate phase, is Michael Hartl’s t tutorial on railstutorial.org. What makes this tutorial stand out for me is its thoroughness. Plenty of tutorials walk you through step by step, but Hartl’s tutorial deals with a variety of crucial issues from the very get-go, including writing your own...

Read on...

Everybody Loves PaaS; PaaS is Failing

April 1, 2013
Originally Published On AppFog

In the beginning, Platform-as-a-Service (PaaS) was created for developers, not for enterprises. Developers could deploy and test applications within minutes, not days, weeks or months. PaaS enabled developers to sidestep the need to invest in a platform of their own (or mess with jumping the IT queue). And Developers found it good. Agility and velocity became the primary drivers for moving workloads off-premise and into public clouds. As a result, PaaS rapidly became the preferred platform for cutting-edge startups and ambitious developers within small and large organizations.

Low introductory prices made it easy for developers and executives to adopt PaaS as their platform; and everyone enthusiastically embraced the agility and velocity they realized through PaaS. Even corporate IT executives saw the upside of PaaS: faster application development reflects well on them. But they saw a downside, too, especially as business units went off the reservation for PaaS suppliers. The lack of central control complicated management of corporate system and created potentially serious liabilities because the integration points were unclear and complicated. The first PaaS providers ignored all of these concerns, even claiming that incumbent systems “didn’t exist” because they weren’t focused on enterprises.

But these days, early PaaS success is making the...

Read on...

It’s Hard to be Number One

April 1, 2013
Originally Posted On AppFog

Now that PaaS has become the hot topic in the Cloud – and now that Enterprise customers are starting to sign those 9 figure contracts for PaaS providers – we’re starting to see the sort of negative marketing that has long been the trademark of Enterprise Software. This is sad, but inevitable. At present the negative marketing seems to largely be targeted at the leaders in the space and seems to largely consist of FUD.

While normally we would simply ignore this kind of thing – a recent post on the Apprenda blog about Cloud Foundry does, in our opinion, require a response. We have been partners with VMware and Cloud Foundry from early in Cloud Foundry’s existence. We are big fans of Cloud Foundry and AppFog is built to support Cloud Foundry. As such we are a part of the ecosystem that Sinclair talks about. Given his basic thesis, we should be worried sick about VMware and should be fighting to find different alternatives.

Nothing is further from the truth.

FUD: What VMware is doing with Cloud Foundry will collapse the ecosystem!

In looking at the post, the entire thesis is that “more cloud” is a bad thing and that by helping enterprises...

Read on...

The Simplest Way to Build and Deploy Web Applications to the Cloud? Use PaaS and Cloud IDEs!

March 17, 2013
By Richard Seroter, Senior Product Manager. Find Richard on Twitter

Web applications are a dominant part of most enterprise IT portfolios and Platform-as-a-Service (PaaS) products offer a compelling way to easily deploy and manage these applications. However, PaaS have proven tricky for vendors to explain, and therefore difficult for customers to understand. In this post, we’ll discuss the reason you should consider using PaaS products, what CenturyLink Cloud has to offer, and how you can deploy a web application to a PaaS in a matter of minutes.

Benefits of PaaS

What exactly is PaaS? Basically, it’s a way of delivering an application platform as a service. Developers don’t interface directly with infrastructure (e.g. servers, networks, load balancers) but rather, focus on building and deployment applications through a set of exposed services in a managed fabric. PaaS simplifies the deployment and management of modern web applications while making those applications more resilient and functional. How can PaaS add value to your organization? Let’s drill into some specifics:

  *Reduce server sprawl with a centralized host for web applications. How many web servers are sitting relatively idle in your data center because they are only running a handful of applications? Server sprawl can be a major issue as each IT project requisitions its...

Read on...

Tutorial: RabbitMQ + Node.js

March 4, 2013
Originally Posted on AppFog

I am very excited about the RabbitMQ & Node.js fucntionality. I got the ball rolling with a Redis/Sinatra tutorial, and now I want to show you how to get started with RabbitMQ in a basic Node.js app.

I picked Node for this app because I’ve been pretty heavily embedded in Node-world recently, but I would recommend using RabbitMQ in conjunction with the many clients that exist in a variety of languages and frameworks. This tutorial will cover only the very basics.

Getting started: dependencies and server setup

First things first, make sure that you have RabbitMQ installed on your machine.

I’m of the opinion that getting dependencies right can save you from a lot of headaches down the road, I always start a new Node app with my package.json file. In this example, I’ll be using an Express server (still the standard for Node, and with good reason) and the amqp module as my RabbitMQ client. Here’s what my package.json file will look like:

{ “name”: “af-rabbitmq-example”, “version”: “0.0.1”, “scripts”: { “start”: “node app” }, “dependencies”: { “express”: “*”, “amqp”: “*” } } Now, I’ll run the usual npm install and won’t have to fuss with...

Read on...

Docker and the Future of the PaaS Layer

March 4, 2013
Originally Published On AppFog

Docker and the Future of the PaaS Layer

Brief intro to Docker

You know what’s pretty easy nowadays? Throwing a bunch of processes onto a server running somewhere far away. Dozens. Thousands. Millions. As many as you want. This was really, exasperatingly hard just a few years ago. But Amazon Web Service, CenturyLink, and other players have come along to make this pretty painless.

But you know what’s still really hard? Making those processes completely self-contained and yet running on one kernel and manageable from a single interface. This is the problem that Docker was meant to solve.

Docker chose to address this problem by building a developer-friendly abstraction layer on top of Linux containers (LXC). LXC is a powerful concept, but it simply wasn’t built as an intuitive interface. It’s a pain to use and prohibitively complicated for anyone but the most adept Linux power users.

And so the idea of enabling developers of all stripes to actually use them in a way that gets rid of tons of conceptual overhead and streamlines the use of containers into an actual runtime that makes real sense amounts to a massive win over the more low-level containerization tools that already exist.

Docker takes LXC and constructs a...

Read on...

LinkedIn brings some sanity to the node.js debate

March 4, 2013
Originally Published On AppFog

LinkedIn brings some sanity to the node.js debate

If you’re anything like me, you’re probably pretty sick of the whole node.js debate. Node has been called cancer (which Ted Dziuba called it in a rant which isn’t linked here because it has now been removed from his personal web page). It’s probably been called much worse. It’s been sardonically labelled as bad-ass rock star tech in an admittedly hilarious video. You’re probably even sick of talking about how stale this discussion has become.

Fortunately, the node community couldn’t be bothered with any of this malarkey. They’ve been quietly adding something like 50 to 100 new modules a day to the Node package manager (NPM) library. Node hasn’t even seen a 1.0 release yet–actually, they just released version 0.8.0 on June 25th–but it has already come light years as a framework and now has a developer ecosystem surrounding it that could well be unparalleled in the open source community.

Now, there are signs that the discussion surrounding it is maturing as well. This article by Shravya Garlapati, discussing LinkedIn’s use of node, came into my Hacker News feed the other day, and it’s really a breath of fresh air.

Why? Because it’s the kind of...

Read on...

Why JSON will continue to push XML out of the picture

March 4, 2013
Originally Published On AppFog

Why JSON will continue to push XML out of the picture

The world’s digital infrastructure is currently characterized by a plethora of data interchange formats. It’s not the least bit surprising that such a multiplicity undergirds things at the moment. The internet is scarcely a generation old, while the “Internet of Things” and “Big Data” more closely resemble regulative ideals than realities. But I nonetheless believe that there are strong, discernible historical tendencies currently at work in this field, tendencies that strongly favor JSON over others.

Ten years ago, XML was the primary data interchange format. When it came on the scene, it was a breath of fresh air and a vast improvement over the truly appalling SGML (Standard Generalized Markup Language). It enabled people to do previously unthinkable things, like exchange Microsoft Office documents across HTTP connections. With all the dissatisfaction surrounding XML, it’s easy to forget just how crucial it was in the evolution of the web in its capacity as a “Swiss Army Knife of the internet.”

But it’s no secret that in the last few years, a bold transformation has been afoot in the world of data interchange. The more lightweight, bandwidth-non-intensive JSON (JavaScript Object Notation) has...

Read on...

Node.js is taking over the Enterprise – whether you like it or not

February 4, 2013
Originally Published On AppFog

Node.js is taking over the Enterprise – whether you like it or not

The question is no longer if Node is enterprise ready. The question now is the following: what major digital enterprises will end up being the last hold-outs?

There’s now no question whatsoever that Node is far more than a flash in the pan. The question nowadays is not whether or not Node will break out of its so-called “hipster hacker” bubble, but rather how much of the digital world it will conquer.

In spite of all of the early FUD directed at the Node community and arguments that you shouldn’t use Node for anything much less for enterprise-ready web development, a pretty sizable chunk of the corporate world has gotten on the train.

It turns out that the same things that made hackers fall in love with Node are more or less the same reasons why enterprises are turning to it. In a world in which we want information pipelined to us in real time and in which technological advancements like open APIs and distributed computing have made that possible in once-unprecedented ways, then it’s no surprise whatsoever that the contemporary digital marketplace would begin looking for tools to not just...

Read on...

New Control Panel Interface!

July 6, 2012

We are pleased to announce our new control panel interface with the following new features:

New dashboard page that shows the account billing summary and also overall bandwidth for the account. Increased logon performance by 10x so that you wont have to wait for the dashboard page to load. New server list page that shows the CPU, Storage Allocation, and Memory usage. Server Price calculator now shows the hourly cost of each component of a server before build out. and much more!

The new interface is part of a big effort to optimize the user experience for all of our customers and increase overall speed in gaining access to critical data. There are over 50 additional bugs fixed in this latest build. Thanks CenturyLink Cloud Team

...

Read on...