I currently have a requirement for a highly available multiple region message bus with at-least-once delivery to Azure Functions. The usual way of doing this would be to use Service Bus with active replication. In other words, you set up queues/topics in two regions and clients send two copies of each message, one to each region. The receivers then read messages from both regions and keep a log of messages already received to avoid duplicate processing.
Following up from the NIDC launch event on Friday night, it seems there’s some confusion about what sort of talks we’re looking for and what should go in the talk synopsis when you’re submitting. In particular, some people are deciding not to submit talks on the (incorrect) assumption that theythey’re technical enough, or just because they don’t know what to fill in on the submission form. So here’s my take on it.
If you’re going to #HackTheHub this weekend, you’re probably considering using cloud AI/ML services to get a bit of a head start. Azure of course has a whole heap of services for Artifical Intelligence, Machine Learning and bots, and a pretty generous free plan to get you started. However, if your plans are grand enough that the free plan might not cover your needs, just get in touch with me via the #HackTheHub Slack (or find me on the day) and I’ll kit you out with enough extra free processing to get you through the weekend.
So you become an MVP, so you need to get listed in places, so you need a website, so you need a blog, so you need a blog post. This is that blog post. Will future blog posts be more enlightening? There’s only one way to find out …