It’s fairly common to want to have a server running a process, be it a website, a calculation, or anything else you can imagine. Often outside of the device’s core functionality though, there are many other things you may be interested in. Information on if the process is still running, what server(s) are running, what errors are occurring in the process, and general information being available externally are common examples of this.
DevOps engineers working on fast-scaling software architectures that include Ably now have it a bit easier with Control API. This new feature allows you to increase your testing capability and to configure complex production systems quickly and safely, directly from your configuration and orchestration tools.
At Ably, we run a large scale production infrastructure that powers our customers’ real-time messaging applications around the world. Like in most tech companies, this infrastructure is largely software-based; also like in most tech companies, much of that software is deployed and runs in Docker containers.
Web Components are a great way to build reusable functionality you can use in different web pages and web apps. Imagine sharing components between different frameworks like React, Vue.js, or Next.js! In this post, we delve into Web Components and show you how to build a chat web component with Ably to use it in an application built with AWS Amplify and AWS Lambda.
New investment to fuel continued growth, as Ably is projected to power synchronized digital experiences in realtime for one billion devices per month by 2023.
Today I’m absolutely thrilled to announce Ably’s $70M Series B co-led by Insight Partners and Dawn Capital LLP. We’ve grown immensely since I shared details of Ably’s Series A funding in 2020. Back then we reached 50 million devices per month. Our mission is to become the definitive infrastructure of the internet, so we set ourselves the goal of reaching one billion devices by 2025, which felt like an insurmountable challenge at the time.
The fallacies of distributed computing are a list of 8 statements describing false assumptions that architects and developers involved with distributed systems might make (but should undoubtedly steer away from). In this blog post, we’ll look at what these fallacies are, how they came to be, and how to navigate them in order to engineer dependable distributed systems.
A common problem that our customers have is event streaming spikey traffic to their clients. For example, imagine a server which needs to stream details on cryptocurrency trades. The quantity of trades happening each second is likely to fluctuate, sometimes nothing could happen, other times perhaps thousands. In order to ensure reliable communication, it’s important that rate limits are in place on how many messages are to be sent to subscribed clients.
Webhooks are the easiest way to integrate your various business applications, but they can create challenges and complexity when you are scaling. If you’re an Ably user, you don’t have to worry about this. What’s more, with ‘Incoming Webhooks’ it is now easier than ever to receive messages from a 3rd party integration, with no risk of bottlenecks when you’re rapidly scaling.
