Thursday, November 02, 2006
Tuesday, July 11, 2006
Tuesday, July 04, 2006
Fast web services
Service-Oriented Architecture blog writes:
....that a two to ten-fold performance gain has been documented with the application of Fast Web Services in XML parsing. But he notes that performance hinges on the amount of time applications spend in the tasks of serialization and parsing. "A multiple of 2-10x may sound like a lot, but if the original time spent doing these tasks is so small in comparison to the end-to-end timescales, there isn’t much overall gain," he said. Plus, there are other ways to speed up Web services processing.
Colin comes up with a rule of thumb to follow: use text-based XML for interoperability across systems, and Binary XML or Fast Web Services for system-specific tasks such in-memory messaging or platform-specific tools.
....that a two to ten-fold performance gain has been documented with the application of Fast Web Services in XML parsing. But he notes that performance hinges on the amount of time applications spend in the tasks of serialization and parsing. "A multiple of 2-10x may sound like a lot, but if the original time spent doing these tasks is so small in comparison to the end-to-end timescales, there isn’t much overall gain," he said. Plus, there are other ways to speed up Web services processing.
Colin comes up with a rule of thumb to follow: use text-based XML for interoperability across systems, and Binary XML or Fast Web Services for system-specific tasks such in-memory messaging or platform-specific tools.
Thursday, September 15, 2005
Monday, September 12, 2005
Consider becoming Buddhist
 | You scored as Buddhism. Your beliefs most closely resemble those of Buddhism. Do more research on Buddhism and possibly consider becoming Buddhist, if you are not already. In Buddhism, there are Four Noble Truths: (1) Life is suffering. (2) All suffering is caused by ignorance of the nature of reality and the craving, attachment, and grasping that result from such ignorance. (3) Suffering can be ended by overcoming ignorance and attachment. (4) The path to the suppression of suffering is the Noble Eightfold Path, which consists of right views, right intention, right speech, right action, right livelihood, right effort, right-mindedness, and right contemplation. These eight are usually divided into three categories that base the Buddhist faith: morality, wisdom, and samadhi, or concentration. In Buddhism, there is no hierarchy, nor caste system; the Buddha taught that one's spiritual worth is not based on birth.
