Database schema migration is often an intimidating concept for many software engineers. In an ideal world, developers start with the perfect database schema that can scale to handle millions of requests to their service. But there can be times where you pick the wrong datastore or a data model that you need to change after your product is in the hands of customers.
Our engineering team at MuleSoft faced this challenge last year.
This blog is the fourth and final part in a 4-part series on how to use a Slack bot to extract LaunchDarkly data. If you haven’t already, check out part one, part two, and part three of the series before pursuing the final steps of this demo.
This demo demonstrates how to use Anypoint Design Center’s flow designer to extract LaunchDarkly data (feature flags) using a Slack bot. The purpose of this demo is to provide a quick and efficient method to retrieve user profiles, including permissions. If you haven’t already, please check out part 1 of this blog series before moving on to part two.
In part two of the demo, we will create an API specification in API designer using the LD API,
In every software development process, there is always a need to test features and products before releasing them. This process can often be manual and requires providing specific users with permissions by ensuring that each user has the right security and governance. This process can become complex quickly, especially if you have a lot of users to manage and many features to flag.
One of main use cases with Salesforce that MuleSoft customers use involves uploading records that are stored in CSV format to Salesforce. MuleSoft has provided various ways to fulfill this use case. We have dataloader.io, the most popular Data Loader for Salesforce on Salesforce AppExchange, and also have Anypoint Platform’s Salesforce Connector with various operations.
We added another option to help you easily accomplish the above use case.
API response time is essential to providing the frictionless end-user experiences necessary for you to meet your API program’s KPIs and retention goals. One way to optimize performance is by having a caching layer in your API architecture. This layer allows you to deliver cached responses for common requests––thereby accessing data in a quick and inexpensive manner.
With the decentralization of IT and the adoption of APIs and microservices, enterprises are struggling to keep up with an accurate view of deployed APIs and their dependencies. This lack of visibility often translates into quality issues––whether it is failed deployments, lengthy processes for identifying and diagnosing of production issues, increased technical debt, or less reuse of available assets.
A somewhat “hidden feature” of the Mule Maven Plugin is the ability to use stored encrypted Anypoint user credentials in deployments. Normally, when deploying an application using a deployment strategy, the user either sets plain text credentials in the application’s POM, or injects them into the plugin configuration through the command line, or sets them through a property.
Governance, visibility, and control are the trifecta requirements for software management. With digital landscapes comprised of APIs, integrations, applications, hardware devices, on-premises systems, and SaaS tools, the companies with the most accurate pulse on their digital landscapes are the ones setting economic and digital trends.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.