Serverless Software

Developers may never see groups of servers like this again in the future.

Developers may never see groups of servers like this again in the future.

I love the words “loosely coupled.” At times in my career, I’ve built software and have aimed to ensure that processes, workflows, and components worked well on their own. In the places where I had to work with data or services on different physical machines, I tried to ensure that each item would run separately, and communicate when needed, but wouldn’t fail if another machine was down.

That’s kind of the idea proposed in the article that says the future of software is serverless? It’s an interesting read, talking about the advances in cloud services that can change the way developers build applications. Developers should think about liking services, and pieces of applications, ignoring the idea their systems are tied to specific servers.

It’s a future that I think makes sense for most environments. Development shouldn’t be concerned about the size or care of physical machines. Instead they should think about building on a platform of services, and expecting the scale to grow or shrink as needed, without code changes.

I do think this could be the future in which development proceeds inside companies, as well as for commercial software. However vendors need to sell “private clouds” which function in the same way as the public ones, for those companies that want to control, and invest in, their own hardware.

Steve Jones

The Voice of the DBA Podcasts

We publish three versions of the podcast each day for you to enjoy.

About way0utwest

Editor, SQLServerCentral
This entry was posted in Editorial and tagged . Bookmark the permalink.

One Response to Serverless Software

  1. As we move into “Cloud” type environments I’ll be interested to see how performance tuning evolves. One of the biggest pressures I’ve seen that “forces” developers to tune their code is slow performance caused by increased usage and or data. Even in current environments I see cases where poorer performing code is masked/supported by the fact that other applications/code sharing the same space are tuned as a matter of course. So one application may be using 75% of the resources, but no one notices because even though that application may be one of a dozen, and possibly not even the largest, all of the other applications are designed to do more with less.

Comments are closed.