I have read loads and loads of stuff about the following shares, analyzed a lot about them, to me, for now, these are the best and safe bets. Also please have a look at the disclaimer down below the article. Thanks.
NTPC
Trademark indian govt power share, one can buy around 190.
YESBANK
very strong fundamentals, good management model, good quarterly results and on the uptrend, very positive outllook as far the current govt foresight is concerned (hopefully ok), different and dynamic from traditional banking,one can buy around 125.
SATYAM COMPUTERS
Tech mahindra bought satyam cheaply, dead cheap i would say, one can buy around 65 for now
JAIPRAKASH ASSOCIATES
NO.2 after dlf, stable when you compare it with DLF (not that fluctuating), not so costly, not just into construction but diversified into many businesses - one can buy around 190 levels.
ANDHRA BANK
not many aware of its revenues, its all set to explode all over india - one can buy now, right now.
IDBIBANK
well established infront of the competitors like icici, got name as a faithful bank, strong homeloan sector accounts, doing well offlate, one can buy around 100.
RELIANCE NATURALS
Won the recent court hearing, once people minted money with this script, its available at a decent price now, can pick up this script around 80.
disclaimer : Im holding all the above, but you guys please dont rely on me, its ur money, you are the best judge on that, so you decide. Its my blog and just my opinions.
ALOK INDUSTRIES
a textile stock, i love it because it is around 20 rupees, but thats not all, its a strong company, this rules the textile industry in many areas of INDIA, and it is currently at very low levels. The textile industry has been going through a rough patch since more than 2 years, and hence the low price...and there are lot of promises ahead from the new MP Mr. Maran, he is in the news everyday. Alok industries is in good profits if you look at the past quarterly results and aggressive in its expansion plans through out India. I think its a very safe Bet, allows us to buy volumes.
BIOCON
is a gold mine for me, pick it up with both of your hands whenever the market is down, if you are a long term investor then you have struck gold i would say. Biocon's latest release of the cheapest diabetes drug would be a trendsetter for the company in the coming months (or years). Biocon has been waiting for this kind of success since ages, whatever, its always been a strong Indian biotechnological company.
Friday, June 26, 2009
Family Politics : Shame on us.
This article is not in particular about any particular politician of INDIA, no criticism, its a discussion about our welfare, well being and foresight on our Nation's Pride. We, the People of India, even after 62 years of independence, have the same mentality of casual acceptance, means we dont have a problem if a politicians son is getting on to the heir by default. Often, even highly educated people take it for granted, and more ridiculously they praise a politicians son in acceptance, crazy. Some talk about their looks, their speech, their body and their smile. This is INDIA my dear...not a TOY to play, more than a billion precious souls, lets come out of this shameful acceptance of politicians sons and families by default. Think about his zeal, experience and capabilities to lead this precious soil but not his birth star. Let's Wakeup.
Even a kid can tell that the stage is being setup for RAHUL GANDHI's would be primeministership. Im not against him personally, but this is INDIA, every Indian needs to have high regards for the highest post. So Mr. Manmohan singh and Mr. Rahul Gandhi are one and the same ? Astonishing !!! I know there is no qualification for Indian politics, but what is interesting to me is the mere INDIAN thinking.
Why should we be happy if someone's son is becoming an MLA, MP, CM or PM ? insane isn't it. It's like a servant being happy about his master, it's like ages back we had RAJA and his sons's. Laloo and then his wife, NTR and his son-in-law, Karunanidhi and his son, Rajasekhar Reddy and his son, Nehru, Indira, Rajiv and now Rahul ? Also lets not get into the concept of "one guy is better than the other guy", let's start thinking about the best ?
INDIA is so easy ? Family Property ? is it ? Lets be ASHAMED of accepting sons and families just like that, for decades and decades. Have very high regards for the country. It's high time. Lets think. Thanks to Mr. JaiPrakashNarayan for making educated minds mature.
Even a kid can tell that the stage is being setup for RAHUL GANDHI's would be primeministership. Im not against him personally, but this is INDIA, every Indian needs to have high regards for the highest post. So Mr. Manmohan singh and Mr. Rahul Gandhi are one and the same ? Astonishing !!! I know there is no qualification for Indian politics, but what is interesting to me is the mere INDIAN thinking.
Why should we be happy if someone's son is becoming an MLA, MP, CM or PM ? insane isn't it. It's like a servant being happy about his master, it's like ages back we had RAJA and his sons's. Laloo and then his wife, NTR and his son-in-law, Karunanidhi and his son, Rajasekhar Reddy and his son, Nehru, Indira, Rajiv and now Rahul ? Also lets not get into the concept of "one guy is better than the other guy", let's start thinking about the best ?
INDIA is so easy ? Family Property ? is it ? Lets be ASHAMED of accepting sons and families just like that, for decades and decades. Have very high regards for the country. It's high time. Lets think. Thanks to Mr. JaiPrakashNarayan for making educated minds mature.
Microsoft's Velocity - Distributed Caching
Introduction
The rate of change of position, in physics, is termed as VELOCITY, has very little coincidence with the concept of “Distributed Caching”, but MS-Velocity is definitely catching up slowly but surely more on its conceptual merits and on the need of the hour of the “software applications world”. The terms scalability and availability are becoming a default necessity in today’s software applications, hence ‘ms-velocity’ is here.
Scope of this Article
Thorough understanding of, “The Microsoft’s way of Distributed Caching”
Who is making this noise
A project team/code named “VELOCITY” within Microsoft. It is at beta stage (Beta is nothing but just one step to go live, though beta version might also have several sub-versions in it). Microsoft has a much fancier name for beta; called CTP, “community technology preview” in full and the versions are called CTP1, CTP2 & CTP3. Currently velocity is at CTP3. Frankly speaking, to me, it looks like an alpha version and gives you a feeling of integrating bits and pieces. For eg:- For most of the time CTP3 bits were ready but the CTP3 samples were missing, ofcourse they are ready now, now the help file to understand the sample code is missing.
Caching Story
A cache is a type of dynamic and high speed memory that is used to supplement the function of the central processing unit and the physical disk storage. As the microprocessor processes data, it looks first in the cache memory and if it finds the data there it does not have to do the more time-consuming reading of data from larger memory. The cache acts as a buffer when the cpu tries to access data from the disk so the data travelling from the cpu and physical disks can have synchronized speed. Disk reading and writing process is generally slower than cpu function.
Caching in Web Applications
We cannot imagine the MSN portal or the Amazon web site, or the corporate SAP financial application being down when we need it. Same is the case with any online banking website in the world. Fundamentally, applications need to be available all the time to support access at any time, and from anywhere.
Another major expectation, especially from application developers and from datacenters is that of scalable and available applications at a low cost.
One of the most important factors in building high-performance, scalable web applications is the ability to store items, whether data objects, pages, or parts of a page, in memory the initial time they are requested. You can store these items on the Web Server or other software in the request stream, such as the proxy server or browser. This allows you to avoid recreating information that satisfied a previous request, particularly information that demands significant processor time or other resources. Known as caching, it allows you to use a number of techniques to store page output or application data across HTTP requests and reuse it. Thus, the server does not have to recreate information, saving time and resources.
Distributed Caching is not entirely a Brand New invention.
Distributed caches are not new – during the last couple of years several caching products (memcached, ncache & sharedcache) have emerged to address the performance and scalability needs of applications. Most of these support key-based access. Other than memcached (by Danga Interactive), which is an open source technology, most others target enterprises and enterprise workloads and scale. I think the web workloads require considerably large scale, with 1000s of cache nodes in a cluster. The web scale distributed caches not only require mechanisms that can scale and provide availability in very large clusters, they must be easy to manage or self-managed.
ASP.NET Caching & How Velocity is different
Velocity is all about caching & only caching (exclusively); prior discussing Velocity, I would like to brief the basics of ASP.NET caching. In ASP.NET caching we have two types of caching a) page output cache & b) application cache. Page output caching saves the output of page processing and re-uses the output instead of re-processing the page when a user requests the page again, where as application caching allows you to cache data you generate, could be any object like for eg:- dataset or any business object.
ASP.net cache object runs in the same process as your web application, it could be an advantage depending on your need and at the same time it could be a disadvantage. Whatever, it makes it clear that it is not a distributed cache, which means the ASP.NET cache cannot be shared among multiple servers. If you want to share the same ASP.NET cache among multiple servers, you must duplicate the cache for each server.
The greatest advantage of ASP.NET is that it works great for web applications running on a single server, but when you have a web-farm scenario consisting of multiple web servers then there is no straight forward implementation. Similarly whenever a server fails the natural thing we would do is to reload the data programmatically in to our objects. These two issues can be considered as limitations because situations like this doesn’t help sites which has millions/billions of users. Scalability is an issue with ASP.NET caching, unless the programmer does a brilliant work around.
Velocity addresses the above limitations of ASP.NET caching.
In the near future, “Velocity” envisions being an integral part of the .NET application stack targeting both enterprise and web workloads (and scale).
As applications start using the caches for data access, it’s easy to believe, they will demand richer data services like query, transactions, analytics, synchronization etc. We never know that the requirement of LINQ queries on distributed cache on most of the .NET applications could be one of the most programming requirements in the coming days, just like they query the backend SQL Server database. Microsoft envisions “Velocity” to become a comprehensive distributed caching platform. The performance, scale, and availability functionality of “Velocity” along with its rich data services will allow for rich web and enterprise applications development and deployment.
Distributed Caching fits here
In general, distributed caches are especially ideal for applications with the following characteristics…
Ø There is a considerable number of data requests that are mostly read (e.g. product catalogs)
Ø Large concurrent access to such data can be provided by replicating the catalog data on multiple cache nodes. Since updates are infrequent to such data, maintaining consistency (synchronously or asynchronously) is not very expensive.
Ø Applications that can tolerate some staleness of data
Such applications can provide better performance and scale by not requiring immediate updates over refreshing of caches
Ø Applications that can work with highly partitioned data (e.g. session data, shopping cart)
Ø High scale and performance can be supported by partitioning and distributing data across multiple cache nodes, and thereby distributing data processing across the cache nodes
Ø Applications that can work well with eventual consistency.
1.2 System Requirements & Prerequisites
Supported Operating Systems:
Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Vista Service Pack 1; Windows XP Service Pack 3
How to attack Velocity in notime
Download the CTP3 samples, do the setup for shared folder kind of caching on a single machine (your pc or laptop). Do not get confused by powershell tool and all that help on that, forget it. Simply open the velocity administration tool and try to start the cluster by typing Start-CacheCluster (remember this works happily only if you are using CTP3 dlls and the CTP3 samples, also remember you have to copy the installation dlls to your sample application folder and add references). That's it you are all set.
You will get to see more on velocity day by day here, im delighted at its ease and especially with the shiftover from the existing session code to the distributed cache plug-in just by few changes in the configuration file. Cool.
The rate of change of position, in physics, is termed as VELOCITY, has very little coincidence with the concept of “Distributed Caching”, but MS-Velocity is definitely catching up slowly but surely more on its conceptual merits and on the need of the hour of the “software applications world”. The terms scalability and availability are becoming a default necessity in today’s software applications, hence ‘ms-velocity’ is here.
Scope of this Article
Thorough understanding of, “The Microsoft’s way of Distributed Caching”
Who is making this noise
A project team/code named “VELOCITY” within Microsoft. It is at beta stage (Beta is nothing but just one step to go live, though beta version might also have several sub-versions in it). Microsoft has a much fancier name for beta; called CTP, “community technology preview” in full and the versions are called CTP1, CTP2 & CTP3. Currently velocity is at CTP3. Frankly speaking, to me, it looks like an alpha version and gives you a feeling of integrating bits and pieces. For eg:- For most of the time CTP3 bits were ready but the CTP3 samples were missing, ofcourse they are ready now, now the help file to understand the sample code is missing.
Caching Story
A cache is a type of dynamic and high speed memory that is used to supplement the function of the central processing unit and the physical disk storage. As the microprocessor processes data, it looks first in the cache memory and if it finds the data there it does not have to do the more time-consuming reading of data from larger memory. The cache acts as a buffer when the cpu tries to access data from the disk so the data travelling from the cpu and physical disks can have synchronized speed. Disk reading and writing process is generally slower than cpu function.
Caching in Web Applications
We cannot imagine the MSN portal or the Amazon web site, or the corporate SAP financial application being down when we need it. Same is the case with any online banking website in the world. Fundamentally, applications need to be available all the time to support access at any time, and from anywhere.
Another major expectation, especially from application developers and from datacenters is that of scalable and available applications at a low cost.
One of the most important factors in building high-performance, scalable web applications is the ability to store items, whether data objects, pages, or parts of a page, in memory the initial time they are requested. You can store these items on the Web Server or other software in the request stream, such as the proxy server or browser. This allows you to avoid recreating information that satisfied a previous request, particularly information that demands significant processor time or other resources. Known as caching, it allows you to use a number of techniques to store page output or application data across HTTP requests and reuse it. Thus, the server does not have to recreate information, saving time and resources.
Distributed Caching is not entirely a Brand New invention.
Distributed caches are not new – during the last couple of years several caching products (memcached, ncache & sharedcache) have emerged to address the performance and scalability needs of applications. Most of these support key-based access. Other than memcached (by Danga Interactive), which is an open source technology, most others target enterprises and enterprise workloads and scale. I think the web workloads require considerably large scale, with 1000s of cache nodes in a cluster. The web scale distributed caches not only require mechanisms that can scale and provide availability in very large clusters, they must be easy to manage or self-managed.
ASP.NET Caching & How Velocity is different
Velocity is all about caching & only caching (exclusively); prior discussing Velocity, I would like to brief the basics of ASP.NET caching. In ASP.NET caching we have two types of caching a) page output cache & b) application cache. Page output caching saves the output of page processing and re-uses the output instead of re-processing the page when a user requests the page again, where as application caching allows you to cache data you generate, could be any object like for eg:- dataset or any business object.
ASP.net cache object runs in the same process as your web application, it could be an advantage depending on your need and at the same time it could be a disadvantage. Whatever, it makes it clear that it is not a distributed cache, which means the ASP.NET cache cannot be shared among multiple servers. If you want to share the same ASP.NET cache among multiple servers, you must duplicate the cache for each server.
The greatest advantage of ASP.NET is that it works great for web applications running on a single server, but when you have a web-farm scenario consisting of multiple web servers then there is no straight forward implementation. Similarly whenever a server fails the natural thing we would do is to reload the data programmatically in to our objects. These two issues can be considered as limitations because situations like this doesn’t help sites which has millions/billions of users. Scalability is an issue with ASP.NET caching, unless the programmer does a brilliant work around.
Velocity addresses the above limitations of ASP.NET caching.
In the near future, “Velocity” envisions being an integral part of the .NET application stack targeting both enterprise and web workloads (and scale).
As applications start using the caches for data access, it’s easy to believe, they will demand richer data services like query, transactions, analytics, synchronization etc. We never know that the requirement of LINQ queries on distributed cache on most of the .NET applications could be one of the most programming requirements in the coming days, just like they query the backend SQL Server database. Microsoft envisions “Velocity” to become a comprehensive distributed caching platform. The performance, scale, and availability functionality of “Velocity” along with its rich data services will allow for rich web and enterprise applications development and deployment.
Distributed Caching fits here
In general, distributed caches are especially ideal for applications with the following characteristics…
Ø There is a considerable number of data requests that are mostly read (e.g. product catalogs)
Ø Large concurrent access to such data can be provided by replicating the catalog data on multiple cache nodes. Since updates are infrequent to such data, maintaining consistency (synchronously or asynchronously) is not very expensive.
Ø Applications that can tolerate some staleness of data
Such applications can provide better performance and scale by not requiring immediate updates over refreshing of caches
Ø Applications that can work with highly partitioned data (e.g. session data, shopping cart)
Ø High scale and performance can be supported by partitioning and distributing data across multiple cache nodes, and thereby distributing data processing across the cache nodes
Ø Applications that can work well with eventual consistency.
1.2 System Requirements & Prerequisites
Supported Operating Systems:
Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Vista Service Pack 1; Windows XP Service Pack 3
How to attack Velocity in notime
Download the CTP3 samples, do the setup for shared folder kind of caching on a single machine (your pc or laptop). Do not get confused by powershell tool and all that help on that, forget it. Simply open the velocity administration tool and try to start the cluster by typing Start-CacheCluster (remember this works happily only if you are using CTP3 dlls and the CTP3 samples, also remember you have to copy the installation dlls to your sample application folder and add references). That's it you are all set.
You will get to see more on velocity day by day here, im delighted at its ease and especially with the shiftover from the existing session code to the distributed cache plug-in just by few changes in the configuration file. Cool.
Subscribe to:
Posts (Atom)
Posts
