Web Applications





Web applications are systems that run in browsers that perform functions normally associated with other client-based programs. One of the most commonly used web applications is email; instead of downloading individual emails to a local machine, the data is shown through a website. Other examples of web applications are collaborative systems like a wiki or an online game.

Share tech news, updates, or what's on your mind.

Sign up to Post

dtSearch Desktop with Spider is a powerful search tool for Windows. It includes indexing and searching — both are extremely robust and fast! It is available in other editions, including Desktop with Spider and Network with Spider. This article is about the version that I use — Desktop with Spider.

Without even knowing it, most of us are using web applications on a daily basis.  In fact, Gmail and Yahoo email, Twitter, Facebook, and eBay are used by most of us daily—and they are web applications. We generally confuse these web applications tools for websites.  So, what is a web application and how is it different from a website? What are some different types of web applications?  We will help you decipher which is best for the business functions you want to achieve- a website or a web application.

Website vs. Web Application

The best way to elucidate the difference between websites and web applications is to think in terms of purpose.  Do you want to provide information or do you want to get it?

Websites are simple, static, single page sites or marketing websites for distributing information. Websites generally feature and promote products, services, and organizations through articles, images, video, and files. A site informs the world about who you are and what you offer. For instance, you can check your local Italian restaurant website as a customer to check out the ‘Day’s Special,’ or hours of operation without giving away any information about yourself.

Web applications on the other hand are less focused on marketing and more on functionality to fulfill specific business purpose (submitting, storing, searching, and retrieving data). Web applications are software that runs on the web to provide some kind of service or to improve efficiency. Web applications generally always use databases, and are therefore called dynamic. It requires user interaction, as in the user has to provide information in order for the application to work. The big advantage of a web application is that it does not need the developer to build a client for a specific type of computer or a specific operating system because it runs in a web browser. Users can even be using Internet Explorer, Chrome or Firefox, though some web applications may require a specific Web browser.

An Example:

Think of the website of your bank, which promotes the brand and provides customers vital information about their services, and security features. Any member of the public can view the bank’s website but for account holders, the bank also offers web application tools focused on providing specific functionalities. For instance, to help check the balance on their account, submit an online loan application form, or pay bills online.

Technical Foundation

Websites and web applications both are collections of programming code for delivery of content and functionality on the web. The software run on web servers and is accessed through web browsers on a variety of devices.  Both use the same coding languages and tools (HTML, JavaScript, CSS and others) to develop the software. Web applications commonly use a combination of server-side script (ASP, PHP, or Python etc) to deal with databases, storing and retrieving information and client-side script (HTML, Javascript, CSS and others etc.) to present that information, along with frameworks like Rails, Django, etc. to develop and maintain the application.

Types Of Web Applications

There are three different types of web-based applications depending on the roles performed and logic placed and distributed by the server and the client browser.

Server-side HTML Web Application- In this type of web development architecture, the server generates HTML content and sends it to the client as a full-fledged HTML-page.

JS Generation Widgets (AJAX)- The page displayed in the browser shows widgets, where data is uploaded through AJAX query from the server into the content of the page. Any updates from the server show up only for the part of the page requested by the client.

Service-oriented Single-page Web Apps– An HTML-page is downloaded from the server, which acts as a container for JavaScript code to address a particular web service and retrieve business data only. The data is used by the self-sufficient JavaScript application, which generates the HTML content of the page.

It’s also possible to implement hybrid architecture to meet specific business requirements. The architecture of this collection of logically related interactive functions can consist of a number of components, including-

  • Business application functionality
  • Security
  • Browsers such as Internet Explorer
  • E-Mail functionality
  • Forums or bulletin boards
  • Custom-built Advertising

Web Applications Are The Future

Web apps can be customized and tailored for business purposes, like accounting software, reminder systems, order forms, and sales tracking for time saving efficiencies. Web applications can also be designed to strengthen both internal and external communication and improve data delivery and distribution. Advanced web applications are now available as online portals and eCommerce, which delivers content and the functionality of searching, adding to cart, and online financial transaction.

Most business owners understand the value of websites in their marketing plan but not many know the benefits of web applications and how they can offer stronger products and services, improve SEO, reduce cost significantly and help expand their business. Ultimately, whether you choose a website or a web application depends on your assessment of what you want to achieve.


Expert Comment

by:Shreedhar Bhumralkar
A very good article

Expert Comment

In my day we called them dynamic websites that reacted to you what you wanted
A shopping site is hardly an application - it doesn't change according to my interaction, yeah it may offer products based on my history but its the same site for everyone
MS Excel online is an application, one change is seen by everyone
At what point does a shopping site that basically shows the same information to everyone become an application?

Is a mobile app an application because it's called an app even tho its still showing a website?
While opting for any web-to-print solution, you need to discuss with your team and some of your end users and know their opinions about your decisions. In this article we list down some questions you need to ask yourself.

Originally, this post was published on Monitis Blog, you can check it here.

Websites are getting bigger and more complicated by the day. Video, images and custom fonts are all great for showcasing your product or service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, could lead to some difficult decisions about what to cut.


Web loads speeds are integral factors in determining your SEO and how long customers will stay at your site. But web design, as important as it is for driving traffic, can also get in the way of your ultimate goal of bringing customers and revenue. In other words, you must avoid page bloat at all costs!


