Cloud enabled storage - the yet-to-be-born technology that enables a customer to "own" their data yet use computing power on the "Cloud" will be the next big thing.
When SAN and NAS was first introduced, they were considered unnecessary innovation that did nothing but extract money from customer's pocket. However, gradually, they took over the enterprise storage because of their ability to split data storage from data processing (the servers, etc). This prove to be a key capability customers need.
Moving to the next big thing - cloud, how can someone capitalized on it?
One key trap for Cloud computing is the ownership and control of data. For consumers, many are willing (knowingly or not) to trade their ownership of data (i.e. privacy) for free services. So Googles, Yahoos are all offering "the future of computing - Cloud" with minimum resistance.
The story is different in enterprise computing though, given the number of incidents in the past while related to Cloud computing, privacy breach, data leak, there is enough doubt in the enterprise market that the threat of handling core business data to some one one the Cloud is far out weight the benefit -- after all, enterprise rely on data to survive and make money, unlike consumers who are just consuming convenient data services.
So, what is the next big thing? Since we have separated data storage from data processing with SAN, NAS, etc, it is logical that we can keep data storage in house, and consume data process (utility computing was not new idea at all).
Of course the current protocol used to access data will not be sufficient for reverse hosting the data. New protocols and ideas need to be invented.
One probably candidate is in-memory database - which hosts the database in memory, and only need burst network bandwidth to load data initially.
Another approach is let customer run database services in house, and run application services on the Cloud.
On the fly data compression will again be a topic - the data flow through the network pipe between data owner and data processor should be compressed, and encrypted. We know database access are great candidate for data compression because of the sparsity of the data retrieved.
Splitting data storage and data processing is the key for the success of Cloud computing in Enterprise world. This won't be easy, and will not be driven by companies like Google or Facebook which business model is to exploit customer data. New start-ups, or EMC, NetApp may have a chance.
I will be working on an architecture framework that enables secure and efficient data flow between data storage and data processing.
Data Storage <=> Data Processor <=====> Data Access
The new architecture is beyond just data transferring, because the application architecture we are using today are designed based on proximity between data and processor, the remote-access architecture now-a-days are more or less a patch to the data-processor combined model.
The new model need to be built on the assumption that Data Storage can be far away from Data Processor. This assumption is the ultimate enabler for Cloud in enterprise.
If IBM catches this departing train, the day that most people will be using a handful of super fast computers MAY come back.
Well, since the super computers will not store your data, so they are not as scary as last time they appeared.
Of course part of the architecture is to ensure the data processor can not reconstruct data it processes -- better yet -- the processor's partition that used to process one customers data should be isolated and inaccessible by anyone else.
Sounds like an interesting idea, isn't it?
One day, AI will replace human and becomes the new ruler of the world. (yeah, you are right, the Robots).
This is because some people "need to" create these robots to conquer others - unfortunately, those creators are not fundamentally different than their "enemies".
So, ironically, their ultimate creation will be capable of conquer everyone - the creators included.
They know this! But they cannot resist the fear of "being conquered first".
Thursday, June 10, 2010
Wednesday, April 07, 2010
Error during EHP1 install for SAP NetWeaver JAVA
You may see the following error during READ_PROFILE phase
Error while reading properties from /usr/sap/C11/SYS/profile/DEFAULT.PFL. Variables [/J2EE/DBSystem/DBTypeFo
rSAP, /J2EE/DBSystem/DBName] not found. A possible reason can be that the start release is lower than 6.40 SPS09.
Error while reading properties from /usr/sap/C11/SYS/profile/DEFAULT.PFL. Variables [/J2EE/DBSystem/DBTypeFo
rSAP, /J2EE/DBSystem/DBName] not found. A possible reason can be that the start release is lower than 6.40 SPS09.
But you are sure you are running NetWeaver 7.0, after all you are installing Enhancement Pack.
You tried to add variable "/J2EE/DBSystem/DBTypeForSAP, /J2EE/DBSystem/DBName" to the DEFAULT.PFL manually, but you still get the error.
You tried to look up these 2 variables in SDN, help, or notes, but found nothing. Don't blame yourself, there is nothing about these variables.
You should add:
j2ee/dbtype = ORA
j2ee/dbname = C11
sure if you use MS SQL, you should add "j2ee/dbtype = mss".
Yeah, as confusing as it is, j2ee/dbtype and j2ee/dbname are the real variables it's looking for. The 2 shown in the error log, are just "superficial" names.
Good luck EHP-ing.
Monday, February 01, 2010
What's really wrong about iPad from Apple?
It's not a big surprise that iPad disappoints. While thousands of super smart people all trying to guess what handful of super smart people can bring up to the table -- the guess will always be better than the real -- the guessers simply outnumbers the producers.
OK, I'm no designer, Although I own iPhone, iPod touch, iPod, and 4 Macs, I don't think I'll by an iPad.
Why? Not because the screen resolution (which I don't like) or the size.
But because iPad was designed totally wrong. It was designed for Apple shareholders, not Apple customers.
iPad was designed to avoid cannibalize notebook market. It was trimmed down not because technical ability, but was because it needs to leave market for MacBooks. Wrong thinking!!!
The iPad could be revolutionary due to it's interface. It could be the real game changer for the PC industry. It should not find itself in a limited squeezed niche. It should be designed to do everything a notebook can do, but more (the multi-touch interface and new multi-touch apps).
Why be afraid of cannibalizing notebook market? Who's there to lose? It's PC notebooks, they still command over 90% of the market share. Why does one think Apple can only sell this 3rd category to existing Apple customers? If this is a full function computer, but with multi-touch interface, there will be more PC users switch. Now, people have perfect excuse not even give it a try - it's limited, it can't do much....
By "protecting" the notebook category, Apple is not only protecting it's MacBook business, but also protecting the other 90% of notebooks running Windows.
I think Steve Jobs reached such a point that a line of business is more emotional than practical. He started Apple selling computers, and he's having trouble letting the notebook business go. Or Apple share holders want to see "increased income" rather than "replaced" income.
They don't understand, if you have 90% market share to gain, you don't need to how to limit yourself to save others. This time, Steve did not understand either.
iPad, could have change the PC industry if it really delivers a MacBook in the shell of 4 iPhones.
It did not, and it disappointed the world. I don't know if Steve have a chance to re-try.
Subscribe to:
Posts (Atom)