New Whitepaper: Introducing Azure Search
Wednesday, April 15, 2015
For most of us, talking about search makes us think of Google (and maybe Bing). But for people who build applications, talking about search should bring something else to mind: the possibility of building a search box directly into a custom application's user interface. It's possible to do this with Google or Bing, but this approach has some limitations. Rather than relying on existing search services, creating a search UI for which you can control the results can have a lot of appeal.
One way to do this is to use Elasticsearch
. A simpler option, though, is to use a managed search service such as Microsoft's recently announced Azure Search. Azure Search isn't designed for end users. Instead, it's accessed by applications via a RESTful interface. The goal is to make it straightforward for developers to add search to the UI of the applications they build.
I've written a Microsoft-sponsored introduction to Azure Search, available here
, that explains why adding search to custom apps makes sense. The paper also walks through the basics of the technology, giving you a big-picture sense of what Azure Search does and how it works.
I don't know about you, but I love search UIs. If every application I use offered at least the option of search, I'd be a happy man. The availability of Azure Search is a step on the road to making this happen.
New White Paper: Understanding NoSQL on Microsoft Azure
Sunday, December 28, 2014
Strictly speaking, this isn't a new whitepaper--it's an update of an earlier paper I wrote on this topic. But Azure's native support for NoSQL has gotten so much broader that the paper
is almost entirely new.
The technologies it covers are:
- DocumentDB, Azure's document store
- Tables, Azure's key/value store
- HBase, Azure's column family store, and
- HDInsight, Azure's implementation of the Hadoop technology family.
As usual, my goal is to provide a big-picture introduction to these technologies. The paper won't provide details on how to use any of them, but I hope it will provide a place to start in deciding whether you need NoSQL and in choosing among the options.
If this sounds interesting to you, the paper is available here
The New Big Picture for Data
Friday, October 31, 2014
It's a heady time for data. We've seen more change in the last few years than in the previous couple of decades. Because of this, we need to think about data in some new ways.
For example, the traditional big-picture view of data technologies looks like this:
In this world view, the operational data that applications use is stored in a
relational database. Over time, that relational data gets loaded into a
relational data warehouse, where it becomes analytical data. Business
intelligence (BI) applications then use that analytical data to help
organizations make better decisions .
But things are changing. Here’s a more accurate big-picture view of
the data world today:
Increasingly, applications are using relational and NoSQL
databases for operational data. Turning this operational data into analytical
data implies having both a relational data warehouse and an unstructured data
lake. BI applications are then able to access both kinds of
data to help their users.
And there’s another new piece: search data. As search
services become more available (Amazon Web Services and Microsoft Azure both
provide them today), building search into every application gets easier. Users love search, and with a managed search service in the cloud,
the barrier to entry is significantly lower. But search data is different from
either operational data or analytical data—it’s a new category. Accordingly,
it’s staking out a new position in the data world.
Data technologies have shaken off decades of relational
torpor; lots of new things are happening. It’s time to look at this world in a
Introducing DocumentDB: A NoSQL Database for Azure
Friday, September 12, 2014
Document databases are probably the most popular NoSQL stores today. MongoDB
has lots of users, for example, as do RavenDB
and others. If you'd like to run these on Azure, you certainly can: MongoDB and RavenDB are both available in the Azure store today.
Alongside these, Microsoft now offers DocumentDB, its own document database for Azure. Like most of what Microsoft adds to Azure today, DocumentDB is a managed service, so creating and using databases is relatively straightforward. And like MongoDB, DocumentDB stores JSON documents grouped into collections, although these two document stores also differ in some interesting ways.
I've written a Microsoft-sponsored introduction to DocumentDB, available here
, that gives an overview of the technology. The target audience isn't NoSQL database experts, though. My goal was to explain this technology in a way that would make sense to a .NET developer who works in the relational world, a category that I'd argue is much larger today than the set of NoSQL experts. If that's you, and if you're interested in modern data technologies, you might find the paper worthwhile.
Visiting Central and Eastern Europe
Wednesday, September 10, 2014
I'm returning to Europe later this month for a two-week speaking tour, sponsored by Microsoft. I'm doing a variety of talks in different cities, all related to Azure and cloud computing. Here are the cities and dates:
- September 23: Bratislava
- September 25: Vilnius
- September 30: Kiev
- October 2: Budapest
- October 3: Prague
After visiting many times, I've become really fond of this part of the world. I'm looking forward to the tour.
Conveying Information: The Beauty of Slidedocs
Sunday, August 31, 2014
I spend a lot of my time working out how best to convey information. Sometimes, this means creating and giving presentations, but I also do quite a bit of writing.
Yet deciding how to structure a written document has gotten harder. Books are too slow for most of what I do--updatable papers on the web are better. Still, no matter how good a paper might be, it has no value if people don't read it.
And people just don't seem to be reading many papers any more. Ask yourself: When was the last time you sat down and actually read a 20-page whitepaper from start to finish? At best, I'm guessing you skimmed it, looking at the diagrams and reading just the parts that were most interesting. The tl;dr culture has taken over.
I'm not complaining here, really; I do the same thing myself. But this change means that that people like me have to find another way to convey information, something that lets us get our points across and actually gets read. It's a challenge.
All of which is why I was so happy to discover Nancy Duarte's slidedocs
. The core idea--using PowerPoint slides to create a document that's meant to be read rather than presented--isn't entirely new. But what she does with this idea is absolutely beautiful, creating structure that guides writers into an effective, modern approach. The format all but forces you to focus on the diagrams and the main points, which is exactly what most readers want anyway.
I've used her slidedocs templates for a couple of projects, and while they're not right for everything, they're really useful for many things. If you haven't seen these yet, I encourage you to take a look.