Skip to main content

The Database Is Dead - Gartner

Very amusing story in zdNet about how since individual devices will eventually all have RFID on them, a database is no longer required - just realtime access to where things are - right?

Well, if you read further into the article, it's not that it's about databases themselves (hopefully Feinberg isn't so naive as to think that tracking numbers isn't a job for a database- but then who knows) - but rather it's the DBAs.

The quote:
a point made by the Gartner analysts is that there's a bit of urban myth to the idea that data must always be stored — or cached — in a database. Sometimes when you really think about the business processes that the data must support and then the degree to which the data must persist to support that process, you may realize that you don't need a database after all. As data is moved closer to its source and only kept in one place, not only is the quality is better, according to Friedman, "the data is where you need it, when you need it and only lasts for as long as you need it."

Well - except when you need to track where it went, etc.

However, for that, I do agree that
" The result is that structured data and SQL will take a back seat to XML and XQuery. "

It's an interesting idea and one that especially holds true after Steve Black's session on how to sell VFP.

Forget about talking about databases - and talk about information flow. I have always maintained that a database is simply the repository of information and those who like to make the arguments for and against specific formats are primarily guardians trying to protect their own little "kingdoms". Best part about FoxPro is that it works with all of those formats.

But it's also a valuable time to think about the LINQ project - because if I can grab all of my data from its various sources with a single object declaration (better examples here)- then I should be VERY happy about that.


Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…