This is why businesses today, more than ever, must develop a clearly defined web performance optimization strategy. In fact, web monitoring should be an integral part of your web design best practices. To be clear, web performance optimization (or WPO) is the science of making your website perform better so it increases visitor retention, improves SEO, and drives more sales.

To give a great case study of how WPO works, consider what 37signals (now Basecamp) did with their Highrise marketing website. Using A/B testing, the company did multiple tests to determine the best plan for their landing page. In one case, the original background was white and cluttered with information. A dramatic change was made by replacing this white background with a picture of a person smiling.


The new landing page led to an increase in signups at the Highrise site by 102.5%!


This list provides another 99 great case studies of how WPO made a huge difference in website conversions.


In what follows, we take things further by providing you a brief checklist of the key steps to ensuring your website performance optimization strategy is on track.

Keep Things Fast! 

Website conversions are integrally tied to the speed of the site. One second saved in download time can make all the difference between a sale or a bounce.


Check Your Web Hosting 

Your web hosting may offer “unlimited bandwidth” but if it involves shared services with other websites that impacts overall performance, then is it really worth it? It’s always a good idea to periodically review your hosting plan to ensure you’re getting the best value for your dollar.


Make Your Site Mobile First

Having a “mobile first” website is critical to success in today’s digital marketplace. If you don’t believe it, just consider that mobile commerce transactions in the United States alone are expected to total $123 billion in 2016


Image Optimization 

“Page bloat” – or the practice of cramming websites with high density images – has gotten out of hand and is the number one culprit for long page loading times. Don’t bloat your website! One of the best ways to ensure proper image optimization is to adopt correct sizing and formatting for all your images.


Go Easy with Affiliate Codes & Ads  

Ads and affiliate code are good . . . up to a point! But when you go overboard, this can lead to high bounce rates and can adversely impact your overall website performance. Constantly check how third-party applications impact your load speed! 


Cache Often 

Caching is a mechanism for the temporary storage of web pages in order to reduce bandwidth and improve performance. This saves server time and makes your website faster overall.


Use a CDN 

Content Delivery Networks deliver the static files of a website, like CSS, images, and JavaScript, through servers that are in closer proximity to the user’s physical location. Every second that you save in download time is dollars in your pocket.


Make Your CTA Front & Center 

Don’t make your landing page a game of “guess where to check-out the merchandise.” Visitors don’t want to spend extra time trying to figure out where to complete their transactions. Your Call to Action should be front and center on the landing page.

Adopt Cloud-based Website Monitoring 

Imagine having all of the vital statistics for your website in a nice convenient dashboard, and getting alerts about trouble spots long before they reach impact your customers. Cloud hosted web monitoring is the crucial component in today’s digital marketplace. IT system monitoring is first of all a real time data that can help you respond to problems. You cannot do without monitoring tools, if you hope to optimize and maximize your application’s performance.

Sign up for Monitis FREE 15-day full-featured trial! Premium plan starting from $12/month only! 


This article was originally published on Monitis Blog, you can check ithere.

If you have responsibility for software in production, I bet you’d like to know more about it. I don’t mean that you’d like an extra peek into the bowels of the source code or to understand its philosophical place in the universe.  Rather, I bet you’d like to know more about how it behaves in the wild.


After all, from this opaque vantage point comes the overwhelming majority of maddening defects.  “But it doesn’t do that in our environment,” you cry.  “How can we even begin to track down a user report of, ‘sometimes that button doesn’t work right?'”


To combat this situation we have, since programmer time immemorial, turned to the log file.  In that file, we find answers.  Except, we find them the way an archaeologist finds answers about ancient civilizations.  We assemble cryptic, incomplete fragments and try to use them to deduce what happened long after the fact.  Better than nothing, but not great.


Because of the incompleteness and the lag, we seek other solutions.  With the rise in sophistication of tooling and the growth of the DevOps movement, we close the timing gap via monitoring.  Rather than wait for a user to report an error and asking for a log file, we get out in front of the matter.  When something flies off the rails, our monitoring tools quickly alert us, and we begin triage immediately.

Common Monitoring Use Cases

Later in this post, I will get imaginative.  In writing this, I intend to expose you to some less common monitoring ideas that you might at least contemplate, if not outright implement.  But for now, let’s consider some relative blue chip monitoring scenarios.  These will transcend even the basic nature of the application and apply equally well to web, mobile, or desktop apps.


Monitis offers a huge variety of monitoring services, as the name implies.  You can get your bearings about the full offering here.  This means that if you want to do it, you can probably find an offering of to do it unless you’re really out there.  Then you might want to supplement these offering with some customized functionality for your own situation.


But let’s say you’d just signed up for the service and wanted to test drive it.  I can think of nothing simpler than “is this thing on?”  Wherever it runs, you’d love some information about whether it runs when it should.  On top of that, you’d probably also like to know whether it dies unexpectedly and ignobly.  When your app crashes embarrassingly, you want to know about it.


Once you’ve buttoned up the real basics, you might start to monitor for somewhat more nuanced situations.  Does your code gobble up too many hardware resources, causing poor experience or added expense?  Does it interact with services or databases that fail or go offline?  In short, does your application wobble into sub-optimal states?


