In November 2018, I had the privilege to attend the Australian Oracle User Group national conference “#AUSOUG Connect” in Melbourne. My role was to have video interviews with as many of the speakers and exhibitors at the conference. Overall, 10 interviews over the course of the day, 90 mins of real footage, 34 short clips to share and plenty of hours reviewing and post-editing to capture the best parts.
Security is super important, but also annoying. From a backend developer mindset, all I want is to build great services exposed as APIs that the world can consume with ease. The problem is that in most cases, consumption of my endpoints will be blocked by browsers and other tools/client unless they are exposed as HTTPS with valid SSL certificates.
In this blog, I am going to show you how to use Let’s Encrypt to create your own “Wildcard SSL Certificate” for your existing domain, for example: *.mydomain.com – Then I am going to show you how to assign this certificate to your Oracle LBaaS Listener endpoint.
In a previous blog, I explained how to provision a Kubernetes cluster locally on your laptop (either as a single node with minikube or a multi-node using VirtualBox), as well as remotely in the Oracle Public Cloud IaaS. In this blog, I am going to show you how to get started with Oracle Container Engine for Kubernetes (OKE). OKE is a fully-managed, scalable, and highly available service that you can use to deploy your containerized applications to the cloud on Kubernetes.
I recommend using OKE when you want to reliably build, deploy and manage cloud-native applications. Oracle takes full responsibility of provisioning the Kubernetes cluster and managing tiers (control plane), you simply choose how many Kubernetes worker nodes you want to have and then simply deploy your Kubernetes Applications there. Oracle manages the full Kubernetes Control plane, and wait, the best part is that Oracle does not charge for it, you just pay for the primitive IaaS that you use to run your application.
For the purpose of this demonstration I am going to show how to:
- Provision an OKE cluster
- Configure kubectl locally, so that you can run commands against your OKE cluster, e.g. deploy your application.
Finally, I am going to show you how to deploy a microservice into your OKE cluster.
For the purpose of this demonstration, I built a microservice earlier in a previous blog. It is a containerised NodeJS application called apis4harness that allows to interact with OCI API resources. In particular, it allows to: list, start and stop Oracle Autonomous Data Warehouse (ADW) instances.
This is a high-level visual representation:
In this blog, I am going to show you how to build a nice and simple UI with data coming from invoking REST APIs. All without code, but in just a few clicks.
I consider myself a good backend developer, good at making things functional, but I really struggle every time I need to produce nice UIs. However, using Oracle Visual Builder, I feel like I don’t have to be a UI developer or designer, I can very easily produce nice and friendly mobile UIs that consume my backend REST APIs. If you are like me, a backend programmer who loves API-first design approach, I’m sure that you will find this blog not only informative, but also refreshing.
This is a quick view of what we are going to achieve in this article:
- First, we are going to auto-create Service controls in Oracle Visual Builder by pointing to existing REST APIs.
- Then, we are going to use the out-of-the box widgets and components to build a simple, yet powerful UI that consumes such APIs.
- Finally, we are going to publish the UI and test it across different media, e.g. Web on a laptop, mobile, tablets, etc.
I am thrilled with the Oracle’s Gen2 Cloud Infrastructure architecture, where Oracle completely separates the Cloud Control Computers from the User Code, so that no threats can enter from outside the cloud and no threats can spread from within tenants.
Obviously with more security, there comes more coordination, especially at the moment of invoking OCI resources APIs. Luckily, Oracle did a good job at providing a simple to use CLI and SDK (see here for more information).
For the purpose of this blog, I built a simple NodeJS application that helps demystify the security aspect of invoking OCI APIs. Check this link for examples of running similar code across other Programming Languages.
My NodeJS application manages OCI resources in order to:
- List ADW instances
- Stop an ADW instance
- Start an ADW instance
I started this NodeJS application to list, start and stop ADW resources. However, I designed this application to easily extend it to invoke any other type of OCI resources.
I containerised this application with Docker, to make it easier to ship and run.
This is a picture of the moving parts:
Databases and Data Warehouses have been around for a long time and they bring multiple benefits to business, but these also come at a cost. Some of the associated challenges include:
- Complex and Expensive to provision and secure
- Inability to manage data and user growth
- Costly to maintain
In this post, I will provide some resources on how Oracle Autonomous Database and Data Warehouse aim at easing these challenges and increase the speed at which you can innovate and the value you can get from your data.
Majority of the websites have FAQ pages, and they are always dull. If only you could convert your FAQ to something more tangible that solves the users need you could resolve customer frustration of finding the right information. Moreover, if that experience is more interactive, it leads to an engaging experience where you can contextualise the data and also execute the task on behalf of the customer. We can create this rich experience by making your traditional FAQ’s wrapped inside a chatbot.
In this article let’s have a look at how we can quickly convert FAQ Pages to a Bot in minutes. Oracle’s natural language understanding technology and QnA engine available in Digital Assistant platform can sift through the historical FAQ data and answer even sophisticated requests from your clients. Further, you can handover complex queries to your support as I discussed in an earlier article