We have an ambitious project and I'm looking for some good resources. In a nutshell, we would like to design a completely custom PHP driven web site and seamlessly integrate it with NS. The goal would be to still enter product data, inventory, etc., in NS, and have the PHP web site display the NS products. The PHP site would need to be able to pull not only product info from NS for display purposes, but also pull customer info, previous order history, etc..
I've read through some of the NS User Guide, specifically the SuiteTalkWebServicesPlatformGuide.pdf, and I understand the basics of how to do a soap call to retrieve records from NS, and how to insert new records. I also see that there is some sample PHP code. I haven't spent much time looking at the specifics of what records there are, and what records we would need to pull/push.
What I would love to hear, before we embark on this, is feedback from others who have attempted the same thing. Was it successful? And would you be willing to share what the major pitfalls and/or limitations were?
Here are a few things I'm interested in:
1) Speed. If we need to query the NS database to retrieve product records to display them on our PHP site, then we need the servers to respond really quickly and reliably. How speedy/reliable do the servers seem?
2) Request limiting and Record limiting. I read the section on request/record limiting, but I don't really have a sense of how this will affect us, because I don't yet know how many requests our server would have to make, and whether those would be "long" or "short" requests, to display the products on our PHP site. Any info here would be greatly appreciated.
3) Replication/caching? This relates to my question above. Perhaps if NS limits the number of requests you can make, the better strategy would be to replicate the data from NS by doing off-peak-hour long requests and replicating or caching the data on a different server, maybe in a MySQL database. So basically this would mean grabbing all of the NS product data once a day, storing it locally, and then generating our PHP web site based on the local data. Is this a strategy used by anyone?
4) Custom fields. Let's say that we want to add some additional fields to our web site, fields that are not included in NS. For example, let's say we want to add "favorite color" to our users' profiles. I don't know enough about NS to know if you can add a field in NS for favorite color, and then do a SOAP call to retrieve that record (seems like the cleanest approach) or if we'd have to save that data elsewhere (MySQL database) and then join that with the returned record from our SOAP call.
5) Show stoppers? This is my most important question. Are there any limitations to the Web Services API that were show stoppers for you? Our goal is to make a better web experience that we can make with the packaged NS web site but if there are any big limitations then we'd love to know about them now.
6) Examples? Can anyone show us the URL of a web site that does basically what I'm describing? It would be best if it were done in PHP, but if not, we'd still like to talk a look. Or if there are informative threads on this board, and you'd like to respond by pointing me toward those threads, that would be helpful, too.
Thanks again for any help.