The rise of SaaS products created the need for integration platforms. Let's look at what iPaaS is, and why this exploding market doesn't serve software companies.
Integrating your software product with additional systems your customers use can be difficult. Here's when you should consider leveraging an integration platform.
Instead of placing sensitive resources in public subnets, use AWS Systems Manager to securely access private resources from anywhere - and restrict who gets into production databases.
Processing binary files in integrations is straightforward with a bit of code. In this example, we'll walk through triggering a webhook and processing an image with one of the many Javascript libraries available for image manipulation.
Thinking about GraphQL vs REST? We'll dig into our choice and look at why GraphQL is faster than REST when it comes to both performance and dev productivity.
Creating a logging framework is a Twelve-Factor App best-practice. Here's how logging works with integrations using Prismatic's built-in logging framework, and how you can use it to trigger alerts for your team.
It's important to keep tabs on your customers' integrations and respond quickly if something goes wrong. Let's explore using Prismatic to send integration alerts via email, text, or through your existing systems like PagerDuty or Slack.
It's important to be able to write an integration once, and deploy it to multiple customers who have unique credentials. Let's look at storing customer credentials in Prismatic, and how to tie credentials to instances of integrations.
Integration development usually requires authentication against third-party applications, which can be a tough problem. Prismatic abstracts much of the work surrounding auth and credential management. Let's look at handling credentials in a custom component.