But what if we look beyond those basics?  Let’s explore some things you may never have contemplated monitoring about your software.

User Engagement

Facebook has developed some reputation around having deployment nirvana.  They constantly roll to production and use a sophisticated series of checks, balances, tests, and monitoring to alert them to problems needing correction.  If the number of baby pictures in my feed is any indication, I’d say they’re doing pretty well.


But what happens if Facebook pushes something to production with a mistake not easily caught by automated unit tests?  For instance, what if they accidentally deployed some CSS that turned the “post” button and its text the same color as the background.  The flow of baby pictures would cease, even as all tests passed with flying colors.


Monitis offers “real user monitoring,”  which generalizes a specific case can address this situation.  You may want to monitor user behavior in terms of how they engage with the site.  If Facebook monitors how many times per second its users click “post,” and they see that drop to 0 after a production roll, they’ll know they have an issue almost immediately.  Even if they don’t know what causes it, they can triage and mitigate almost immediately.


If you have responsibility for any sort of e-commerce operation, I strongly encourage you to monitor your revenue.  In a sense, you might consider this a specific instance of user engagement.  You’ll have some sort of normal drip of people making purchases.  Anything affecting that presents you with an obvious red flag.


You might be tempted to think of this as an accounting problem more than a technical one.  Let techies monitor the nuts and bolts and accounting can worry about P&L?  I don’t advise it. Purchases count as arguably the most important metric.  They form the lifeblood of your business.


You mainly think of a “bounce” when you think of web applications.  Google defines bounce as “a single-page session on your site.”  I believe this plays on the opposite of “sticking.”  People land, and “bounce off” of your site.


I’m going to re-appropriate the term a bit for our purposes here and generalize it to all application platforms.  You might want to monitor the rate at which users exit your application from a particular page/screen.


When they leave from, say, an “exit” screen, then fine.  You’d want a high percentage of departures from expected places.  But if people being to leave from a place you’d expect them to remain engaged, that might give you insight into a problem of some kind.  This holds doubly true if it suddenly spikes in one particular place.

User Experience Concerns 

This particular concern would require some fairly sophisticated monitoring capabilities, most likely instrumented from within.  If you do implement such a thing, take care not to impact performance.  But, if you’re up for it, you might learn some interesting things.


Consider monitoring user behavior for user experience concerns.  For instance, do users consistently dismiss a dialog far too quickly to have read it?  Or perhaps do they all tend to execute the same key sequences to navigate through several screens?  If so, you might have located opportunities to improve your user experience.  Get rid of superfluous dialog messages and see about adding shortcuts for things they do frequently.


And you certainly aren’t limited by my suggestions here.  If you have the capability to monitor interactions like this, study your own users with their particular happens and look to improve their experience.

Time to Load Visual Elements

This is another item that you hear about most frequently in websites.  But, as with my looser interpretation of the “bounce” concept, you could really measure this anywhere.  After all, sluggishness is sluggishness.


If you find yourself in a position to monitor the visual performance of your software, you stand to benefit from doing so.  Few things torpedo the user experience as quickly as maddeningly slow loads.  If this is happening, you want to know about it.


This holds doubly true for visual elements superfluous or non-essential to the experience itself. In the world of websites, think of ads or random widgets.  And, while you can test a lot of this for yourself, concerns may arise in the wild that you can’t mimic in your own shop.

Think of Your Own in the Spirit of Innovation 

I’ve enjoyed the exercise in exploring what you might want to monitor.  As both an entrepreneur and software developer, I like thinking about possible implementations, offerings, and features.


In fact, that captures what I find so appealing about the DevOps movement.  As we marry software creation and software delivery, we open up an entirely new category of innovation, that requires new and powerful tools.  We can then combine those tools with the inventive spirit to deliver ever-higher quality software.

Sign up for Monitis FREE 15-day full-featured trial! Premium plan starting from $12/month only!


Read the original post on Monitis Blog.

Believe it or not, the most important thing about the website of your business is not what’s on it but how fast it loads. Yes, that’s right! 


As you can see on this infographic (an oldie but goodie!), there is a clear relationship between web load speed and customer conversions. And unless you have money to burn, the assumption is that you’re in business to earn revenue (rather than just having a fancy looking website!).


Let’s say this another way. The faster a page loads the more likely customers will be to visit and do business on your site. The inverse is also true. The slower a page the less likely customers will be willing to wait around and engage with your brand.


While this seems fairly straightforward, it’s surprising how few business owners really get the importance of website performance and the role it plays in their overall strategy. It might be nice to have a trendy looking website, but if it takes 10 seconds to load visitors won’t hang around long enough to appreciate all the bells and whistles anyway.


It’s important that small businesses leverage the latest web performance insights to ensure that things are running as optimally as possible and that your customers are happy. At the end of the day, this is really all that matters!


In order to help keep your business in check, we list out below the top 10 things you should know about website performance today.

Website Speed Impacts Conversions & Sales 

There’s a direct connection between web load speed and sales conversions. Consider this metric: 1 in 4 visitors would abandon the website if it takes more than 4 seconds to load. And this one: A 2-second delay during a transaction results in shopping cart abandonment rates of up to 87%.


