Microgames for Wetware Developers by Julia Dellnitz & Stefan Zörner

Hypoport invites you to an interesting GOTO Night with Julia Dellnitz & Stefan Zörner on behalf of GOTO Berlin.

The session will start at 7PM on July 2, 2015 at our headquarter Klosterstr. 71, 10179 Berlin. Please come by and give them a visit. Food and Drinks will complement the session.

Microgames are small decoupled learning entities about a specific topic such as software architecture. They help teams and companies to get up to speed in a specific field and can easily be integrated in their daily practices. Microgames implement the idea that the wetware of our brain develops best when we are alert, link our learning to our day-to-day work, learn with positive emotions and distribute small learning units over time.

Julia Dellnitz (Learnical) and Stefan Zörner (embarc) will provide a playful and interactive session with findings from neuroscience and practical examples from software architecture.
Join us and be ready to play!


Julia Dellnitz creates playful and interactive learning formats. Her passion is to support experts in developing and implementing innovative (IT-) products and processes. She has managed large change and IT implementation initiatives over the last decade and has worked with over 4.500 people on learning and innovation topics – especially in international contexts.

Twitter: @learnical

Stefan Zörner from the Bayer AG via IBM and oose to embarc. He embodies twenty years of experience in IT and he still looks forward eagerly. He supports clients in solving architecture and implementation issues. In lively workshops he demonstrates practical design tools and spreads enthusiasm for real architecture work.

Twitter: @stefanzoerner

GOTO Night at Hypoport: From the Monolith to Microservices – Randy Shoup

Hypoport is happy to host an interesting GOTO Night with Randy Shoup talking about “From the Monolith to Microservices”.

On behalf of GOTO Berlin and Microservices Meetup Berlin we welcome you at Hypoport.

Venue: Hypoport, Klosterstr. 71, 10179 Berlin
Date: April 20, 2015
Entrance: 18:30 / 6:30PM
Talk: 19:00 / 7PM

“From the Monolith to Microservices: Lessons from Google and eBay”
by Randy Shoup

Most large-scale web companies have evolved their system architecture from a monolithic application and monolithic database to a set of loosely coupled microservices. Using examples from Google, eBay, and other large-scale sites, this talk outlines the pros and cons of these different stages of evolution, and makes practical suggestions about when and how other organizations should consider migrating to microservices. It concludes with some more advanced implications of a microservices architecture, including SLAs, cost-allocation, and vendor-customer relationships within the organization.

Randy has worked as a senior technology leader and executive in Silicon Valley at companies ranging from small startups, to mid-sized places, to eBay and Google. In his consulting practice, he applies this experience to scaling the technology infrastructures and engineering organizations of his client companies. He served as CTO of KIXEYE, a 500-person maker of real-time strategy games for web and mobile devices. Prior to KIXEYE, he was Director of Engineering in Google’s cloud computing group, leading several teams building Google App Engine, the world’s largest Platform as a Service. Previously, he was CTO and Co-Founder of Shopilly, an ecommerce startup, and spent 6 1/2 years as Chief Engineer and Distinguished Architect at eBay. Randy is a frequent keynote speaker and consultant in areas from scalability and cloud computing, to analytics and data science, to engineering culture and DevOps. He is particularly interested in the nexus of people, culture, and technology.
Twitter: @randyshoup

Please register here. For any questions do not hesitate to contact Dajana Günther.

Microxchg Special: Seneca Node JS μServices Framework and Docker Orchestration

On Wednesday Feb 11, the evening before microxchg – the micro services conference, Hypoport is hosting the microservices meetup Berlin with talks from two of the conference speakers.

Richard Roger will talk about Seneca Node JS μServices Framework

Peter Rossbach will talk about Docker Orchestration

Please register on microservices meetup Berlin.

See you there, Leif

Docker Meetup at Hypoport with “Why you’ll love managing containers with Docker” & “Docker on AWS” on Jan, 19th

Docker Berlin is back! You can now follow us on Twitter too @DockerBerlin

