Looking for a programming book..
-
Hi Gang, Maybe you all might be able to help me out.... What I'm looking for are books on order management systems. Yes, I've seen the ones about ECommerce where it's a single order you are managing, but I'm looking for something about programming techniques for actually managing the orders. In this case, let's pretend you are selling widgets and every 45 days, a new widget is sent to you automagically. You don't have to do anything else. You don't have to return to a web site to process a new order, etc. Nothing I've seen so far has any techniques for handling these recurring orders, etc. on the back end. Anybody want to recommend some good books? (I have the APress (?) ones about ECommerce in C# using Studio 2005, it doesn't talk about recurring shipments at all) Thanks, Nick
This are my own opinions. You know the rest.....
-
Hi Gang, Maybe you all might be able to help me out.... What I'm looking for are books on order management systems. Yes, I've seen the ones about ECommerce where it's a single order you are managing, but I'm looking for something about programming techniques for actually managing the orders. In this case, let's pretend you are selling widgets and every 45 days, a new widget is sent to you automagically. You don't have to do anything else. You don't have to return to a web site to process a new order, etc. Nothing I've seen so far has any techniques for handling these recurring orders, etc. on the back end. Anybody want to recommend some good books? (I have the APress (?) ones about ECommerce in C# using Studio 2005, it doesn't talk about recurring shipments at all) Thanks, Nick
This are my own opinions. You know the rest.....
Scheduled events in SQL Server are routine with this kind of thing. I don't think it needs an entire book.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
Scheduled events in SQL Server are routine with this kind of thing. I don't think it needs an entire book.
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest HemingwayI don't think it needs an entire book. I'm not looking for a book on recurring orders only. But books that show different techniques of how to accomplish this. It could be a regular book on order management with a chapter or two dedicated to this topic. For example, there could be a living order record spawning off shipments and then updating the live record. Or there could be a system that prepopulates several different orders and each order directly relates to a single shipment (in this case, there isn't a shipment system running, just a related record that would have shipment details). That sort of thing.
This are my own opinions. You know the rest.....
-
Hi Gang, Maybe you all might be able to help me out.... What I'm looking for are books on order management systems. Yes, I've seen the ones about ECommerce where it's a single order you are managing, but I'm looking for something about programming techniques for actually managing the orders. In this case, let's pretend you are selling widgets and every 45 days, a new widget is sent to you automagically. You don't have to do anything else. You don't have to return to a web site to process a new order, etc. Nothing I've seen so far has any techniques for handling these recurring orders, etc. on the back end. Anybody want to recommend some good books? (I have the APress (?) ones about ECommerce in C# using Studio 2005, it doesn't talk about recurring shipments at all) Thanks, Nick
This are my own opinions. You know the rest.....
I write software that does somewhat similar stuff with recurring business processes. I doubt you'll find a book on it for programmers, perhaps a business one for inventory managemers or something. I don't know why you want one to be honest. You just need a deep and thorough understanding of the business process then write the code to accomplish it. It used to be called Systems analysis and design (at least it was when I took the course on it some decades ago) and it was at least 50% of the job of a senior software developer to be good at it. Trusting a book for this kind of stuff is very dangerous when you have the actual company or companies at hand to find out what *really* goes one which rarely relates to some hypothetical idealized version written about by some ivory tower business professor with little or no real world exeperience. Our technique for recurring business processes is two fold: a windows service that uses the business object library to do automated processing and event driven processes within the business objects themselves for cases where doing something with one business object should trigger multiple changes with other objects. At no time do we involve the sql server in anything more complex than being a data store because our app is sql platform agnostic. A lot of business software writing books for beginners tout using the sql server triggers for all manner of business processing, years of real world programming have revealed this to be dead wrong to me because you will very quickly outgrow the abilities of SQL and want programming control of a much more complex nature in the end ultimately. Plus db agnosticism is always a good thing because it's not just db maker agnosticism but also db version agnosticism giving you future proofing as well.
When everyone is a hero no one is a hero.
-
I write software that does somewhat similar stuff with recurring business processes. I doubt you'll find a book on it for programmers, perhaps a business one for inventory managemers or something. I don't know why you want one to be honest. You just need a deep and thorough understanding of the business process then write the code to accomplish it. It used to be called Systems analysis and design (at least it was when I took the course on it some decades ago) and it was at least 50% of the job of a senior software developer to be good at it. Trusting a book for this kind of stuff is very dangerous when you have the actual company or companies at hand to find out what *really* goes one which rarely relates to some hypothetical idealized version written about by some ivory tower business professor with little or no real world exeperience. Our technique for recurring business processes is two fold: a windows service that uses the business object library to do automated processing and event driven processes within the business objects themselves for cases where doing something with one business object should trigger multiple changes with other objects. At no time do we involve the sql server in anything more complex than being a data store because our app is sql platform agnostic. A lot of business software writing books for beginners tout using the sql server triggers for all manner of business processing, years of real world programming have revealed this to be dead wrong to me because you will very quickly outgrow the abilities of SQL and want programming control of a much more complex nature in the end ultimately. Plus db agnosticism is always a good thing because it's not just db maker agnosticism but also db version agnosticism giving you future proofing as well.
When everyone is a hero no one is a hero.
John C wrote:
At no time do we involve the sql server in anything more complex than being a data store because our app is sql platform agnostic. A lot of business software writing books for beginners tout using the sql server triggers for all manner of business processing, years of real world programming have revealed this to be dead wrong to me because you will very quickly outgrow the abilities of SQL and want programming control of a much more complex nature in the end ultimately.
... but ... but ... but ... MS is adding C# to SQL server SPs. :doh:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
-
John C wrote:
At no time do we involve the sql server in anything more complex than being a data store because our app is sql platform agnostic. A lot of business software writing books for beginners tout using the sql server triggers for all manner of business processing, years of real world programming have revealed this to be dead wrong to me because you will very quickly outgrow the abilities of SQL and want programming control of a much more complex nature in the end ultimately.
... but ... but ... but ... MS is adding C# to SQL server SPs. :doh:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
-
John C wrote:
At no time do we involve the sql server in anything more complex than being a data store because our app is sql platform agnostic. A lot of business software writing books for beginners tout using the sql server triggers for all manner of business processing, years of real world programming have revealed this to be dead wrong to me because you will very quickly outgrow the abilities of SQL and want programming control of a much more complex nature in the end ultimately.
... but ... but ... but ... MS is adding C# to SQL server SPs. :doh:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull
Yeah, and how many web hosting companies enable SQL CLR?
Please don't bother me... I'm hacking right now. Don't look at me like that - doesn't anybody remember what "hacking" really means? :sigh:
-
Yeah, and how many web hosting companies enable SQL CLR?
Please don't bother me... I'm hacking right now. Don't look at me like that - doesn't anybody remember what "hacking" really means? :sigh:
Don't look at me, I'm not a webdev. :-\
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull