Developers at Indeed have recently switched over to using docker for local development. Being one of the earlier adopters, I fell in love with the type of workflow that it enabled. It allowed me to create seamless environments between both my desktop and portable workstation. The tooling did this by allowing you to resolve container names as hosts in your web browser. For example, if I had a web application named indigo running on port 4000, I could go to http://indigo:4000 to access that application. After a few weeks of enjoying the simplicity of this development workflow, I craved a similar type of environment for some of the larger scale projects that I do at home. In this blog post, I will cover some of the basics that allowed me to enable this type of development.
LAAS is an abbreviation for LevelDB as a service. LevelDB is an implementation of a log structured merge tree (LSMTree) provided by Google. This data structure aimed at providing a high write throughput. When attempting to use LevelDB, I found it difficult to track down supported libraries in different languages. Additionally, the fact that it’s labeled as a database and doesn’t provide a service was troublesome. I wrote LAAS to make the adoption of LevelDB easy for any language. It does this by introducing a RESTful API to the underlying functionality. HTTP request libraries are a dime a dozen, which drove the choice for a RESTful implementation.
We are excited to highlight the open source availability of Status, a Java library that can report a system’s status in a readable format. The Status library enables dynamic health checks and monitoring of system dependencies. In this post, we will show how to add health checks to your applications.