"Fortunate are those who take the first steps.” ― Paulo Coelho

Certified for 70-487 !! [ recently cleared 70-532 too ]

Last week I have cleared my 70-487 Developing Microsoft Azure and Web Services certification. I have started preparing for 45+ days on and off, mostly weekend reading and able to clear through second shot offer. There are plenty of materials there to prepare, but I urge to stick with official curriculum + MVA (microsoft virtual academy videos) for this exam. I had internal employee measure up account with some sample questions, with deep understanding of all those concepts + small hands on helped me crack it. Here is what you will learn through this certification,

9780735677241f1256.70-532_3E18159EChapter 1) Accessing Data using – EF, WCF DataServices, Azure Data Storage, Transaction, Caching, XML ds (data). ..

Chapter 2) Querying and Manipulating data by using EF – LINQ to Objects, entities, ADO.NET, EF, Lazy loading,data model…

Chapter 3) Designing and implementing WCF Services – SOA concepts, WCF API obj and config, Securing, consuming, version, Azure Service bus, one way-two way, hosting..

Chapter 4) Create and consume Web API based services – Design a web api, implement, secure, host and consume web api web services

Chapter 5): Deploying web application and Services- Design, deployment strategy, Configure, manage packages using Nuget, create, configure and publish a web package, share assemblies.

Overall, we  will learn back-end programming/db programming + infra projecs like publishing, nuget, etc also helps us to uinderstand end -to end.

Study notes from Chris –

[Update: May first week  – I have cleared 70-532 🙂 ]


April 8, 2015 Posted by | .NET General, Certification | , , , , | Leave a comment

About -Azure Storage Explorer utility

I got this tools link while searching for Azure Storage free tools – explorer. Azure Storage Explorer is simply a nice tool to work and explore. It is free, elegant and clutter free to use. It just fulfill our expectation. #Good job by david

Download it from here –

This slideshow requires JavaScript.

February 2, 2015 Posted by | Azure, Azure Storage, Azure Tools | | Leave a comment

Windows Azure storage getting started

My reading notes from this book which I bought recently – Developing Cloud Applications with Windows Azure Storage by Paul Mehner.


I will try simplify the content with examples for quicker references. Hope you enjoy this series about Windows Azure Storage.

+ Windows Azure Storage(WAS) – provides independent data management services to our application – data storage for any application/any platform/any language over HTTP

+  We are moving to NoSQL era due to volume of data/performance. In 1970’s we started with flat file –> file based relational db’s -> Relational -> Hierarchical -> N/w -> Federated -> NoSQL (not only SQL).

+ WAS is implements as NoSQL-styled db.

+ There are 3 high level data types in WAS – Blob, Tables and Queues.

+ WAS is not a relational db

+ Access to this WAS is done with simple REST API

+ WAS supports scalability, replication, geo-locaiton, geo-replication, independent and interoperability, maintains fully consistent model (Amazon S3 is eventually consitent model – read operation after update may/may not return the very recent updated data)

BLOBS (for storing unstructured data –  doc, pictures, videos and music)


>  Windows Azure blob service provides a simple RESTful APi for storing and retrieving unstructured data.

> Blobs are organized into Containers(similar to directories), you can have any number of blob’s under containers.

> Blobs and blob containers are easily accessible with unique url’s.

> You can set public access as well.

> Ideal for the storage of web content



> Windows Azure Table service  provides a simple RESTful Api for storing massive amounts of semi structured data.

> These tables are not at all like relational db tables.

> Rows are called entities, consist of properties, which are like columns.

> Different rows stored in the same table can often have different set of properties.



> Queues do not provide permanent storage of the message they handle.

> Unprocessed messages will be deleted from the queue after 7 days.

> Same like MSMQ, it will get deleted upon read, exposed through RESTful API’s.

Happy Azuring!

February 2, 2015 Posted by | Azure Storage | | Leave a comment


%d bloggers like this: