GoodDemo is a one of our new projects that might be a great way to show off web apps. Rather than a screencast or screenshots, GoodDemo guides users through the actual app itself. This article includes an interesting first look at the prototype. Read more at here...
The movie "Hackers" (1995) was spot-on (in being ridiculous.) But security issues with web applications are very real to the companies who have to face the fall-out from the compromise of their customer's privacy.
This article takes a look at two recent attacks on web applications and how they were perpetrated. Then it dives head first into a litany of different potential security holes and more importantly, how to plug them using ASP.Net.
We're kicking off a new project today. Starting from scratch, we're going to build a small web application and document it in real time. Typically, the development of new products start out in a bubble, but the goal of this project is to keep everything out in the open- from the ideas to the code to the mistakes and issues along the way.
Our intentions are to offer a behind-the-scenes look at our own way of doing things and to allow anyone interested to take part and contribute. It can be an opinion, suggestion, idea or scathing criticism of our approach. Hopefully it'll be an interesting process, perhaps even insightful (for you and us.)
Web applications are dynamic- many requiring unique content and interfaces for each user. There are a myriad of ways to take user content out of a database and present it in a browser. This article focuses on the different ways it can be done in the Microsoft world (specifically in ASP.NET), why we chose XSLT for our own product, and finally a look at our technical implementation.
It's amazing to see how fast the usage of a web application can outpace initial expectations. Growth is good for business but creates some real challenges when it comes to trying to keep everything up and running speedily along.
When an application is being designed, estimates are made for the expected maximum load of web traffic and the number of concurrent requests that the databases will need to handle. Often these estimates turn out to be too conservative (and sometimes even way off base), so software architects need to plan for much greater application load to avoid major redesigns in the future. These plans usually need to include a database scale-out strategy.
Scaling web applications and databases can be quite complex depending on the requirements but the good news is that for the majority of web applications, it can be done with little impact on a project's timeline or budget provided it's taken into account at the beginning of the design cycle and not as an afterthought.