A few years ago e-commerce giant Amazon calculated that a webpage load slowdown of just one second could cost it $1.6 billion in sales each year. Any questions?

“Start Render Time” is a Key Metric 

Start Render Time has emerged as a key metric in web performance and is the first visual cue that something is happening on a website. The following statement gives some words of wisdom on this topic:

The median for Time to Start Render across the web is 2.5 seconds. Shoot for better.  The top 10% of sites on the web start render in less than 900 milliseconds — fast enough that the visitor doesn’t have time to think about the fact that he or she is waiting to see content.  That should be the goal.

Design Best Practices Can Become Your Worst Enemy

Increasing the size of your website’s size, images, third-party scripts, and style sheets come with a heavy price and can adversely affect performance. This is especially true in the world of mobile. Over 50% of all time consumers spend on retails site is on mobile devices, and more than 50% of consumers multiscreen during the purchasing.


Some of the worst design practices are evident when web pages are initially blank and then populate, the CTA is the last thing to render, popups block the rest of the page, or when you fail to adopt user experience into your design strategy.


Performance Impacts Shopping Behavior 

We get the importance of website speed on customer conversions and sales. But this impact is more systemic than you might think. Kissmetrics shows that 44% of online shoppers will tell their friends about a bad experience online. And 79% of shoppers dissatisfied with a website performance are less likely to buy from that site again.


Mobile Unfriendly Sites Drive Customers the Other Way 

M-commerce is huge, which is why having a “mobile first” website is critical to success. Mobile commerce transactions in the United States are expected to total $123 billion in 2016. $76 billion will be from tablets, while the remainder will be from smartphones. These same numbers are replicating themselves globally.


A study from Google several years ago showed that mobile-friendliness was a key factor in purchase decisions, with 67% indicating that a mobile-friendly website made them more likely to buy a product or use a service. In addition, 61% indicated that a bad mobile experience made them more likely to leave.


You Can Win with Website Analytics 

Web analytics can make all the difference in how you relate to your customers. The ability to track a single customer across your site and across multiple devices will ensure that you can tailor your brand to their needs.


For instance, you want to learn more about when and where they’re visiting from, what devices they’re using, what are their online activities, and other key demographics such as age. Gaining these insights will help your organization better understand what’s important to your visitors and how to personalize their experience.


Speed Increases SEO 

In April 2010 Google started using page speed as a ranking factor, meaning that faster pages would earn higher SEO rankings than slow ones. More recently, Google also announced that it’s moving in this same direction for mobile web pages. The point here is that you get rewarded for offering your customers a better overall experience; faster load time means higher SEO rankings.


Mediocre Web Hosting Can Increase Downtime 

When reviewing web performance, it’s important not to forget your web hosting service. Even though your provider may offer you unlimited bandwidth, does that mean shared service with other sites that ends up affecting your own web performance?


Are you experiencing downtime or bandwidth issues? If so, it’s worthwhile to review your hosting options to ensure you’re getting the most efficient service. Don’t be afraid to insist on 99.99% uptime.


Too Many Affiliate Codes & Ads Drain Performance 

Becoming an affiliate reseller and pushing ads to bring folks in is great, but too much of a good thing can also become bad . . . especially for performance. When you go overboard on ads and affiliate code, this can lead to high bounce rates and, in turn, can adversely impact your overall website performance.


Website Monitoring Is Key! 

There are significant advantages to adopting website monitoring – cost, scalability, efficiency, to name a few. Not to mention, this frees you up to focus on growing your business, which matters the most anyway.


When it comes to monitoring your website, you don’t want to shortchange yourself. Get the peace of mind you deserve by entrusting your business to a proven industry leader.

Sign up for Monitis FREE 15-day full-featured trial! Premium plan starting from $12/month only!


Original post on Monitis Blog.

Web performance monitoring is broken into two camps: passive and active. Passive monitoring is defined as looking at real-world historical performance by monitoring actual log-ins, site hits, clicks, requests for data, and other server transactions.


This is the kind of monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.


Active monitoring is a more experimental approach. It uses algorithms to take current log data and predict future network states. A good example of active monitoring is synthetic transaction monitoring. This involves deploying behavioral scripts in a web browser to simulate the path a real customer (or end-user) takes through a website.


Synthetic transaction monitoring is especially important for eCommerce and other high traffic sites as it allows webmasters to test new applications prior to launch. Synthetic transactions are scripted in advance and then uploaded to the cloud as a transaction tests.


There are different scenarios where your business would need transaction monitoring in order to stay competitive today.

Entering a New Market 

Before introducing a new application to market you want to have line-of-sight on how real users will interact with that app. Synthetic transaction monitoring provides behavioral scripts that have the ability to simulate an action or set of actions to ensure your application can handle the projected load.

Another benefit of synthetic monitoring is that it helps you simulate what happens when you introduce your application to a new geography. It allows you to test and fix potential issues related to deployments in new regions such as connection speeds (DSL, cable broadband, fiber optics) before real end users arrive. 


Finding Issues Before Customers 

