For a customer we're managing a Cloud Foundry installation (actually Tanzu Application Service, TAS). I wanted to give the deployment of a simple Rust REST API a try and hit some issues which I'll describe in this blog post.
This is part 4 in a series of posts about writing service brokers in .NET Core.
This is part 3 in a series of posts about writing service brokers in .NET Core.
This is part 2 in a series of posts about writing service brokers in .NET Core.
I'm experimenting with writing a service broker in .NET Core that conforms to the Open Service Broker API specification. This is part 1 of a series of posts that explores all service broker details from a .NET perspective.
This is part 2 of a series of (still) unknown length where I try to describe how to deploy the [SDL Tridion Web 8.5 Discovery Service][1] on CloudFoundry.
A customer of ITQ is running [SDL][1] [Tridion][2] content management software and has asked us to deliver a proof-of-concept of running a Tridion website and the Tridion 8.5 micro services on Pivotal CloudFoundry. This post is a journal of my attempts of deploying the [SDL Web 8.5 Discovery Service][3] on CloudFoundry.
I've been involved in a project that uses Pivotal CloudFoundry as the PAAS platform of choice. To provide some minimal background info: CloudFoundry is an open-source PAAS platform that can run on top of a number of cloud infrastructures: Azure, AWS, GCP, OpenStack, VMware vSphere and more. Pivotal is a company that offers a commercial CloudFoundry package that includes support, certification and additional services.