Elixir/Erlang OTP abstractions enforce developers to split programs into independent parts. While “gen_servers” encapsulate parts of business logic on micro-level, “applications” present a more general (“service”) part of the system. Complex programs written in Elixir are always a collection of communicating OTP applications. The main question appeared while developing such programs is how to spli
According to GoF and their great book “Design Patterns: Elements of Reusable Object-Oriented Software”, builder pattern: „Separate the construction of a complex object from its representation so that the same construction process can create different representations.” and it’s a part of an object creational design patterns. Builder pattern is useful when the algorithm how to build an object is som
I have recently found out about Nanobox.io and saw it as an excellent alternative to Heroku when deploying an Elixir, Phoenix and Elm application. The most important advantage of using Nanobox instead of Heroku (which I’m a huge fan) is that it allows for each Elixir node to talk to each other directly. Another advantage is that you can deploy to Cloud computing engine other than AWS such as Azure
Today we’ll be deploying OpenFaaS using Kubernetes as a container orchestrator. OpenFaaS is Serverless Functions Made Simple, and is currently the most easy to deploy Open Source Serverless platform out there. OpenFaaS is Serverless Functions Made SimpleTypically Docker Swarm is used as the orchestrator, but the demand for OpenFaaS on Kubernetes was so high that Kubernetes is officially supported.
Our event driven system runs on Google Cloud and the heart that makes it possible for us to pass all these events around is Pub/Sub, Google’s messaging service. In many ways this has been a great experience, but some things annoyed us. One of them was the fact that it’s a bit cumbersome to use, the SDK (in our case the Java one) is not all that intuitive, it’s in Beta (Alpha when we started using
In the first post of this series I looked at how kubernetes employs a combination of virtual network devices and routing rules to allow a pod running on one cluster node to communicate with a pod running on another, as long as the sender knows the receiver’s pod network IP address. If you aren’t already familiar with how pods communicate then it’s worth a read before continuing. Pod networking in
I’ve been working on a simple web application written in Go, hosted in Google Cloud, using Google Kubernetes Engine. It turned to be such great experience, I couldn’t miss an opportunity to share it. It took me less than an hour to setup things for the first time, reading the documentation and trying to figure out how things work. But, once I finished, I could deploy a new version of my applicatio
Companies and even governments and other organisations nowadays start to evaluate blockchain technologies more and more, and the former picture of a typical slow-in-adoption-dinosaur-enterprise-company is already changing as it has clear benefits to invest in a more modern and scalable infrastructure like Kubernetes to run their mission-critical workloads. A system like kubernetes can also be used
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く