Synthetic monitoring helps you to set up baseline tests in order to measure the way your customers will interact with your websites, APIs, or mobile apps. This type of testing can provide direct feedback on performance degradation or availability issues. It also will help your team locate the root cause, engage the right experts, and fix issues before they impact the end users. 


Measuring Performance Impact of Third Party Applications 

Today’s websites increasingly rely on third-party features such as carts, ads, customer reviews, web analytics, social networking, SEO add-ons, video and much more to provide outstanding customer experiences. If there’s a weak-link in the chain, or one or more of these elements are not working correctly, it can adversely impact your site.


Synthetic transaction monitoring can greatly assist in helping to monitor your third-party applications while also alerting you to potential or real performance degradations and downtime impacts. This helps tremendously in providing line of sight on your service level agreements (SLAs) in order to hold the third-party vendors accountable. 


Testing New Features 

Synthetic monitoring is important at any stage of development, but is especially useful for testing your web, mobile, or cloud-based applications before deploying new features into production. During this stage synthetic monitoring can provide a set of baselines and thresholds that reveal any potential obstacles customers may encounter in the real world. 


Comparing Your Performance to Your Competition 

With synthetic transaction monitoring you can set up benchmark scenarios to see how your applications are performing over time. You can also benchmark your company’s performance against top competitors within a certain historical time frame or within a specific geographical region. This approach can be especially important for establishing your organization’s strategic outlook for the year as well as for preserving competitive advantage in the marketplace. 


Analyzing Your eCommerce Strategy 

If you’re in the eCommerce business, then synthetic transaction monitoring is especially useful for ensuring that your eCommerce strategy is firing on all cylinders. By setting up tests with synthetic monitoring you can get apprised, for instance, about when one of the steps in your website’s online transaction process is no longer working properly. By tracking and analyzing every click and swipe, synthetic transaction monitoring solution can help you to identify problems and prioritize fixes in your website to ensure that customers continue to have the kind of experience they’ve come to expect.


Evaluating New technologies 

Another important use of synthetic transaction monitoring is to assist in the choosing, testing, and optimization of new technologies within your production environment. For example, being able to test if a new CDN (content delivery network) is performing as optimally as possible compared to other known benchmarks will help your organization to decide which product or service will provide the most value to your infrastructure.

Sign up for Monitis FREE 15-day full-featured trial! Premium plan starting from $12/month only! 


Read the original post on Monitis Blog.

Hi.  My name is Erik Dietrich, and this is the first time I’ve posted on the Monitis blog.  By way of introduction, I thought it would make sense to talk about my initial experience with Monitis.


Before I do that, though, I need to explain a bit about myself.   Don’t worry.  It’s relevant, I promise.


I’m a techie by trade.  Specifically, I have historically made a living as a software developer, architect, dev manager, CIO, and, these days, IT management and strategy consultant.  On top of that, I write and present frequently, including routine publishing to my own, tech-centric blog.


Because of this, I know a certain tension to which you can, no doubt, relate. I’m talking about the tension between not having time to build and look after your own website and thinking, “what kind of developer am I if I don’t build and look after my own site?”  I feel awkward about it, but over the years, I’ve come to the conclusion that it’s better to leave my site’s development to WordPress and the folks that make themes for it.  I just don’t have time to take care of it myself.


But this delegation can lead to embarrassing lapses.  I write about software professionalism, IT strategy and the delivery of high quality solutions.  So when someone that follows me on Twitter sends a tweet informing me that my website has gone down, I can’t help but feel silly.  Anyone looking at the situation obviously knows that it’s my hosting company or, perhaps, something with WordPress.  But that doesn’t stop me from feeling the ironic sting of being the last to know about my own outage.

Mitigating Outages for Professionals

When I ran an IT department as the CIO, I had responsibility for some public facing web applications.  I understood acutely the embarrassment of an outage, and I understood how it could be mitigated.  If you become aware of it first and inform your users, you lose far less credibility in their eyes than if they find out and inform you instead.  The outage is still unfortunate for everyone, but you being on top of it makes it seem almost planned to the users that hear of it.


To make sure my group had this advantage, I oversaw the instrumentation of monitoring tools within our network.  This was some years ago now, so I don’t recall the particulars, but I do remember having a dashboard to peruse and getting emails and text notifications to alert me immediately of any problems.  This was powerful stuff.


Mitigating Outages for the Rest of Us


When it comes to my own blog and site, however, this sort of instrumentation never occurred to me.  I had sound reasoning.  An outage on my site is not critical to anyone.  Nobody logs in and interacts with the site in a high-touch way – it’s just content that I publish for people to read.  I don’t lose money when my site was down.


Because of all of these considerations, it made no sense to me to invest in monitoring.  I had a preconceived notion of the cost of such things, since I had, in the past, allocated budget for them.  Had I really gotten serious about it, I would have reasoned that I could probably do better in price a few years later and with different needs, but it never really bubbled up near the top of my own personal priority list.


This changed, however, when I encountered the Monitis product offering.  I’ll fast forward a bit and say that today, I have effective monitoring for my site that gives me exactly the data I want and costs me almost nothing.


Getting Started

I would offer a “how to” at this point, but you’ll have such an easy time it’s honestly not worth the bother.  Go to the main site, click “start monitoring now” and fill out the requested information.  That’s it.  Really.


