This blog describes the basics of what it takes to get an existing LDAP server moved from the PV virtualization type to HVM. I encountered this situation personally while working for a client earlier this year. Efforts have been made to keep most of it generic enough to be useful for other situations involving system upgrades or replacements as well.
This year, the client I work with has started exploring the offerings in Google Cloud Platform (GCP) after investing years into the Microsoft Azure cloud. The opportunity has allowed me to explore a few new technologies that this post will cover and that you will hopefully find interesting.
In short, I was tasked with transforming Pub/Sub to Firestore Database in GCP. The scenario explored in this post takes an FHIR healthcare data feed, extracts telephone and email information, and then stores that in a Firestore database.
Keyhole Software gives readers an in-depth code walkthrough and tutorial for how to integrate Avaya Agent for Desktop using React and SignalR.
This integration allows the web-based application to asynchronously receive information about an inbound call, which enriches agents’ experiences and protects against context switching and double documenting. As for technology, AAfD (Avaya Agent for Desktop) is used as the softphone, React as the library to compose the SPA (Single Page Application), and SignalR as the bi-directional message hub.
The hypothetical scenario in this tutorial can be extended to many other use cases where there needs to be coordination between disparate systems, with an end userโs web browser being informed of the traffic without needing to do any long polling or other methodologies.
Asynchronous data flow is useful to many different business verticles, and SignalR is a powerful tool that will likely become a larger part of the custom Application Development enterprise ecosystem in years to come.
A new trend of creating applications is emerging called Jamstack. No, this isnโt slapping together your favorite flavor of jelly (grape is the best) with peanut butter and two pieces of bread. The intent is an architecture that is faster, more secure, and easier to scale. It focuses on pre-rending and decoupling. This way, the solutions created are more reliable and resilient than before.
Pre-rendering comes by the way of using a static website via a CDN for high availability and security. No more serving your React app via web server like weโve become accustomed to. It reduces cost and complexity by eliminating the regular maintenance and configuration of traditional servers.
Also, the idea of APIs and the ability to move them to things like Serverless functions creates more cost savings, elimination of traditional servers, and use of features only when they are requested. For more information, check out the Serverless website.
Welcome to the fourth and final installment of Creating an FHIR API with GCP. So far, weโve covered a lot!
We discussed the differences between Google and Azure, landing on GCP as the best option for FHIR in Part 1. We began our implementation in Part 2, creating both the BigQuery resources and your FHIR repository resources. And finally, in Part 3, we tackled authentication methods and populating data in our FHIR repository.
This time, weโll wrap everything up with a nice little bow. First, weโll finish our implementation, and then, Iโll share the limitation I found – for the sake of transparency. Letโs dive in.