Last week I hosted a “Bits & Bites” session on Serverless for my colleagues and some guests. These sessions are centered around some new technology, concepts or functionality (the “Bits” part) that one of us has encountered in his daily work and wants to spread the word. These events are great fun as you get to meet with your colleagues who frequently are working some other project and have dinner together (the “Bites” part) – these kinds of extras make the work fun!
As always, I had prepared way too much material for the hands-on exercises. To the positive side, nobody can claim that they finished early and had to keep themselves busy.
Recently, I organised a “Bits & Bites” session, introducing my colleagues to Node.js, Express and MongoDB. At SynTouch, we regularly have knowledge sharing sessions and workshops. Usually they are held late afternoon at a central location and include dinner, hence the name “Bits & Bites”! The reason I have chosen this specific subject has to do both with past as well as current interests.
Over the last years, I have become quite interested in cloud solutions. After completing the vendor-neutral Cloudschool.com’s Cloud Architect certification track, I decided it was time to dive into the real thing.
Although I come from an extensive Oracle background, until now I have not been really impressed with the Oracle Cloud solutions from my perspective as a developer. But when a colleague presented a talk at an internal company event about Amazon Web Services, I became quite attracted to the solution development possibilities on the AWS platform.
In the second part of this two part blog post, I will describe the actual creation of the API definition in API Platform Cloud Service (shortened to APIPCS), the service callout to an external microservice (conveniently located in the Oracle Application Container Cloud Service) using a custom Groovy script policy and testing the flow created. The first part discussed the use case for which we used Oracle API Platform Cloud Service (shortened to APIPCS from now on) as an outbound API Gateway, offering lookup services and centralizing outbound access. This part also described a simple Node.js microservice we created to perform the translation of an internal identification into the API key required by the external API.
Milco NumanMy first experience with Oracle API Platform Cloud Service – part 2
In the first part of this two part blog post, I will describe the use case for which we used Oracle API Platform Cloud Service (shortened to APIPCS from now on) as an outbound API Gateway, offering lookup services and centralizing outbound access. This part will also describe a simple Node.js microservice we deployed to Oracle’s Application Container Cloud Service to perform the translation of an internal identification into the API key required by the external API.
Milco NumanMy first experience with Oracle API Platform Cloud Service – part 1
Milco NumanFirst steps in Cloud-based JS development
Although I have acquired quite some experience in the past years using Oracle’s Service Bus and XQueries for transformations, there are still a lot of things I do not know … Some time ago, one of my colleagues mentioned a neat trick using Service Bus 11g to act as a shorthand for a conditional construct, <MyTagName?>.