I did this, and true to what they say, I had monitoring of my site set up within 3 minutes.  At the time I performed the setup, I recall being in something of a hurry, so I just kind of did a fire and forget.  I setup monitoring HTTP for my site, and didn’t think anything more of it for the rest of the day.


The next day, I got the email shown below.  I saw that they had hit my site with HTTP requests from 3 different locations.  Cumulative uptime of 100%, too.  I won’t lie — I was a bit relieved to see that “all good” seemed to be the default state of affairs.

For a few more days, I continued to receive this daily summary.  I had an even larger sample size of things being alright, and, about a week in, I found myself with a bit more time to dig into the monitoring itself.  I logged into my newly-created Monitis account and poked around in my dashboard.


The default monitoring that I had setup involved 3 locations making HTTP requests all day to my site.  If any 2 locations failed simultaneously, I would receive an email alert that my site was down.  At the time, I had signed up for a trial account, so my next bit of curiosity was “what will this cost me.”  When I went to the pricing page and punched up what this would cost on an ongoing basis, I found the result quite reasonable: $1.20 per month.




My Takeaway: The Value Proposition


I could kick myself for not doing research earlier. I keep my finger on the pulse of many different trends and technologies.  And, if you would have asked me whether or not some kind of affordable site monitoring technology existed, I imagine I would have said, “gosh, probably.”

And yet, I never went out and did the research.


The obvious lesson here is that affordable and effective monitoring for your site exists.  Even if your site is simply you posting a food recipe or two per month, and a couple of your relatives reading it every now and then, it’s probably worth about a dollar per month to make sure it runs smoothly.  Call it peace of mind or call it professional pride.  Either way, if you have a site, you might as well keep an automated eye on it.


But the deeper lesson here is one of cost and specialization.  Cloud technology and its ramifications extend beyond, “it’s easy to provision a server.”  All facets of traditional IT are becoming commoditized and offered affordably and with good quality to people with budgets of all sizes.  If it’s been achievable for the enterprise for years, keep your eyes open, because, quite probably, a version is achievable for you as well.

Sign up for Monitis FREE 15-day full-featured trial! Premium plan starting from $12/month only! 

The world seems to conceive of a curious bubble separating IT from “the business.” More so than just about any other pursuit in the commercial world, people think of IT as some kind of an island.
These days, all we hear about hacktivists took down so and so websites and retrieved thousands of user’s data. One of the techniques to get unauthorized access to database is by performing SQL injection. This article is quite lengthy which gives basic information about SQL injections
It’s a strangely common occurrence that when you send someone their login details for a system, they can’t get in. This article will help you understand why it happens, and what you can do about it.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Real-time is more about the business, not the technology. In day-to-day life, to make real-time decisions like buying or investing, business needs the latest information(e.g. Gold Rate/Stock Rate). Unlike traditional days, you need not wait for a few months or a few weeks to get market trend inform.
Meet the world's only “Transparent Cloud™” from Superb Internet Corporation. Now, you can experience firsthand a cloud platform that consistently outperforms Amazon Web Services (AWS), IBM’s Softlayer, and Microsoft’s Azure when it comes to CPU and disk performance.

Author Comment

by:Superb Internet Corporation
Understood. Thanks for the help. Do you need me to rewrite it? Let me know.
International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
A publishing tool, a Version Control System, or a Collaboration Platform! These can be some of the defining words for the two very famous web-hosting Git repositories: Bitbucket and Github. Git is widely used amongst the programmers and developers for re-developing a maintained code. With this technology, a local and web copy of projects can be saved. 

How Does Version Control System Works?

A Version Control System simply allows saving multiple snapshots of single project. Say, we have a project and files of code. When we work on it for some time, we might find the need to create a safe point of it (which is S1 in the figure).

Now, if we want to work more on the same project, we can copy the code and modify it and then again create its safe point (which is S2 in the figure). And likewise, it is possible to continue modifying the project (S3) but at the same time maintain history of previous projects as well. Say, at some point of time, our project did not work well (S4). So, we have the option to go back to the previous version (S3) and get started again.

When a Git repository is created, a master branch is developed and as long as we generate safe points, the master branches are added. Now, there can be requirement of adding new features to a project that is working currently (S4). So, when one developer is busy adding features to the project (F1), another can continue to make relevant modifications and work on it (S5) and same …

Author Comment

by:Sofía Tomas
Dear Moderator,

My article "Bitbucket vs. GitHub: Which is Right for You?" is ready for re-review. Please Check it.


Author Comment

by:Sofía Tomas
Dear Editor,

Thanks for your reply.


What is Node.js?

Node.js is a server side scripting language much like PHP or ASP but is used to implement the complete package of HTTP webserver and application framework. The difference is that Node.js’s execution engine is asynchronous and event driven, which throws a whole new light on the way a server side app performs. As Node.js is the complete package (web HTTP server and server side language), there is dramatically less overhead in implementing it as a webserver when compared with a typical Apache (and PHP) or IIS (with ASP/PHP) installation.

Node.js is written in JavaScript, the most common client-side language around. This reduces the learning curve somewhat for most web developers as they understand JavaScript and how to code it.

Why is it Important and what are the Benefits?

