March was a big month for releases with Solace. Not only is there big API news for developers, but the release of PubSub+ Broker version 9.13.1 brought along some great features to make administrators lives easier when setting up connections to external services.
Sign up to Solace Academy to get access to our Monthly Feature Highlight Training and read on to learn about the features you’ll be learning to implement in the April training.
The New Solace Go API
The developer landscape is vast, with new technology being used every day. At Solace we’re constantly evaluating what languages our customers are using and it became apparent to that a Go API was needed.
What is Go?
Go is a compiled programming language built by Google that was originally developed in 2007 and announced in 2009, with version 1 being released in 2012. But why was another language created? When Go was first thought up, there were a multitude of different languages in use at Google, each with their own advantages and drawbacks. The designers wanted to develop a language that addressed the issues of existing languages, while keeping the good features, such as:
-
The static typing and run-time efficiency of C;
-
Readability and usability like JavaScript;
-
High-performance networking and multi-processing;
-
Memory safety, garbage collection and concurrency; and
-
Open-source.
Why develop a Go API for Solace?
PubSub+ Platform is built with well-developed and widely used technologies and standards. This allows Solace to be used by virtually any language developed. While these technologies and standards are widely used, that doesn’t necessarily make them easy to develop with. For example, Websocket is a widely used technology for communication, but there are many components that need to be developed, like authentication, message format and structure, error handling, etc.
More and more of our customers are using Go for their development environment, and while using Solace with Go has always been technically possible, there was a lot of development work that would need to be done. There have been some individual efforts made but some amazing developers in our community, but one of the things our customers have been looking for is a solution supported by Solace. With all of this in mind, the new Solace Go API was born!
What will I learn in training?
In the April 2022 Monthly Feature Highlight training you will learn how to set up the sample project for the new Go API and we will give an overview of some of the code that is run with the sample.
You may also be interested in…
The New Solace Connectors for Azure Data Lake Gen 2 and Google Cloud Storage
Solace PubSub+ Broker version 9.11 was an important milestone for supporting cloud storage like Azure Data Lake Gen 2 and Google Cloud Storage. Certain HTTP headers were needed in order to properly send data to these services with REST Delivery Points (RDP) and with with custom HTTP headers implemented in v9.11 customers can finally accomplish this.
The release of Solace PubSub+ Broker version 9.13.1 was another leap forward in helping customers connect to both Azure Data Lake Gen 2 and Google Cloud Storage. Now instead of having to set up these headers and other values manually, a click-to-create solution is available in the Connectors tab, making RDP setup for these services fast and easy.
The old…
Solace PubSub+ Broker version 9.11 made connecting to Google Cloud Storage and Azure Data Lake Gen 2 possible by implementing custom HTTP headers and variable targets in REST Delivery Points (RDP). With these features customers now had everything they needed to pass the correct information to these services and get their data stored.
Unfortunately this still required quite a bit of setup. Customers needed to:
-
Create a queue for and RDP to subscribe to
-
Create an RDP, RDP Consumer and RDP Queue Binding
-
ensure OAuth 2.0 authentication was set up for Azure or OpenID Connect for Google, and
-
make sure the correct custom HTTP headers and variable targets were set
…and the New
Solace PubSub+ version 9.13.1 now has new step by step processes for creating and RDP for both Azure Data Lake Storage Gen2 and Google Cloud Storage. Now, instead of a customer having to know what headers to set and what values to enter in them and having to set up all the information needed for an RDP, they can simply go into the Connectors tab in the Broker Manager and walk through the simple 5 step process to have all the RDP information set up by the Broker itself.
What will I learn in training?
In the April 2022 Monthly Feature Highlight training you will learn how to use the new connector process for creating an RDP connection to a Storage Bucket in Google Cloud Storage.
Explore other posts from categories: For Developers | Products & Technology