If your head is in the cloud then it's likely you'll recognize the terms in this blog title, each with that double 'a' in the middle. They refer, of course, to the three major cloud computing models in common use today: Infrastructure as a Service, Platform as a Service and Software as a Service.
If your head is not in the cloud but is thinking perhaps it should be, then read on: understanding these models, their capabilities, their pros and their cons are crucial to deciding which format is best for your business.
This post will take you through the difference between IaaS, PaaS and SaaS, what each offers, and which areas of your business will factor in determining the most suitable option.
When building an API, sooner or later you’ll have to secure it with some kind of authentication schema. There are many industry-standard solutions available - JWTs, sessions, OpenID...
Then, after implementing one you'll feel satisfaction - your API is secured!
That is until one of your customers gains access to another's data. Uh-oh. You forgot the authorization - again!
We are undoubtedly witnessing significant growth in software services designed for helping businesses increase the ease with which their clients access them. More and more, companies both big and small are turning to such technological solutions which in turn transform the way businesses and clientele communicate. By offering more instantaneous responses to queries, businesses stand to enhance customer satisfaction and thereby strengthen loyalty.
On a more personal level, I had long been sceptical of engaging a bot, however, once offered an expedient, simple solution to my problem within minutes, I began to think otherwise. Yet the question remains: are chatbots as reliable as traditional customer services, and are they natural and organic enough to handle user-specific issues?
While working on a recent project, I came across a product from Google Cloud Platform called Dialogflow. It turned out to be a very interesting experiment and actually, worked better than I'd expected - hence the following article.