Most of the server side languages I’ve used are built on sequential execution models, meaning one task has to finish before another one begins. For instance, PHP (in conjunction with the type of server it is running off e.g. Apache) will spawn a thread for each request made to the server. If that thread needs to get data from a database that takes a while or another request comes in, that thread is locked up and consuming resources. For a data intensive app with many concurrent connections, that could severly impede the server’s performance.

Node.js is single threaded (yes only one thread!) and is beneficial in applications where frequent blocking I/O requests
A frequently used term in Object-Oriented design is "SOLID" which is a mnemonic acronym that covers five principles of OO design.  These principles do not stand alone; there is interplay among them.  And they are not laws, merely principles, like "an apple a day keeps the doctor away." But they serve to guide us in the right direction as we design and build our systems.

There are no real "shortcuts" here.  As Euclid said to Ptolemy, who wanted to know the easy way to learn geometry, "There is no royal road to geometry."  So, too, there is no royal road to good object-oriented design. But that said, read on for some of the summary and background information that will make your software designs more coherent and easier to build, test, extend and reuse.

Do I Really Have to Learn This?
What happens when these principles are ignored?  Some call it software "rot."  I prefer to think of it in terms of fragility and viscosity.  Software that is of fragile design is difficult to extend or modify.  Even simple changes can induce seemingly unrelated entropy elsewhere in the system (Einstein called this, "spooky action at a distance").  Eventually this phenomenon comes to the attention of the business managers, and they become resistant to change.  Developers become frustrated as micromanagement ensues.  Ultimately the system must be scrapped and re-invented.

Software that is viscous
LVL 111

Author Comment

by:Ray Paseur
Thank you, Todd.  As time permits I will have five more articles in the series to illustrate each of the principles at work in PHP.
Thoughout my experience working on eCommerce web applications I have seen applications succumbing to increased user demand and throughput. With increased loads the response times started to spike, which leads to user frustration and lost sales. I have seen several downtimes during the holiday season and promotional events, which is catastrophic for businesses.

The reason for this is mostly performance bottlenecks or scalability issues. Usually web applications get their data from relational databases. If an application is not designed right, databases become bottlenecks. The cost of scaling an enterprise databases like Oracle or DB2 is huge and can take us only so far as most of the relational databases are not always horizontally scalable. The other bottleneck is usually web service calls. On high loads web service calls can literally kill a website not designed for scalability and performance.

I recommend the use of caching for almost any application. Though I have used memcached and EHCache as caching providers and will be using memcached's example for this article, I am not here to propose any one caching solution. For simple websites simple map based solution of WhirlyCache, OSCache or cache4j might work pretty well, though you can still use more advance solutions like EHCache, memcached, JCS, Terracotta, Oracle Coherence
LVL 14

Expert Comment

by:Giovanni G
I think I miss some point here, if you store it as "currentCustomer" and you have 2 clients currently browsing your website what happens when customer B makes a request? He will appear as customer A due to the shared "currentCustomer" cache key.

I agree session-scoped caches are bad but I think your cache-key should be something like "currentCustomer-<id>" then the session cookie should provide <id> and <auth_nonce> and then you can retrieve from memcache currentCustomer-<id> and verify that the auth_nonce matches, or something like that.

I really don't see how the proposed solution could work in a multi user environement.

Author Comment

Hi ThG,

Good catch!!! I will fix it in the article. To keep is simple and focused on caching only, I will not talk about nonce here.

Thanks for your feedback.
Developer tools in browsers have been around for a while, yet they are still heavily underused by developers. Developers still fix html or CSS then refresh page to see effect, or they put alert or debugger in JavaScript and then try again and again trying to fix the issue. In this walk through I will cover few most helpful tools available. I am using Chrome and a sample ASP.NET MVC application
To open the developer tool you have following options:
  1. Keyboard short cuts – Cntrl + Shift + I/J/C or simply press F12
  2. Right click on page – Inspect element

Chrome's developer tool looks like
1.pngThe top menu has several option to enable you focus on specific page information.2.pngElement
This is to inspect/modify page's DOM tree (HTML and CSS). You can modify HTML and styles here and see the change without the need to reload the page. The modifications do not effect your source files; the changes are local to your browser. Refresh/reload will undo changes made on the browser.

To view HTML DOM
Right click on the element and select the one you want to inspect or click on the magnifying glass on top left, and then move the mouse over the element you want to inspect. When you inspect any element you will see this:
3.pngThe left panel shows the DOM and the right panel the CSS Style of selected element. By default the HTML of other elements are collapsed; to open/collapse them click on the black triangles.
4.pngTo Modify Element
If I have to fix slow responding website my first thoughts are server side optimizations: the database may not be optimized or caching is not enabled, or things like that. We often overlook another major part of our web application: the client. We often ignore this area, but it has major impact on performance of a website. So before jumping into optimization we need to know how things are processed by the browser.

Web pages utilize a lot of resources; they can contain images, JavaScript and CSS files, Flash and much more. For each individual resource there is a separate request from the browser to the server -- and requests cost time. Each request has two phases, the time required making connection to the server and making the request, and the actual time it takes to send the resource and download it to the broswer.