Which religion is the right one for you? (new version) created with QuizFarm.com |
Wednesday, April 06, 2005
An open source accounting software for Indian markets - My wish list
Set of components
This open source system should be developed as a set of components. Each and every function/feature of this application should be exposed as a web service. These set of components/methods should be accessible by SOAP,REST and Programming languages based APIs. By this way, integration, customization and extending the system is lot easy.
Breaking User interface lock-in
As I noted previously, user interface lock-in of existing systems like tally keeps the users. This kind of well defined set of components allows us to develop multiple interfaces. Any company can build a new interface, an Interface nearly identical to tally with same set of screens and short-cut keys will be the best starting point. By this interface tally-savvy users/accountants have no reason to stick with their pirated tally. Learning curve for data entry operators and switching cost for companies are almost zero.
Plug-ins
This modular architecture should support plug-ins. Plug-ins are optional components that can be replaced at will, either at run time, configuration time or at development time. For example when users want to add new features like sending SMS from the accounting software, they can write a new plug-in and attach to this core system.
Plug-ins are like extensions to the core systems and can be used as adapters to connect other systems like inventory. Without even touching any core part of this system it should able easy to write plug-ins. Like reading data from a third party application or from a Excel sheet or calendar system.
Data import/export API
I have already explained why this is a single most required feature here. This feature along with nearly identical tally interface alone will bring lots of pirated tally users into this open source system.
Multi-language support
Supporting multiple languages is not a fancy feature anymore and especially to a country where 90% of population doesn't speak English. It should be a mandatory for any application targeted to this market. This feature will make sure this open source system reaches the un reached mass market.
No vendor lock-in
There will be no vendor lock because of its open source nature. Any software distributor with sufficient technical and functional knowledge can customize and resell this system.
What this means to Independent software vendors
Forget about fighting with tally or NX. It is about services (or customization), not products. Make profit by providing services. Services market will be bigger than products market.
What this means to Software developers/Students
This will be the biggest opportunity to learn programming and easiest way to show your skills to potential employers.
This open source system should be developed as a set of components. Each and every function/feature of this application should be exposed as a web service. These set of components/methods should be accessible by SOAP,REST and Programming languages based APIs. By this way, integration, customization and extending the system is lot easy.
Breaking User interface lock-in
As I noted previously, user interface lock-in of existing systems like tally keeps the users. This kind of well defined set of components allows us to develop multiple interfaces. Any company can build a new interface, an Interface nearly identical to tally with same set of screens and short-cut keys will be the best starting point. By this interface tally-savvy users/accountants have no reason to stick with their pirated tally. Learning curve for data entry operators and switching cost for companies are almost zero.
Plug-ins
This modular architecture should support plug-ins. Plug-ins are optional components that can be replaced at will, either at run time, configuration time or at development time. For example when users want to add new features like sending SMS from the accounting software, they can write a new plug-in and attach to this core system.
Plug-ins are like extensions to the core systems and can be used as adapters to connect other systems like inventory. Without even touching any core part of this system it should able easy to write plug-ins. Like reading data from a third party application or from a Excel sheet or calendar system.
Data import/export API
I have already explained why this is a single most required feature here. This feature along with nearly identical tally interface alone will bring lots of pirated tally users into this open source system.
Multi-language support
Supporting multiple languages is not a fancy feature anymore and especially to a country where 90% of population doesn't speak English. It should be a mandatory for any application targeted to this market. This feature will make sure this open source system reaches the un reached mass market.
No vendor lock-in
There will be no vendor lock because of its open source nature. Any software distributor with sufficient technical and functional knowledge can customize and resell this system.
What this means to Independent software vendors
Forget about fighting with tally or NX. It is about services (or customization), not products. Make profit by providing services. Services market will be bigger than products market.
What this means to Software developers/Students
This will be the biggest opportunity to learn programming and easiest way to show your skills to potential employers.
Tuesday, March 15, 2005
Firefox in trouble
A post by Mike Griffin in theserverside.net pointing to this article from eweek
From the Comments:
At first the thrill of a new project and the recognition that goes with it carries you through those tiresome evenings. You are creating something new and there are no bean-counters around to mess everything up. However, as time goes on, as with most things, the thrill begins to wax and wane, and after months of getting no more than 4 hours of sleep per night it begins to affect your health. You get sick more often than you used to, and you're main goal quickly becomes to merely get through each day. And then there's the guilt of spending too much time on it, when the basement needs painting, things need fixed around the house, and you're not spending enough quality time with your kids (and when you do you're the walking dead so it doesn't count). Finally, and much to your surprise, the project doesn't really turn out to be the big career booster you thought it was going to be. In fact, perspective employers are hesitant to hire you when they find out you have a mistress on the side pulling at your time and resources.
Comment #2
For an open-source project to remain successful long-term, it needs a strong developer community. "A project with a truck number of two is in deep trouble."
From the Comments:
At first the thrill of a new project and the recognition that goes with it carries you through those tiresome evenings. You are creating something new and there are no bean-counters around to mess everything up. However, as time goes on, as with most things, the thrill begins to wax and wane, and after months of getting no more than 4 hours of sleep per night it begins to affect your health. You get sick more often than you used to, and you're main goal quickly becomes to merely get through each day. And then there's the guilt of spending too much time on it, when the basement needs painting, things need fixed around the house, and you're not spending enough quality time with your kids (and when you do you're the walking dead so it doesn't count). Finally, and much to your surprise, the project doesn't really turn out to be the big career booster you thought it was going to be. In fact, perspective employers are hesitant to hire you when they find out you have a mistress on the side pulling at your time and resources.
Comment #2
For an open-source project to remain successful long-term, it needs a strong developer community. "A project with a truck number of two is in deep trouble."
Subscribe to:
Posts (Atom)