Our team has built numerous enterprise scale APIs capable of supporting millions of requests daily to thousands of consumers.
We utilize the latest in web API technologies, such as edge functions, serverless architectures, API gateways, etc., in your language or framework of choice to improve developer efficacy, application performance, and application stability.
REST vs GraphQL vs gRPC
All these options solve the same problem of allowing client applications and servers to communicate. When working with teams, we work to understand the use cases to create best practice solutions that will last. REST is ubiquitous and well supported but has some limitations. GraphQL and gRPC both solve some of these limitations in their own unique ways but require additional configuration and training to get started.
API Gateways
Regardless of the protocol selected or whether microservices or monolithic applications are involved, we always recommend configuring services behind an API gateway.
An API gateway validates incoming requests, handles routing them to the appropriate service, and responds to the client with response. This allows teams to utilize any infrastructure architecture to build their services while implementing a single interface for client teams looking to integrate with those services. This assists in development velocity, avoids application fragility caused by explicit resource naming, and allows for better service access security policies.
Hosted vs Serverless Solutions
Our team utilizes both hosted solutions like NestJS and distributed solutions like the Serverless Framework to create backend services. We analyze traffic, performance, technology, and budgetary constraints to help identify the ideal solution for an organization. Our goal is to help deliver best-in-class data solutions that meet product needs.
Hosted solutions are typically easier to develop and optimize for performance but come with scaling challenges in later stage organizations. Serverless solutions yield high performance and solve the scaling challenges but can be challenging to develop and fine tune due to the lack of centralized logic. Our architects will help identify the best course of action based on an organization’s long term needs and will find a balance between these options that yield the ideal result.
1. Tell us about the technology you use to build APIs supporting your front-end applications.
2. What type of database do you use to normally support your applications?
3. Have you used an API gateway for your APIs? If yes, what purpose has the API gateway played in your application?