Category: API Design
-
Serverless AWS REST API Design Options
Designing and implementing an API in AWS Serverless Application model you use: AWS API Gateway for routing, validation =, and authorization of the API Calls to the AWS Lambda implementation AWS Cognito for authentication, basically implementing OAuth 2.0 client grant flow Parameter Store and AWS KMS to store configurations and connection strings in a secure…
-
MuleSoft: AnyPoint Exchange Generated Connector
What is AnyPoint Exchange Generated Connector: AnyPoint Exchange has many custom connectors that are professionally developed. However, for any API specifications (RAML or OpenAPI) that you publish to AnyPoint Exchange, it generates a Mule( 4 or 4) connector. You can download the connector from AnyPoint Exchange or directly form AnyPoint Studio. The connector simplifies many…
-
API Delivery Technology Capabilities
I have been working with an organization to expose its services and capabilities as a set of APIs on AWS Cloud. To be able to do so, I believe an organization got to have a minimum set of API Technology Delivery capabilities. I will provide a brief description of the capabilities that I helped develop:…
-
GraphQL API with Node.js Sample
Introduction In this sample, I am exploring building an API with Node.js and GraphQL. For a long time, I have been building APIs in SOAP and REST usually with either in code like C#/ASP.Net, Java/ Spring or ESB platforms like BizTalk and MuleSoft (AnyPoint Platform). Node.js has been gaining a lot of popularity with many…
-
Implement Rest API in MuleSoft, Azure Logic Apps, Asp.Net core or Spring-Boot? MuleSoft: Step1- Defining an API in RAML
I have been working lately on comparing on comparing different technologies to build web API’s.. One of the main concerns was if we wanted to build a simple API service which technology would be easier, more productive to develop the service with. To provide a reference comparison I will build the same web service (in…
-
Practical REST API Design, implementation and Richardson Maturity Model
Richardson Maturity Model classifies REST API maturity as follows Level Zero: These services have a single URI and use a single HTTP method (typically POST). For example, most Web Services (WS-*)-based services use a single URI to identify an endpoint, and HTTP POST to transfer SOAP-based payloads, effectively ignoring the rest of the HTTP verbs.…
Genetic Thought Software Inc. 