Health Care

If you've used a web ontology before, or any other large-scale data repository, you're likely familiar with one of the chief concerns facing anyone in such a position: how do you get your data into the system? Moreover, how do you get large amounts of data into the system with (relative) ease? And if you've used a content management system before, you've likely faced a similar, albeit inverted problem: how do you get your data out?

If you can accomplish these preliminary items without a good deal of effort, you're finally left with the task of transforming the data from one, and allowing it to be recognizable by the other.

If, instead, you haven't used either of these, you're likely wondering why on Earth you would want to.

Hey, that's not what I was thinking!

That's a very common complaint customers have with developers, when they receive the result of weeks or months of hard work. And it indicates a failure of planning.

Why do websites get hacked? Websites get hacked for a bunch of different reasons:

That's the essence of a question I got today. And it's not one that can be answered easily, because there's no such thing as a site being "secure." It's not an either/or question, it's really a "how much" type of question. How hot is it today?

Not 2 weeks after my newsletter calling out how people take for granted that nothing bad will happen to their web sites, two of the biggest providers went down yesterday, Amazon and Akamai, in several separate incide

All the planning and preparation in the world won't prevent an incident, but it can greatly reduce the consequences.
Nothing better prepares you for responding to disaster than experience. In the world of web applications, sometimes we act as firefighters, coming in to rescue the smoldering remains of a hacked site, a crashed server, or an unexpected traffic burst.

No matter how diligent you are at preventing vulnerabilities and securing your environment, it's impossible to be completely secure on the Internet. What you can do is plan for how to limit the damage that people can do when they manage to compromise some part of your system. This line of thinking is called "Defense in depth" -- you can't just apply security updates and call it good.

At Freelock, we don't think one backup is enough. All kinds of things can, and often do go wrong. Murphy was an optimist, after all.

How would losing your web site affect your business?
That might seem like a silly question, but a surprising number of small organizations don't think it can happen to them. Think again -- web sites get lost all the time, through a variety of means. The server hosting your site might have a hardware failure. Your site might get hacked. Your web developer might accidentally delete something critical. Your host might go out of business, leaving you stranded. If you're in the tech world, you hear about these incidents all the time.

I have a lot of respect for graphic designers and people who can come up with clear, concise information in a graphical way.

There are basically 3 models for getting web applications built:

• Proprietary platform
• Custom code
• Open Source