OPSWAT uses NetSuite as its CRM and ERP system. Our engineering team has been integrating with NetSuite through its various APIs, to transfer information in and out of the system. As our product family offering has grown, we have needed to constantly maintain and update this information flow by updating the NetSuite scripts. This process has been prone to human error and very challenging to debug as deep NetSuite knowledge is needed in order to trace down sources of issues. Faced with these issues, our engineering team began looking for a solution to externalize the logic for the routing of information from within the NetSuite scripts. In addition, we wanted to make sure that we had tight coupling between our systems, so that if a particular system is unavailable, we would still be able to update records in NetSuite without compromising data consistency.
If you pay attention to Amazon Web Services (AWS), you may have seen an announcement about a year ago that hosting would soon be available in China (Beijing). And if you’ve looked into it, you no doubt noticed that it’s not truly part of AWS – it’s actually a separate company (a joint venture) and requires a separate account. While many of the services are the same, they lack much of the seamless integration with the broader AWS ecosphere.
Until now, most average Amazon (AWS) users could effectively ignore the distinction between paravirtual instances (PV) and hardware assisted virtual instances (HVM). HVM was a technology reserved for high performance, large-capacity use cases. EG: 10Gbe LAN connection, >64 GB RAM, etc. But with changes being made in AWS, all users can and should be considering HVM for their instances.