How many APIs exist inside your organization? Dozens? Hundreds? How are you keeping track of access, security, and policies on those APIs? Are you getting consistent alerts if any of those services go down? If you are trying to manually manage each of those individually, you may wish to consider using an API management solution. API management is a critical component to your suite of integration capabilities which allows you to centrally monitor, secure, and deploy your organizations API connectivity and is essential to reliably ensure maintain, monitor, and secure your APIs. Learn more in this post on how to work with Flex Gateway and Docker.
Wow, it’s good to be back. What an event. After two years without any in-person activities, it was a surreal experience to say the least. Salesforce did an excellent job getting folks in and out of the venue, and making the whole event as well-run as we’ve all come to expect from them. The keynotes, sessions, and the concert experience (Weezer) were all very memorable, and they covered a ton of ground. There were a few stand-out items for me that I took particular note of and I’d like to discuss them here.
In 2016, Salesforce acquired a company known as Demandware, and re-branded their solution as Salesforce Commerce Cloud. Later, in 2018, Salesforce acquired a company known as CloudCraze, and that later became known as Salesforce B2B Commerce, and the original Demandware acquisition became known as B2C Commerce. One key difference between these two solutions is that the B2B Commerce product runs “on platform”, and the B2C (Demandware) product does not.
If you’ve been a developer for any length of time, you’ve been tasked with connecting data from system A to system B. It could be data from your ERP to your Ecommerce web store, or it might be from your CRM to your Marketing tools. These ‘point to point’ integrations work well when a business is in it’s infancy along the path of digital transformation. Unfortunately, as the number of point to point integrations grows, so does the complexity of trying to maintain those systems. They become so fragile, and so unstable, that the entire IT team is afraid to touch them let alone replace them (which would feel like a herculean task). In addition, dev teams outside of central IT are slowed down because central IT is spending all of their time maintaining and keeping those systems working and online. What if there was a better way?
We’re going to review how to work around the frequent and ever present error: String or binary data would be truncated. The statement has been terminated.
Do you ever develop prototypes, or starter projects/accelerators, that you’d like to use again in the future? A good way to do that is by creating custom templates for dotnet. Once completed, anytime you want to create a new project of that type in the future, you can use key in “dotnet new ” and you’re off, complete with correct namespaces. You can even do conditional checks, or variable replacements.
REST services are everywhere. It’s tough to find an application that doesn’t leverage an externally hosted REST service in some way. Prior to .NET Core 2.1, a common library that was used to perform REST requests was RestSharp. I love RestSharp, but let’s explore the new alternative IHttpClientFactory that became available as part of .NET Core 2.1.
This post will walk you through the steps necessary to add a strongly typed appsettings.json configuration file to your console application. I’ll dispense with the formalities of writing a detailed introduction on why you would be interested in doing this and jump right into the steps involved.
Front-end frameworks like React, Angular, and Vue are making big waves in software development. Microsoft makes great tooling for working with JS frameworks like those in the form of Visual Studio Code. There is also a large trove of information and tutorials getting setup inside the VS Code environment. One specific resource I really appreciated was Cory House’s Pluralsight course on setting up a JS development environment.
Here is a common scenario for you. You’re building an application… any application. It could be your side project, a sales tool, an ecommerce site, a REST api, a video game, a reporting dashboard. Anything. You’re building your app, and you reach a point that you’d like to try it out, to see how it would look to a user. How do you simulate a production scenario with no data to test with? If you’re lucky, you have data from an existing customer you can use, or there is a sample dataset available online. If you’re unlucky, you’re left generating dummy data using garbage inputs (random strings, random numbers, etc) – data that passes the regex, but doesn’t provide a good simulation.