“Hallo Deutschland” – Getting Started with Bluemix in Germany

Share this post:

Node.js Cloudant Boilerplate in Germany

Node.js Cloudant Boilerplate deployed to Bluemix Germany

“Hallo Deutschland” or “Hello Germany” is an app I recently deployed. I didn’t want to push a simple “hello world”. The reason is that Bluemix Public is now available in Frankfurt, Germany. It is an important addition to the Bluemix regions. As a German, I am really excited (yes, we can) to be able to deploy applications and store data close to home. Here are some things to get you started with the “German Bluemix”.

Getting Started

Bringing a cloud service to a new location is like moving with your family to a new city: You need to learn your way around to feel home. You probably know what is in the moving boxes, but not your visitors. And it may need some time to unpack and get your new home fully equipped. To get you started quickly, let me share what I learned about our new home:

Bluemix Status Page

Bluemix Status including Germany

  • First of all, Bluemix Public in Frankfurt, Germany, is identified as region “eu-de”. This means the console is accessible as The API endpoint is “”.
  • Next, if you already have a Bluemix account, then you automatically have access to the new German region. If not, just sign up for a free trial account.
  • Similar to the start of Bluemix in London and Sydney, the Bluemix catalog for Germany has not the extensive list of services yet. Nonetheless, a good chunk of cognitive, data and analytics, integration and other services are already available. Together with the runtimes and compute options Bluemix provides the foundation for your applications.
  • As usual, the Bluemix documentation is available at “/docs”, i.e.,
  • Not surprisingly, the Bluemix status page (see screenshot) includes the new “eu-de” region.

My Data in Germany

When you click on a service in the Bluemix catalog then the dialog to provision that service comes up. I always find it interesting to take a look at the “location” property. It indicates from where the service is delivered, i.e., where the data is processed (and stored, if any). When Bluemix Public in Frankfurt, Germany, was launched I went from service to service, checked the location and repeatedly said “Hallo Deutschland”. It is great to have my data stored and processed that close to home.

P.S.: If you are new to Bluemix and want to get an even broader overview then I would recommend reading my (slightly dated) blog article from early last year on “How to Bluemix“. Thereafter, start by deploying a boilerplate to easily get your first Bluemix application up and running in no time.

More What's New Stories

Securely Access MongoDB from a Spring Boot App Running on Bluemix Kubernetes Using Kubernetes Secrets

This example builds on my previous post where I showed how to access a Bluemix MongoDB service from a Spring data app running locally. In that simple example the MongoDB credentials were either hard coded in the application or specified manually on the command line.

Continue reading

Accessing a Bluemix MongoDB Service from a Java Spring Boot Application

In this blog post I'll show how to access a Compose for MongoDB database running on IBM Bluemix from a Spring boot application running locally. Spring is a popular open source framework and container for Java applications. MongoDB is a popular open source document oriented NoSQL database that uses JSON-like documents.

Continue reading

Spring, Liberty and Single Sign On

Have you ever wondered how you could protect your Spring app with the Bluemix SSO service? In this article, we’ll cover how you can convert a Spring application running on Liberty from using a manually configured Open ID Connect (OIDC) Server, to using the Bluemix Single Sign On service. A short while ago I wrote […]

Continue reading