Month: March 2014

Windows Azure Services Bus

Posted on

Windows Azure Service Bus

Service Bus is messaging infrastructure that sits between applications allowing them to exchange messages in a loosely coupled way for improved scale and resiliency. Service Bus is managed and operated by Microsoft with a 99.9% monthly SLA.

Use Service Bus to:

Manage message delivery in the cloud

Service Bus Queues offer simple first in, first out guaranteed message delivery and supports a range of standard protocols (REST, AMQP, WS*) and API’s to put/pull messages on/off a queue. Service Bus Topics deliver messages to multiple subscriptions and easily fan out message delivery at scale to downstream systems.

Connect on-premises applications to the cloud

Service Bus Relay solves the challenges of communicating between on-premises applications and the outside world by allowing on-premises web services to project public endpoints. Systems can then access these web services, which continue to run on-premises from anywhere on the planet.

Push notifications at scale to mobile devices

Notification Hubs provide a simple, scalable way to send out push notifications to apps on popular mobile platforms without needing to understand or directly interface with the many notification mechanisms for each platform.


Windows Azure Queue service is used for reliable, persistent messaging between applications. You can use Queues to transfer messages between applications or services in Windows Azure. Queues store messages that may be read by any client who has access to the storage account. A queue can contain an unlimited number of messages, each of which can be up to 64KB in size. Queues are assessable via REST services from anywhere via the internet, and supports .NET, Java and Node.JS client libraries.


SharePoint Infrastructure Planning and Design

Posted on

The Infrastructure Planning and Design (IPD) series provides guidance for Microsoft infrastructure products. The series is a collection of documents that leads the reader through a sequence of core decision points to design an infrastructure for Microsoft products. It also provides a means to validate design decisions with the business to ensure that the solution meets the requirements for both business and infrastructure stakeholders.

The IPD documents are designed to be used by the following IT personnel:

  • Infrastructure planners and architects who have a firm operational grasp of the technology.
  • Partners and consultants who design infrastructure solutions.
  • Business managers who want to understand how the technology decisions being made both support and affect the business.

Data Protection Manager

This guide enables you to quickly identify what types of data to protect, what the recovery goals are, and what the protection strategy is for achieving those goals. This guide incorporates best practice guidance from the Data Protection Manager engineering team to help you create an optimized infrastructure design that meets the business requirements.

Operations Manager

This guide outlines the infrastructure design elements that are crucial to a successful implementation of Operations Manager. It guides you through the process of designing components, layout, and connectivity in a logical, sequential order. You’ll find easy-to-follow steps on identification and design of the required management groups, helping you to optimize the management infrastructure.

Virtual Machine Manager

This guide outlines the elements that are crucial to an optimized design of Virtual Machine Manager (VMM). It leads you through the process of identifying the business and technical requirements for managing virtualization, designing integration with System Center 2012 – Operations Manager if required, and then determining the number, size, and placement of the VMM servers. It will help you to confidently plan for the centralized administration of physical and virtual machines.

SharePoint Online—Evaluating Software-plus-Services

This guide presents a clear comparison of SharePoint collaboration technologies across on-premises, standard hosting, and dedicated hosting scenarios. It is designed to be used as a framework for evaluating the business and technical feasibility of moving to Microsoft SharePoint Online. It identifies key SharePoint workloads, and provides a customized assessment to help the organization determine which offering best meets the organization’s requirements.

SharePoint Server 2010

This guide takes the IT architect through an easy-to-follow planning and design process to successfully create a SharePoint Server infrastructure that is appropriately placed, sized, and designed to deliver the desired business benefits, while also considering the performance, capacity, and fault tolerance of the system. It addresses the scenarios most likely to be encountered by someone designing a SharePoint Server infrastructure.





Microsoft selects Katpro as Windows Azure Circle partner!!!

Posted on

We are pleased and excited to announce that Katpro has successfully been enrolled on to Microsoft Corporation’s elite Windows Azure Circle Partner program. This elite program is reserved for Microsoft’s partners who have achieved success in delivering Windows Azure based solutions.
Windows Azure is an open and flexible cloud platform that enables companies to quickly build, deploy, and manage applications across a global network of Microsoft-managed data centers. Enterprises can build applications using any language, tool, or framework and integrate public cloud applications with a current IT environment.
This achievement acknowledges the serious investment Katpro has made in developing and delivering world-class cloud computing solutions on Microsoft’s Windows Azure Platform. We are committed to enable our customers realize the full potential of cloud computing. We are committed to demystify cloud and help our customers in their journey to cloud.


ASP.NET MVC 4 Mobile Features

Posted on

The Apple iOS (iPhone and iPad) uses Objective C, Google Android uses Java and Windows Phone uses Silverlight, yet each one of these options has a distinct API and a distinct market. Choosing to focus on one particular technology stack could leave 50 percent of the market—or more—unable to use your application. If you choose to try to support all of these platforms, you have at least three distinct codebases to maintain, significantly increasing your development and maintenance costs.

The Hybrid Application Concept

The basic concept of a hybrid application is to wrap a mobile-optimized Web application in a device-specific native application shell. The native application shell hosts a Web browser control that’s configured to launch the specific mobile application URL when the shell application launches. Other UI elements can be provided in the native application shell as needed, but only the Web browser control is required. The native Web browser control then listens to the URLs being requested as the user navigates the site. When the user requests a specific URL that requires native functionality, the Web browser control interrupts the navigation event and instead invokes the native functionality. As the user completes the native process, the application navigates the Web browser control back into the Web site flow in the appropriate location.

ASP.NET MVC uses the Model-View-Controller architecture pattern, which consists of three components – the model, the view and the controller.