To init and containerize this new year properly we have two great speakers lined-up at Hypoport on Jan, 19th.

Johannes Ziemke [Docker Inc.] and Sascha Möllering [ZANOX.de AG]

Managing containers with Docker…and why you’ll love it – Johannes Ziemke

What are the challenges of today’s infrastructures, why containers are the right building blocks and Docker the right tool to manage those.

Docker is an open-source project to easily create lightweight, portable, self-sufficient containers from any application. The same container that a developer builds and tests on a laptop can run at scale, in production, on VMs, bare metal, OpenStack clusters, public clouds and more.

I’ll talk about the challenges of managing complex infrastructures based on my past experiences, why live state mutation sucks and configuration management is doomed, self-sufficient and light-weight containers are the answer and how Docker manage those.

Last but not least I’ll show how to build, ship and run containers and real world examples of what Docker is already used for.

Speaker profile: http://de.linkedin.com/in/johannesziemke

Docker in the Cloud on AWS – Sascha Möllering

In this talk, I’ll describe how to leverage the potential of Docker and Amazon Web Services to deploy Docker Containers in AWS, connect to managed services from your application and implement the immutable server pattern.

Speaker profile: https://www.linkedin.com/pub/sascha-m%C3%B6llering/2b/268/403


6:00 – 6:30: Networking

6:30 – 7:15: Managing containers with Docker

7:15 – 7:30: Break

7:30 – 8:00: Docker in the Cloud on AWS

8:00 – open end: Networking

This meetup is kindly sponsored by Hypoport, which provides venue, food and drinks! It would be nice if you sign up on the meetup Docker Berlin event.

Marry Xmas and a Happy New Year. See you there.

Docker Global Hack Day #2 – Berlin Edition at Hypoport

We are proud to announce that we are part of the Docker Global Hack Day #2. Join other members of the Docker community to hack on Docker projects using the next big Docker release! You’re all invited to Hypoport HQ in Berlin for a hacking session while sharing a meal/drink with fellow Dockers. This hackathon is your last chance to win a ticket to the sold out DockerCon Europe. Please register using our meetup event page.

See you then.

How to open async calls in a new tab instead of new window within an AngularJS app

I recently wanted to generate a PDF on users demand and show it in a new browser tab.
Sounds trivial, at first not for me :) I tried it with different “solutions” and on my way my google search result got better and better. With “open window new tab without popup blocker async” I finally found in this thread a nice and easy solution. The trick is to remember the reference to the new window and change the location of that window when your asynchron call completes.

$scope.generatePdf = function () {
  var tabWindowId = window.open('about:blank', '_blank');

  $http.post('/someUrl', data).then( function (response) {
    tabWindowId.location.href = response.headers('Location');

If you want to see it in action open this plunker. While testing this plunker, it seems that openWindow will open a tab, as long as the async call is quick enough (less than a second). The setTimeout is therefore set to 1001.

I hope you will find this solution quicker than I did. Please let me know if you have any questions or suggestions. Either per @leifhanack or comment here.

managing multiple ssh keys

Recently I wanted to connect to some remote server using different ssh keys. With the right ~/.ssh/config file this is easy and comfortable.


IdentityFile ~/.ssh/%h/%r/id_rsa
IdentityFile ~/.ssh/%h/id_rsa
IdentityFile ~/.ssh/id_rsa

%h and %r are placeholder for host and remote-user. ssh foo@bar will first check if ~/.ssh/bar/foo/id_rsa exists, next ~/.ssh/bar/id_rsa and finally ~/.ssh/id_rsa.


Host github
        HostName 123.45.678.90
        User myuser
        IdentityFile ~/.ssh/123.45.678.90/id_rsa

Instead of ssh myuser@123.45.678.90 the above config allows you to simply type

ssh github

You don’t need to remember all your IPs and remote-users any longer. For me this is a big time saver.

Please let me know if you have questions or suggestions. Either per @leifhanack or comment here.