Each additional image or file is slowing is your website. Browsers should download these resources in parallel, but there is limit to how many concurrent connections a browser can make to your website at a given time. The typical modern browser can have six to eight connections to a domain. This means that no more than eight parallel request will be made to your website by browser. If your page needs more resources, the browser will have to wait for previous requests to be completed before it makes the requests for other resource; until then, they are queued and compete for connections to the server. Moreover some resources depend on other resources -- for …
Foolproof security solutions has become one of the key necessities of every e-commerce or Internet banking website. If you too own an online shopping site then its vital for you to equip your web portal with customer security features that can allow your visitors to experience optimal security while undertaking a range of monetary transactions. SSL(Secure Socket Layer) is one of the most promising security options for websites that include sensitive data. In this article, you'll find everything about SSL and its significance for a website that's powered by ASP.NET.
What is SSL exactly?
SSL (Secure Socket Layer) is a highly commendable security mechanism that's being used for encoding communications between the client and server. This is specially helpful for websites which involve a lot of financial transactions. By sending the data between browser and web server in an encrypted form, SSL prevents any sort of tampering by unauthorized individuals such as hackers. SSL works as an excellent tool for securing the privacy of sensitive data, keeping it confidential to the fullest. SSL works perfect for hiding sensitive data including bank account details, login information, credit card details etc.
SSL Certificates - What are they?
SSL certificates basically contain the organization/website's digital identity that includes symmetric as well as asymmetric keys. As a website administrator, you …

New Relic:

Our company recently started researching several products to figure out what were the best ways for us to increase our web page speed and to quickly identify performance problems that we may be having. One of the products we evaluated was New Relic.  Here is a list of pros and cons that my team came up with that may help you decide of New Relic is right for you.


1) Application Stack Trace Details

New Relic offers a great interface for debugging the server side of performance issues. While running on your servers it keeps track of the entire run time stack and gives a detailed report on issues. For example, it counts up the number of database queries that are running within your particular thread and gives a report on how many different queries are executed and how long each took. This is a great feature to allow you quickly to identify performance issues: which queries take too long, which query is called too many times, what function is running for way too long.  All these issues become apparent for you to fix.

2) Global Real User Tracking

Since the application runs on your servers and also as part of javascript on your webpage, you get accurate real user page load times. This was way more valuable to our company than simulated traffic because it allowed us to see exactly how our web pages were performing all across the world. Real user page performance tracking …
Using Quotation Marks in PHP
This question seems to come up a lot for developers who are new to PHP.  And it got me thinking, "How can we explain the rules for quotation marks?"  For better or worse, PHP has so many rules!  This article tries to answer the questions.

First, some mandatory reading.  You need to understand the terms "variable" and "string" as they are used in the context of computer programming.  Take a moment to read these pages.  If it doesn't all "click" at first, don't be too concerned.  We will show some examples and explanation below.

Quotation Marks Used With Strings
A string is nothing more than a few characters strung together.  The code snippet below has examples of perfectly valid strings.  The first string is the single capital letter "A" and it has a length of one character.  The second string is the empty string.  It has a length of zero.  You can probably figure out the lengths of the other two strings.

Alphabet Soup

Open in new window

If you want to assign these literal string values to PHP variables, you must put quotes around them in the assignment statement.  Both of these examples are acceptable.  Note that one uses single quotes and the other uses double quotes.

$x = 'Alphabet Soup';
$y = "Alphabet Soup";

Open in new window

A Change in PHP Behavior with Session Write Short Circuit (Winter 2014)**
With the release of PHP 5.6 the session handler changed in a way that many think should be considered a bug.  See the note at the end of this article.

A Foreword: PHP session_unregister() (Fall 2014)
Some obsolete code sets contain "Logout" examples that use the session_unregister() function.  PHP deprecated this function more than 5 years ago and removed it recently.  If you have a script that uses session_unregister(), you should replace the function name with unset(), using the same function call arguments.  Going forward, do not use session_unregister(), session_register(), or session_is_registered().  Instead check the PHP man pages for these functions.  There are solutions and explanations of the alternatives in the user-contributed notes.

And now, on to our Article: PHP Sessions -- Simpler Than You Think
This EE question ("I am looking for a solution for logout after inactivity.") got me thinking...

Developers who are new to PHP session handling sometimes over-think the role and behavior of PHP sessions.  This article takes the process apart and reconstructs it to show how easy it can be to use the PHP session to your (and your clients') advantage.

Use the Built-In Features Whenever Possible
PHP already has a built-in solution
LVL 14

Expert Comment

by:Jim Riddles
The same goes for me.  I have learned so much about the proper way to approach PHP programming.  I still have so much more to learn, but with Ray's articles, I know that I will get there.  Thanks so much, Ray for all of your time and efforts!  They are much appreciated.

Expert Comment

by:Oliver Russell
Nice write up on PHP sessions. Have you used Redis server for php session management? I am using it on my server. Redis is efficient in handling sessions in PHP. If you use memcached as well, you will see a significant increase in performance of database.

Web Applications





Web applications are systems that run in browsers that perform functions normally associated with other client-based programs. One of the most commonly used web applications is email; instead of downloading individual emails to a local machine, the data is shown through a website. Other examples of web applications are collaborative systems like a wiki or an online game.