The model is the core component that actually implements the logic of a particular data aspect of the application. The model’s logic is implemented in the controller component, which facilitates changes to the model. The controller passes the new information to the view, where it is displayed in the user interface. This pattern simplifies the process of application creation and use because it keeps the different logic layers of the application (input logic, business logic and UI logic) separated. Application building is complex, but the MVC pattern facilitates focus on just one aspect at a time. This greatly reduces potential complications and also allows for increased interoperability between developers.

The Benefits of MVC vs Traditional ASP.NET

The traditional ASP.NET framework uses WebForms to build Web application user interfaces. They help mete out the HTML interface from the application logic and bind server-side .NET controls to reduce the amount of code required. However, MVC improves on the capabilities of ASP.NET and accelerates the deployment and usage of the framework in enterprise Web applications. The benefits include:

  • Simpler and more efficient page lifecycle
  • Availability for multiple forms on a page
  • Improved Ajax functionality and efficient jQuery page loads
  • Ability to conduct multiple tasks on the different forms of a page
  • Total control over HTML and better interaction with JavaScript
  • Easier visibility into system bugs and more streamlined process of identification and correction
  • Future-proof as new developments such as HTML5 become more commonplace MVC Architecture

Posted on

The Model-View-Controller (MVC) architectural pattern separates an application into three main components: the model, the view, and the controller. The ASP.NET MVC framework provides an alternative to the ASP.NET Web Forms pattern for creating Web applications.

MVC design pattern

Model View Controller design pattern

The MVC framework includes the following components:




Advantages of an MVC-Based Web Application

The ASP.NET MVC framework offers the following advantages:

  • It makes it easier to manage complexity by dividing an application into the model, the view, and the controller.
  • It does not use view state or server-based forms. This makes the MVC framework ideal for developers who want full control over the behavior of an application.
  • It uses a Front Controller pattern that processes Web application requests through a single controller. This enables you to design an application that supports a rich routing infrastructure. For more information,
  • It provides better support for test-driven development (TDD).
  • It works well for Web applications that are supported by large teams of developers and for Web designers who need a high degree of control over the application behavior.

SharePoint Service Bus

Posted on

Windows Azure Service Bus provides a hosted, secure, and widely available infrastructure for widespread communication, large-scale event distribution, naming, and service publishing. Service Bus provides connectivity options for Windows Communication Foundation (WCF) and other service endpoints – including REST endpoints — that would otherwise be difficult or impossible to reach. Service Bus Queues support a brokered messaging communication model. When using queues, components of a distributed application do not communicate directly with each other, they instead exchange messages via a queue, which acts as an intermediary. A message producer (sender) hands off a message to the queue and then continues its processing.



Service Bus queues are a general-purpose technology that can be used for a wide variety of scenarios:

  • Communication between web and worker roles in a multi-tier Windows Azure application
  • Communication between on-premises apps and Windows Azure hosted apps in a hybrid solution
  • Communication between components of a distributed application running on-premises in different organizations or departments of an organization

The Windows Azure AppFabric Service Bus September 2011 (version 1.5)  release introduces enhancements to the Service Bus such as “brokered” messaging capabilities, through namespace entities represented by queues, topics and subscriptions. The Brokered Messaging infrastructure enables to build an Event-driven distributed Service Oriented Architecture, Distributed Asynchronous Cloud Notifications and Intra-Application Messaging. Basically, it can be useful anywhere where  a loosely decouple messaging is required such as Queuing and Publish-Subscribe messaging across both on-promises and cloud targets.

From the abstraction point of the view, the Azure Service Bus represents a logical connectivity between the event sources and their consumers using a loosely decouple model. The consumers need to subscribe their interest to the Service Bus in prior of receiving a specific event interest. This metadata (subscriptions) represents a logical connectivity for event interest; they are stored on the cloud a managed by tools and/or specific client applications.


Introduction to Android for Mobile Application Development

Posted on

Android has emerged as a new mobile development platform, building on past successes while avoiding past failures of other platforms. Designed to empower mobile software developers to write innovative mobile applications, Android is open source platform, with no up-front fees, and developers enjoy many benefits over other competing platforms. Touted as an innovative and open platform, Android is being positioned to address the growing needs of the mobile marketplace.

The open source appliance platform

Android is a complete operating environment based upon the Linux® V2.6 kernel. Initially, the deployment target for Android was the mobile-phone arena, including smart phones and lower-cost flip-phone devices. However, Android’s full range of computing services and rich functional support have the potential to extend beyond the mobile-phone market. Android can be useful for other platforms and applications.The BlackBerry and iPhone, which have appealing and high-volume mobile platforms, are addressing opposite ends of a spectrum. The BlackBerry is rock-solid for the enterprise business user. For a consumer device, it’s hard to compete with the iPhone for ease of use and the “cool factor.” Android, a young and yet-unproven platform, has the potential to play at both ends of the mobile-phone spectrum and perhaps even bridge the gulf between work and play.

The Android platform

With Android’s breadth of capabilities, it would be easy to confuse it with a desktop operating system. Android is a layered environment built upon a foundation of the Linux kernel, and it includes rich functions. The UI subsystem includes:

  • Windows
  • Views
  • Widgets for displaying common elements such as edit boxes, lists, and drop-down lists
 Android software layers

The Android software layers

Android gives you a World-class platform for creating and games for Android users everywhere. Android is the first complete OpenSource free Mobile platform. Android providing to completely alter the look and feel and functions of a mobile device.Android brings million of Phones,Tablets, and other devices. We has expertise in the development and Integration of Android Application. Katpro’s Mobile App developers and mobility Consultants understand the possibilities that Android OS offers and also are up to date.

Benefits of Mobile Application

  • Speed and Reliability.
  • Improved productivity.
  • Enhanced User Experience.
  • Portability and Ease of Development
  • Uniform Work and Feel.
  • Reduced Development Costs.