Solution Architect skilled in Salesforce, NetSuite and JavaScript Development
A cheat sheet covering RESTful concepts for design and development.
The cheatsheet is one page and covers versioning, designing consistent URIs, HTTP methods, HTTP status codes, error handling and authentication/authorization.
REST APIs function primarily through the use of resources that are located at a certain URI.
Versioning is one of the most critical parts of API design. Versioning allows us to potentially make breaking changes at some point in the future.
The goal of caching is to avoid having to generate the same response twice.
In this blog article we look at five techniques for caching in a RESTful api.
A REST API is a type of API that confirms to the RESTful constraints. REST is designed to take advantage of existing protocols like HTTP.
HTTP Status Codes and HTTP Methods are the building blocks of building a good RESTful API.
REST or REpresentational State Transfer is an API architecture style that uses a uniform interface.
For an API to be RESTful there are six rules that it needs to follow.
Slow WordPress websites can be difficult to improve especially if we don’t have a plan on how to resolve the problem. I have a list of five recommendations that I always look at doing when trying to resolve speed issues.
Documenting a Salesforce Org is really challenging because it can be complex especially when working across many different branches or divisions. Maintaining and keeping the documentation in sync is also really difficult if there isn’t significant executive sponsorship.
In this blog article, we’ll be focused in on the Analytics API because it’s primarily used for reporting and dashboards.
I know that when I am working in JavaScript, I prefer to keep everything to using promises or async/await instead of occasionally using callbacks because a library doesn’t support them.
There are a number of different JavaScript modules or libraries that are available on npm to connect to the different REST based Salesforce APIs.
In this post, I show my favourite library.
An API gateway is essential part of organizing requests that need to be processed by different microservices.
When looking at patterns it’s important to understand what tradeoffs are being made.
AWS Lambda allows us to dramatically lower our costs for running an application. It’s fairly easy to convert an Express.js app into running in the serverless framework.
Integration middleware is software that is used to fill the gaps between applications and databases. That means it allows remote systems to communicate with one another and even do transformations between systems.
Integrations allow businesses to potentially save a lot of money by reducing duplicate data entry, reducing licensing costs, and allowing systems to interact end to end.
APIs come in many different styles and types. Before running into a style we need to understand the different options and the trade offs that we are making.
I was recently working on a serverless api that uses serverless offline, express.js and mongodb.
We started getting emails from MongoDB Atlas telling us that we ran out of connections.
There are quite a few different reasons to consider using serverless instead of looking at building a monolith or building services in containers.
The Serverless Framework allows us to abstract away quite a bit of the complexity from setting up lambda functions and the necessary events to execute them, especially through the API gateway.
In this blog post we look at how to set up a simple project to use the serverless framework.