phobos 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 97e08e50c3b2cfdb020c71c181989cb90e865316
+  data.tar.gz: 21bab9e83626f738b5903355e477b03ad5ff4d89
+SHA512:
+  metadata.gz: 17421090032e4212c626f708e80f5dca3d3c6421757982268980d954841473ab5176fdb907ac594bc079a5595b4f405b6402362767e01e12ec6b9a45d83e3d01
+  data.tar.gz: aa1b7bbf6f07c99cde3f2246a0dc848b9e7a1cb395e42e1513e5a1e7265488cb46b81dc48ae9d049abf61ebab4854dece2b4d594ab52a2e3310fd97412a2c406

data/.gitignore

@@ -0,0 +1,14 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+spec/examples.txt
+/tmp/
+.DS_Store
+config/phobos.yml
+log/*.log
+.byebug_history

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.ruby-version

@@ -0,0 +1 @@
+2.3.0

data/Dockerfile

@@ -0,0 +1,13 @@
+FROM ruby:2.3.1-alpine
+
+RUN apk update && apk upgrade && \
+    apk add --no-cache bash git openssh build-base
+
+WORKDIR /opt/phobos
+
+ADD Gemfile Gemfile
+ADD phobos.gemspec phobos.gemspec
+ADD lib/phobos/version.rb lib/phobos/version.rb
+
+RUN ["bundle", "install"]
+ADD . .

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in phobos.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,176 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

data/README.md

@@ -0,0 +1,413 @@
+![Circle CI](https://circleci.com/gh/klarna/phobos.svg?style=shield&circle-token=2289e0fe5bd934074597b32e7f8f0bc98ea0e3c7)
+
+# Phobos
+
+Simplifying Kafka for Ruby apps!
+
+Phobos is a micro framework and library for applications dealing with [Apache Kafka](http://kafka.apache.org/).
+
+- It wraps common behaviors needed by consumers and producers in an easy and convenient API
+- It uses [ruby-kafka](https://github.com/zendesk/ruby-kafka) as its Kafka client and core component
+- It provides a CLI for starting and stopping a standalone application ready to be used for production purposes
+
+Why Phobos? Why not `ruby-kafka` directly? Well, `ruby-kafka` is just a client. You still need to write a lot of code to manage proper consuming and producing of messages. You need to do proper message routing, error handling, retrying, backing off and maybe logging/instrumenting the message management process. You also need to worry about setting up a platform independent test environment that works on CI as well as any local machine, and even on your deployment pipeline. Finally, you also need to consider how to deploy your app and how to start it.
+
+With Phobos by your side, all this becomes smooth sailing.
+
+## Table of Contents
+
+1. [Installation](#installation)
+1. [Usage](#usage)
+  1. [Standalone apps](#usage-standalone-apps)
+  1. [Consuming messages from Kafka](#usage-consuming-messages-from-kafka)
+  1. [Producing messages to Kafka](#usage-producing-messages-to-kafka)
+  1. [As library in another app](#usage-as-library)
+  1. [Configuration file](#usage-configuration-file)
+  1. [Instrumentation](#usage-instrumentation)
+1. [Development](#development)
+
+## <a name="installation"></a> Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'phobos'
+```
+
+And then execute:
+
+```sh
+$ bundle
+```
+
+Or install it yourself as:
+
+```sh
+$ gem install phobos
+```
+
+## <a name="usage"></a> Usage
+
+Phobos can be used in two ways: as a standalone application or to support Kafka features in your existing project - including Rails apps. It provides a CLI tool to run it.
+
+### <a name="usage-standalone-apps"></a> Standalone apps
+
+Standalone apps have benefits such as individual deploys and smaller code bases. If consuming from Kafka is your version of microservices, Phobos can be of great help.
+
+### Setup
+
+To create an application with Phobos you need two things:
+  * A configuration file (more details in the [Configuration file](#usage-configuration-file) section)
+  * A `phobos_boot.rb` (or the name of your choice) to properly load your code into Phobos executor
+
+Use the Phobos CLI command __init__ to bootstrap your application. Example:
+
+```sh
+# call this command inside your app folder
+$ phobos init
+    create  config/phobos.yml
+    create  phobos_boot.rb
+```
+
+`phobos.yml` is the configuration file and `phobos_boot.rb` is the place to load your code.
+
+### Consumers (listeners and handlers)
+
+In Phobos apps __listeners__ are configured against Kafka - they are our consumers. A listener requires a __handler__ (a ruby class where you should process incoming messages), a __topic__, and a __group_id__. Consumer groups are used to coordinate the listeners across machines. We write the __handlers__ and Phobos makes sure to run them for us. An example of a handler is:
+
+```ruby
+class MyHandler
+  include Phobos::Handler
+
+  def consume(payload, metadata)
+    # payload  - This is the content of your Kafka message, Phobos does not attempt to
+    #            parse this content, it is delivered raw to you
+    # metadata - A hash with useful information about this event, it contains: The event key,
+    #            partition number, offset, retry_count, topic, group_id, and listener_id
+  end
+end
+```
+
+Writing a handler is all you need to allow Phobos to work - it will take care of execution, retries and concurrency.
+
+To start Phobos the __start__ command is used, example:
+
+```sh
+$ phobos start
+[2016-08-13T17:29:59:218+0200Z] INFO  -- Phobos : <Hash> {:message=>"Phobos configured", :env=>"development"}
+______ _           _
+| ___ \ |         | |
+| |_/ / |__   ___ | |__   ___  ___
+|  __/| '_ \ / _ \| '_ \ / _ \/ __|
+| |   | | | | (_) | |_) | (_) \__ \
+\_|   |_| |_|\___/|_.__/ \___/|___/
+
+phobos_boot.rb - find this file at ~/Projects/example/phobos_boot.rb
+
+[2016-08-13T17:29:59:272+0200Z] INFO  -- Phobos : <Hash> {:message=>"Listener started", :listener_id=>"6d5d2c", :group_id=>"test-1", :topic=>"test"}
+```
+
+By default, the __start__ command will look for the configuration file at `config/phobos.yml` and it will load the file `phobos_boot.rb` if it exists. In the example above all example files generated by the __init__ command are used as is. It is possible to change both files, use `-c` for the configuration file and `-b` for the boot file. Example:
+
+```sh
+$ phobos start -c /var/configs/my.yml -b /opt/apps/boot.rb
+```
+### <a name="usage-consuming-messages-from-kafka"></a> Consuming messages from Kafka
+
+Messages from Kafka are consumed using __handlers__. You can use Phobos __executors__ or include it in your own projet [as a library](#usage-as-library), but __handlers__ will always be used. To create a handler class, simply include the module `Phobos::Handler`. This module allows Phobos to manage the life cycle of your handler.
+
+A handler must implement the method `#consume(payload, metadata)`.
+
+Instances of your handler will be created for every message, so keep a constructor without arguments. If `consume` raises an exception, Phobos will retry the message indefinitely, applying the back off configuration presented in the configuration file. The `metadata` hash will contain a key called `retry_count` with the current number of retries for this message. To skip a message, simply return from `#consume`.
+
+When the listener starts, the class method `.start` will be called with the `kafka_client` used by the listener. Use this hook as a chance to setup necessary code for your handler. The class method `.stop` will be called during listener shutdown.
+
+```ruby
+class MyHandler
+  include Phobos::Handler
+
+  def self.start(kafka_client)
+    # setup handler
+  end
+
+  def self.stop
+    # teardown
+  end
+
+  def consume(payload, metadata)
+    # consume or skip message
+  end
+end
+```
+
+It is also possible to control the execution of `#consume` with the class method `.around_consume(payload, metadata)`. This method receives the payload and metadata, and then invokes `#consume` method by means of a block; example:
+
+```ruby
+class MyHandler
+  include Phobos::Handler
+
+  def self.around_consume(payload, metadata)
+    Phobos.logger.info "consuming..."
+    output = yield
+    Phobos.logger.info "done, output: #{output}"
+  end
+
+  def consume(payload, metadata)
+    # consume or skip message
+  end
+end
+```
+
+Take a look at the examples folder for some ideas.
+
+The hander life cycle can be illustrated as:
+
+  `.start` -> `#consume` -> `.stop`
+
+or optionally,
+
+  `.start` -> `.around_consume` [ `#consume` ] -> `.stop`
+
+### <a name="usage-producing-messages-to-kafka"></a> Producing messages to Kafka
+
+`ruby-kafka` provides several options for publishing messages, Phobos offers them through the module `Phobos::Producer`. It is possible to turn any ruby class into a producer (including your handlers), just include the producer module, example:
+
+```ruby
+class MyProducer
+  include Phobos::Producer
+end
+```
+
+Phobos is designed for multi threading, thus the producer is always bound to the current thread. It is possible to publish messages from objects and classes, pick the option that suits your code better.
+The producer module doesn't pollute your classes with a thousand methods, it includes a single method the class and in the instance level: `producer`.
+
+```ruby
+my = MyProducer.new
+my.producer.publish('topic', 'message-payload', 'partition and message key')
+
+# The code above has the same effect of this code:
+MyProducer.producer.publish('topic', 'message-payload', 'partition and message key')
+```
+
+It is also possible to publish several messages at once:
+
+```ruby
+MyProducer
+  .producer
+  .publish_list([
+    { topic: 'A', payload: 'message-1', key: '1' },
+    { topic: 'B', payload: 'message-2', key: '2' },
+    { topic: 'B', payload: 'message-3', key: '3' }
+  ])
+```
+
+There are two flavors of producers: __normal__ producers and __async__ producers.
+
+Normal producers will deliver the messages synchronously and disconnect, it doesn't matter if you use `publish` or `publish_list` after the messages get delivered the producer will disconnect.
+
+Async producers will accept your messages without blocking, use the methods `async_publish` and `async_publish_list` to use async producers.
+
+An example of using handlers to publish messages:
+
+```ruby
+class MyHandler
+  include Phobos::Handler
+  include Phobos::Producer
+
+  PUBLISH_TO = 'topic2'
+
+  def consume(payload, metadata)
+    producer.async_publish(PUBLISH_TO, {key: 'value'}.to_json)
+  end
+end
+```
+
+#### Note about configuring producers
+
+Since the handler life cycle is managed by the Listener, it will make sure the producer is properly closed before it stops. When calling the producer outside a handler remember, you need to shutdown them manually before you close the application. Use the class method `async_producer_shutdown` to safely shutdown the producer.
+
+Without configuring the Kafka client, the producers will create a new one when needed (once per thread). To disconnect from kafka call `kafka_client.close`.
+
+```ruby
+# This method will block until everything is safely closed
+MyProducer
+  .producer
+  .async_producer_shutdown
+
+MyProducer
+  .producer
+  .kafka_client
+  .close
+```
+
+### <a name="usage-as-library"></a> Phobos as a library in an existing project
+
+When running as a standalone service, Phobos sets up a `Listener` and `Executor` for you. When you use Phobos as a library in your own project, you need to set these components up yourself.
+
+First, call the method `configure` with the path of your configuration file
+
+```ruby
+Phobos.configure('config/phobos.yml')
+```
+
+__Listener__ connects to Kafka and acts as your consumer. To create a listener you need a handler class, a topic, and a group id.
+
+```ruby
+listener = Phobos::Listener.new(
+  handler: Phobos::EchoHandler,
+  group_id: 'group1',
+  topic: 'test'
+)
+
+# start method blocks
+Thread.new { listener.start }
+
+listener.id # 6d5d2c (all listeners have an id)
+listener.stop # stop doesn't block
+```
+
+This is all you need to consume from Kafka with back off retries.
+
+An __executor__ is the supervisor of all listeners. It loads all listeners configured in `phobos.yml`. The executor keeps the listeners running and restarts them when needed.
+
+```ruby
+executor = Phobos::Executor.new
+
+# start doesn't block
+executor.start
+
+# stop will block until all listers are properly stopped
+executor.stop
+```
+
+When using Phobos __executors__ you don't care about how listeners are created, just provide the configuration under the `listeners` section in the configuration file and you are good to go.
+
+### <a name="usage-configuration-file"></a> Configuration file
+The configuration file is organized in 6 sections. Take a look at the example file, [config/phobos.yml.example](https://github.com/klarna/phobos/blob/master/config/phobos.yml.example).
+
+__logger__ configures the logger for all Phobos components, it automatically outputs to `STDOUT` and it saves the log in the configured file
+
+__kafka__ provides configurations for every `Kafka::Client` created over the application. All [options supported by  `ruby-kafka`][ruby-kafka-client] can be provided.
+
+__producer__ provides configurations for all producers created over the application, the options are the same for normal and async producers. All [options supported by  `ruby-kafka`][ruby-kafka-producer] can be provided.
+
+__consumer__ provides configurations for all consumer groups created over the application. All [options supported by  `ruby-kafka`][ruby-kafka-consumer] can be provided.
+
+__backoff__ Phobos provides automatic retries for your handlers, if an exception is raised the listener will retry following the back off configured here
+
+__listeners__ is the list of listeners configured, each listener represents a consumers group
+
+[ruby-kafka-client]: http://www.rubydoc.info/gems/ruby-kafka/Kafka%2FClient%3Ainitialize
+[ruby-kafka-consumer]: http://www.rubydoc.info/gems/ruby-kafka/Kafka%2FClient%3Aconsumer
+[ruby-kafka-producer]: http://www.rubydoc.info/gems/ruby-kafka/Kafka%2FClient%3Aproducer
+
+### <a name="usage-instrumentation"></a> Instrumentation
+
+Some operations are instrumented using [Active Support Notifications](http://api.rubyonrails.org/classes/ActiveSupport/Notifications.html).
+
+In order to receive notifications you can use the module `Phobos::Instrumentation`, example:
+
+```ruby
+Phobos::Instrumentation.subscribe('listener.start') do |event|
+  puts(event.payload)
+end
+```
+
+`Phobos::Instrumentation` is a convenience module around `ActiveSupport::Notifications`, feel free to use it or not. All Phobos events are in the `phobos` namespace. `Phobos::Instrumentation` will always look at `phobos.` events.
+
+#### Executor notifications
+  * `executor.retry_listener_error` is sent when the listener crashes and the executor wait for a restart. It includes the following payload:
+    * listener_id
+    * retry_count
+    * waiting_time
+    * exception_class
+    * exception_message
+    * backtrace
+  * `executor.stop` is sent when executor stops
+
+#### Listener notifications
+  * `listener.start_handler` is sent when invoking `handler.start(kafka_client)`. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+  * `listener.start` is sent when listener starts. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+  * `listener.process_batch` is sent after process a batch. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+    * batch_size
+    * partition
+    * offset_lag
+    * highwater_mark_offset
+  * `listener.process_message` is sent after process a message. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+    * key
+    * partition
+    * offset
+    * retry_count
+  * `listener.retry_handler_error` is sent after waited for `handler#consume` retry. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+    * key
+    * partition
+    * offset
+    * retry_count
+    * waiting_time
+    * exception_class
+    * exception_message
+    * backtrace
+  * `listener.retry_aborted` is sent after waiting for a retry but the listener was stopped before the retry happened. It includes the following payload:
+    * listener_id
+    * group_id
+    * topic
+  * `listener.stopping` is sent when the listener receives signal to stop
+    * listener_id
+    * group_id
+    * topic
+  * `listener.stop_handler` is sent after stopping the handler
+    * listener_id
+    * group_id
+    * topic
+  * `listener.stop` is send after stopping the listener
+    * listener_id
+    * group_id
+    * topic
+
+## <a name="development"></a> Development
+
+After checking out the repo:
+* make sure docker is installed and running
+* run `bin/setup` to install dependencies
+* run `sh utils/start-all.sh` to start the required kafka containers in the background
+* run `rspec` to run the tests
+
+You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+The `utils` folder contain some shell scripts to help with the local Kafka cluster. It uses docker to start Kafka and zookeeper.
+
+```sh
+sh utils/start-all.sh
+sh utils/stop-all.sh
+```
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/klarna/phobos.
+
+## License
+
+Copyright 2016 Klarna
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
+
+You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.