Connections Cloud – avoiding sending massive messages

Currently, Connections Cloud, unlike other services, has no limitation in terms of number of messages sent, data replication, or downloading of messages made by IMAP.

This does not mean that misuse of these services is not controlled. There are monitoring mechanisms to prevent abuses, in a way that an unreasonable use of a service is detected, or there is an use for something that has not been designed to work that way, the account/user that is making use of the service may be suspended (as reflected on service agreements).     A clear example is the use of IMAP, as we have seen previously is not a mechanism designed for a mass of data extraction, since an indiscriminate use of it can affect the service.  Obviously, if IBM detected that is doing such use not appropriate, could stop the service to avoid affecting other clients.

In order to standardize the service, are being gradually introduced so-called mechanisms of “rate limits” or “api throttling”, which restrict the number of calls that can be made to it directly in the API. So far, only APIs for Social (connections) had those protection mechanisms (limiting calls to the API that is could make per minute), but not the mail.

The first affected service will be sending massive post, so that a user cannot send more 5000 messages per day, or not more than 500 messages in a time of 15 minutes.   They are figures that I find are very reasonable, and difficult to achieve, since Connections Cloud is not a mail to mass or transactional delivery platform (there are excellent tools for this purpose, such as Sengrid, Awever or MailChimp, or the more specific to mail with a strong component in professional marketing, the WCA – Watson Campaign Automation).

Note also that on this year roadmap, it is planned to have similar “API Throtling mechanism” for the other related services, in order to ensure the “healthy” Connections Cloud service, additional mechanisms, providing similar mechanism to the ones Google or Microsoft already have in place in its service  (ie, replica, sync, bandwith usage, etc)

Microsoft distributes fix to avoid crash of Notes in Windows 10

In recent weeks I have received complaints from several customers, which mentioned that after the latest automatic update in Windows 10 (the so-called Windows 10 Creators Update released April 11, 2017), they suffered crashes of Notes (which until then had operated normally) .  Just a couple of days ago I receive news that Microsoft has distributed a fix which solves the issue of the blue screen.

This problem was caused by a certain API calls to the Windows UI, not working correctly, because what in certain operations, arose from a crash. The problem has been resolved with the latest update from Microsoft.

I have attached a link to the update

Migration of IBM Domino-Connections Cloud (SmartCloud) to MS O365 (part I)

As employee of IBM, one of the occasions more frustrating that I usually find is when one of my clients wants to migrate from Domino or SmartCloud to one of our direct competitors, Microsoft or Google.

The reasons tend to be different.  Within them, we find also 2 different cases it is important to differentiate. On the one hand, are customers who are not yet in the cloud (and seek to modernize their infrastructure to the best option) and by another, those who already know SmartCloud (but in many cases, not all of the new features or possibilities that are being incorporated, nor the diversity of options of connection and integration).

Having a good knowledge of the product, most of the time you realize that decisions have not taken how many times all the elements, and not is rare in the background, “siren songs” of Microsoft and a false sense of simplicity/modernity in such alternative.  In general, a high percentage of these migrations are often reversed, as if you have the opportunity to explain to your customer the roadmap for the product, positioning it, and technically compare it against the competition, the customer sees it already with another perspective.  When in addition you present the problems of migration to other environments, the real costs, risks and the value it can bring such change is highly debatable, approach tends to completely change.

The attached presentation summarizes the main points of this problem to a large extent, and introduces of if enough material to write a post dedicated to this subject about the real value of each product  (which I promise to write soon). However, what happens on those other occasions, more complicated to manage, where evolutionary, functional, technical, or even cost component is not important and there is no other option than migration?.  It is something inevitable and even logical, since we are in a world increasingly more changing, which occur in constant mergers of companies, acquisitions or strategic shifts, which may influence decisively forcing a migration.   In those cases, without forgetting that it is the decision of the customer, responsible posture is work towards customer satisfaction and not to close doors face a future. It is not reasonable to put a spoke in the wheel, but not to disguise the reality. It will therefore a hard situation, since it is difficult to have the confidence of the customer in these cases. Throughout this post, we will try to see how we can deal with this migration, and with t hat we could find in each case.

Continue reading