Lambda is a top-rated compute service available on the AWS cloud service network. Its popularity largely derives from its ease of use, allowing users to run Lambda functions reliably without provisioning or managing servers. Lambda can be triggered manually or by any linked events in the AWS network, including DynamoDB streams, SQS, Kinesis, and more.

With the emergence of the hybrid solutions, solutions such as BizTalk Server that were purely on-premises solutions are communicating with SaaS solutions and are being deployed in a hybrid model. There are many advantages to cloud integration. Organizations can take advantage of powerful features of the Azure Platform and other cloud-based services from Microsoft, such as Service Bus, Logic Apps, Power BI, and Event Hub.

I recently published a post regarding BizTalk Schema Validation: DateTime Restrictions on my personal blog. Still, I was curious to see if we have the same capability in Logic Apps Standard and Consumption. And by doing that, see how compatible these two technologies are regarding XML Schemas and validations.

The Simple Notification Service, or SNS for short, is one of the central services to build serverless architectures in the AWS cloud. SNS itself is a serverless messaging service that can distribute massive numbers of messages to different recipients. These include mobile end-user devices, like smartphones and tablets, but also other services inside the AWS ecosystem. SNS’ ability to target AWS services makes it the perfect companion for AWS Lambda.

There are such cloud services that can drastically accelerate your innovation and reduce your time to market by providing you with functionalities that are simple, ready-to-use and that allow you to add a real added-value to your users. Azure Communication Services is one of those. In this article, we’ll have an overview of what Azure Communication Services (“ACS” for short) is, what functionalities it provides and what are some of the use cases in which it can be leveraged.

Azure SQL Database is at the heart of many applications running on Azure. Whether a company is migrating its on-premises applications to Azure or designing a new application from scratch, there are high chances of Azure SQL Database being considered and used.

Many organizations leverage AWS to build fully managed, event-driven applications, which break down complex workloads into APIs, event streams, and other decentralized services in order to improve performance and scalability. This type of architecture relies primarily on AWS Lambda functions to process synchronous and asynchronous requests as they move between a workload’s resources, such as Amazon API Gateway and Amazon Kinesis.

App registrations is a mechanism in Azure AD allowing to work with an application and its permissions. It’s an object in Azure AD that represents the application, its redirect URI (where to redirect users after they have signed in), its logout URL (where to redirect users after they’ve signed out), API access and custom application roles for managing permissions to users and apps.

One of the first questions you must ask yourself when deciding to construct an application in the cloud is whether your application will be built utilizing serverless or fully managed services. To begin, let me state that these are extremely loosely defined concepts and that there may be cloud services that fall somewhere in the middle, as well as others that are both serverless and fully managed services at the same time.

Over the years, containerization has grown in popularity among organizations and will continue to grow. For example, containerization is slowly becoming the de facto approach when it comes to building applications following the microservices architecture. It is undeniable that containerization has a lot of advantages, but these advantages come at a cost.

In this article, we’ll deep dive into all the basics to help you decide if AWS RDS is the right decision for your architecture and help you hit the ground running if you do end up AWS RDS. For many decades now, relational databases (RDS) have been the place to store your data. They are pretty flexible often use some kind of SQL dialect, which is one of the main languages taught in computer science classes, and widely understood by the average developer.

One of the most notable advantages of the Cloud is the ability to scale resources to meet demand. We then scale out or up when the demand increases, and we scale in or down when the demand decreases. For the record, scaling out / in refers to increasing or decreasing the number of instances of a given resource, whereas scaling up / down refers to increasing or decreasing the capacity (CPU, Ram, Disk, I/O performance) or a given instance.

Jay V is one of the founders of Serverless Stack (SST), an open-source framework that makes it easy to build serverless apps. He spends his time trying to figure out what the future of the cloud will look like. And liking memes on Twitter.

Recently we launched features to provide support for Log Analytics in Serverless360. Log Analytics workspaces are used by a lot of different features within the Azure Monitor stack and by providing the ability to link a Log Analytics Workspace to a Business Application in Serverless360 we see that it provides a way you can allow a support user the ability to view and run queries against your log data without needing to be an Azure Expert.

The year 2021 has ended, and we are now entering 2022. Last year, Microsoft released a few new Azure services and updated others. This blog post will discuss the most exciting cloud integration-related updates and releases.