Day: December 19, 2018

In case you missed it, Sensu Go is here! And, as I wrote previously, one of the hurdles with migrating workloads from the original version of Sensu to Sensu Go are the changes in the internal event data structure. The existing handlers and mutators in the community maintained Sensu Plugins collection might not work as expected in Sensu Go because of these event data model changes. But friends, I’m here to tell you that we’ve got this problem licked.

The new 3.0.0 release of the sensu-plugin gem has opt-in logic to help you transition workloads using existing Ruby mutators and handlers from the Sensu Community Plugins collection. Once the community plugins you rely on are updated to require the 3.0 sensu-plugin gem, you’ll have a much easier time migrating your existing workflows without having to write your own mutator for event data. This post marks the first in a series in which I help folks migrate their workloads to Sensu Go. https://goo.gl/cftWdN

Web services are a standard when it comes to the design and development of API interfaces between enterprise software applications, which is why there are several web service testing tools that provide the testers with the ability to design and execute software tests. In this article, we present 5 tools to test web services, specifically SoapUI, JMeter, Postman, SoapSonar, and Wizdler. These tools provide various capabilities to cover all types of web service tests that can be performed, such as functional tests, service simulation (Mocking), security evaluation, and load and performance tests.

SoapUI

SoapUI is one of the tools to test web services, which allows you to design web services tests of SOA and REST architectures. You have been on the market since 2005. With SoapUI, you can try web services in the SOAP, REST, JMS, and AMF protocols, and you can also make HTTP(S) calls for web applications and JDBC for databases. It has a free version and a professional version (the latter has a cost). https://goo.gl/iQqf8a

#ICYDK: Europe keeps influencing data privacy around the world. First, there was GDPR, and now we have PSD2, which is the new phase of Europe’s Payment Services Directive. And as with any new compliance, there’s a lot of confusion about what it does, what you have to do and what it all means. You can basically sum it up like this: PSD2 forces banks to make data available. To be honest, that sentence is a bit tricky because of two words: banks and data. There are a lot of definitions of “banks,” but let’s assume we mean companies who hold onto your money and provide access via services like checking, credit/debit cards, and online banking.

Data is even trickier as there are basically three kinds of data PSD2 is forcing banks to expose. https://goo.gl/bz13nC