Skip to main content

Service Bus Topic - Different ways to create and manage it

In the last post, we saw how easily we can integrate Service Bus Topic with WCF. Today topic is simple. There are times when we need to create topics and subscriptions that are valid for one day or two. Not only this, this task can sometimes be done by various persons of applications. Let’s see what our options are.
Of course the most powerful tool is the code. From code we can create topics, subscriptions and configure them in any way we want. When we create a topic we can set the default TTL value of messages that will be send to the topic, but we will not be able to set a property that specify the TTL of the topic (delete after 2 days for example). But, beside this we can set others values like the maximum size of the topic, enable or disable the batch operations and if the message duplication detection is activated. Similar configurations can be made to a subscription using SubscriptionDescription.
TopicDescription topicDescription = new TopicDescription()
{
RequiresDuplicateDetection = true;
}
In this moment we cannot specify from configuration file (or any kind of XML) a new topic or a new subscription or to reconfigure one of them. If we need something like this we can very easily create a small application for this purpose.
The last way to create topics and subscriptions is from Windows Azure portal. This can be created from the portal using only the mouse. All the main properties can be configures from here. We need to go the Service Bus tab. In this tab we will have buttons than give us the ability to create topics and subscriptions. The only limitation is on subscriptions, we cannot create filters and actions for them. Because of this a subscription created from the portal will receive all the messages.

Another way to create them (that I don’t enjoy) is by HTTP requests. Yes, using simple HTTP request we can create and manage Service Bus. The assembly that we use from the code to create a topic is only a wrapper over HTTP requests. Because the topic is quite complex, please find more information about this in the following link: http://msdn.microsoft.com/en-us/library/windowsazure/hh780752.aspx
We saw that we can create and manager topics in various ways. Because all the commands can be executed over HTTP/HTTPS we can create any configuration tool (and also use Service Bus) from any language and platform. This can be great when we want to integrate it in a big and old system that is written in Perl or from COBOL (that use a library like Libcurl).

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...