In most performance comparisons, Redis (an open source key-value cache/store) is mainly treated as a caching-only solution. Others are only focused on a single provider. However, customers are interested in deeper utilization of built-in data types and server-side operations. In production, you may have several loads that query your database simultaneously—with different types of tasks.
For this reason, we designed a scenario that evaluates Redis performance in more complicated conditions. It combines two different types of queries (both simple and complex) generated concurrently. We’ve just published the performance results here (latencies, throughput, etc.). In this blog post, you’ll find some of the main findings.
An ability to easily extend core functionality is a key for any system’s evolution. Every popular config management or cloud orchestration tool offers a handy and effective way to do so. For instance, knife plugins in Chef, custom functions in Puppet, and terraform plugins. Being a complex tool, BOSH also provides out-of-the-box utilities for the purpose. The best option for extending BOSH functionality are plugins for a command-line interface (CLI). In fact, major part of the BOSH command-line utilities are implemented as BOSH plugins: the standard BOSH commands, MicroBOSH, BOSH AWS plugin, etc.
Unfortunately, there is no official documentation available on how to create a custom BOSH plugin by yourself, so I decided to compile such a tutorial. In this blog post, I provide guidelines on how to create a custom plugin for BOSH CLI to push the boundaries of the BOSH functionality and significantly boost resolution of application tasks.
Although monolithic architectures are prevalent today, they might not be the best fit for complex cloud-based systems—especially if you implement changes frequently. That’s where microservices enter the arena to overcome the challenges by splitting monoliths into multiple independent services, each with its own simple business logic. Still, choosing either PaaS or IaaS for microservices is an open question. Below is a table that demonstrates six major differences when implementing microservices on IaaS vs. PaaS (such as Cloud Foundry).
WATCH RECORDING OF LIVE STREAM:
Summary of the event
Nasser Manesh of Altiscale shared his experience with deploying multi-tenant Hadoop clusters using Docker. The talk covered the differences between containers and VMs, as well as addressed typical issues with containers, configuration, monitoring, troubleshooting, etc.
Dan Lorenc of Google explained when, why, and how to adopt Docker within your organization.
01/12 Meetup (Boston, MA): “Cloud Foundry in Production: Use Cases, Limitations, and Lessons Learned”
01/14 Meetup (New York, NY): “Cloud Foundry in Production: Use Cases, Limitations, and Lessons Learned”
01/14 Workshop (New York, NY): “Installing Cloud Foundry: How to Get Started Running Your Own PaaS” (3 hrs)
01/20 Meetup (Austin, TX): “New Ways to Deploy Cloud Foundry Using Juju Charms. Cloud Foundry in Production.”
Related paper: “Hadoop Distributions: Cloudera vs. Hortonworks vs. MapR“
In this blog post, you’ll find a technical overview of Admin UI, a Web service that allows to gather metrics from the Cloud Foundry components. I’ve shed some light on its core layers, featured functionality, integration with CF APIs, etc. You’ll also discover what issues you may face while logging in, scaling, and debugging—as well as how to address them.
Though the official Cloud Foundry documentation provides some general guidelines on how to create a buildpack, it does not demonstrate the in-depth behavior of scripts and how to test and debug buildpacks. In this post, I will try to fill in the missing gaps.
On Dec 17, the Cloud Foundry community will celebrate its achievements at the year-end party in Palo Alto. 10+ speakers will discuss the blueprints for the future of the CF Foundation and Cloud Foundry in the era of container-driven DevOps. Join the sessions I’ll take part in:
- 6:45–7:10 pm, Community Lightning Talks
- 7:35–7:45 pm, Lightning Panel: Will Docker Eat Cloud Foundry’s Lunch?
At the Lightning Panel together with James Watters of Pivotal, we will discuss the state of integration between Cloud Foundry and Docker; what Diego will and will not resolve when it comes to the growing tension between two darlings of the cloud; what is missing in an attempt to standardize the containers the POSIX-style; as well as other challenges and possible solutions.
We also wanted to hold a “Cloud Foundry 101″ workshop on Dec 18 (to help you learn how to deploy CF with BOSH-lite and create your first apps on CF), however for some tech reasons we need to move it to another date. Probably, either late December 2014 or January 2015. Sorry, guys, we’ll do our best to prepare for it as needed. As of now, we expect that Dave Nielsen, Cloud Computing Evangelist and Consultant, and Leandro Cacciagioni, Senior DevOps Engineer at Altoros, will help you to discover how Cloud Foundry solves the issues of portability, scalability, extensibility, and reliability. We’ll announce the new date very soon, track our updates at @altoros.
The launch of the Cloud Foundry Foundation is not only an important milestone for our community, but a defining moment for the future of many industries.
Altoros’s commitment to Cloud Foundry began as a way of helping an open source PaaS to become more consumable. One day, my colleague and I were showing what Cloud Foundry is to executives of a $4B pharmaceutical and medical device company. Little did we know that it could save thousands of human lives. These were the early days of what would become software-defined drug delivery.
This commitment resulted in Altoros deploying software assembly lines that help companies to re-invent their industries. To deploy the assembly lines, we leverage products and solutions offered by the Cloud Foundry ecosystem.
Cloud Foundry went through rounds of customer discovery and validation. It is seen both as an application delivery platform and a digital change agent. That is the magic of Cloud Foundry.
A lot has changed in the Juju orchestration tool and the Cloud Foundry Juju Charm, since our latest blog post about them. In this new post, I will overview the new features and provide two guides on installing CF, taking into account these updates. You will learn about:
- The new Cloud Foundry Juju charm implementation and some of its features
- How to deploy Cloud Foundry automatically with the latest CF Juju charm
- How to deploy Cloud Foundry manually using the config file
- How to customize your CF deployment by editing the config file
- How to upgrade CF with Juju
Join the upcoming East Bay meetup to learn when to use Docker, Diego, or Cloud Foundry and how to deploy Spring Boot-based Microservices with Docker—together with Chris Richardson, the founder of the original Cloud Foundry. In addition to Mr. Richardson’s presentation, I will speak about the opportunities that Diego brings to both Docker and Cloud Foundry users and likely scenarios of Docker evolution in clustered systems.