Author: admin

It is always telling when folks assume I mean REST when I say API. While the web dominates my definition of API, and REST is definitely a leading architectural style, these assumptions always define the people who bring them to the table, more than they ever do me. I’m in the business of studying how people are applying programmatic interfaces using the web. To reflect my research I’ve been evolving a diagram of my toolbox that I’ve been publishing as part of workshops, presentations, and some talks I’m preparing for 2018. It reflects what I’m seeing as the evolving API toolbox that I’m seeing companies working with, and a diversity in which I’m encouraging others to think about more, as we choose to ignore the polarizing forces in the API sector.

To set the tone for any API conversation I am participating in, I prefer to introduce the concept of the API toolbox including more tools than just REST, acknowledging that there are a growing number of tools in our API infrastructure toolbox which can be applied to different APIs, to solve a variety of problems and challenges we face. Also, we need to be more honest about the fact that there are many legacy solutions still in use across large organizations, even as we consider adopting the latest in leading-edge approaches to API deployment in newer projects. https://goo.gl/jBd5hw #DataIntegration #ML

ICYMI: Part I – OAuth2 in a Nutshell

OAuth2 is a framework, defined here. It’s not a protocol, because the RFC doesn’t contain enough implementation specifics. I say this with the understanding that the line between protocol and framework is a blurry one…

The RFC first defines four roles: https://goo.gl/QqHQTt #DataIntegration #ML

ICYDK: NetSuite offers stellar Software as a Service (SaaS) products for accounting, operations, cloud relationship management (CRM), and eCommerce. It enables interdepartmental coordination by uniting accounting, sales, and support with on a single interface. However, teams face difficulties when the cloud-based solution needs to be connected with Enterprise Resource Planning (ERP), CRM or other e-commerce applications. There are so many features to extend the NetSuite functionalities yet users face several issues while integrating it with third-party applications.The application is cloud-based with a differentiated architecture and teams face challenges while integrating it with on-premise legacy applications. Overcoming hybrid world challenges with the archaic coding approach is difficult.

The point-to-point approach requires heavy coding and it is strategically unwise to execute Netsuite API  integration with the help of this approach. As a lot of IT staff are required to brute coding and integrate NetSuite with other systems in an enterprise. Let’s imagine an IT ecosystem where there are thousands and thousands of applications. These applications cannot be integrated with a single NetSuite integration flow. https://goo.gl/C2hNRf #DataIntegration #ML

First, we need to download Tomcat (https://tomcat.apache.org/download-70.cgi).

I downloaded the Core .zip file. https://goo.gl/6n8sSt #DataIntegration #ML