Cloud-Nativehttps://content.pivotal.io/cloud-native
Limitless, on-demand, pay-as-you-go computing power reduces costs and drives IT and business agility.en-USCloud-Native Security
Presented by Tsvi Korren, Aqua Security at DevSecOps 101: Containers, Clouds, and Apps in Boston on May 16th, 2019. https://content.pivotal.io/cloud-native/cloud-native-security-2
525659869Wed, 22 May 2019 14:46:27 -0400Jun 5 - Modern Cloud-Native Streaming Platforms: Event Streaming Microservices with Apache Kafka® on Kubernetes Webinar
<p>Join Michael Ng, Product Manager for Confluent, and Kamala Dasika, Product Marketing for Pivotal, to answer the questions of &lsquo;why cloud-native platforms&rsquo; and &lsquo;why run Apache Kafka on Kubernetes&rsquo;. They&rsquo;ll also share the types of workloads best suited for this combination, tips to determine the path forward for legacy apps and a demo running Apache Kafka as a streaming platform on Kubernetes.</p>
<p><a href="https://www.confluent.io/online-talks/modern-cloud-native-streaming-platforms?utm_source=pivotal&amp;utm_medium=partner-referral&amp;utm_campaign=kubernetes" target="_blank">Register Now</a></p>
https://content.pivotal.io/cloud-native/jun-5-modern-cloud-native-streaming-platforms-event-streaming-microservices-with-apache-kafka-on-kubernetes-webinar
525352660Tue, 21 May 2019 13:34:18 -0400Amy WelchPathway to Cloud-Native .NET
Presented at Speed and Scalability: Winning with Software in Today's Modern Economy in Cleveland on May 2nd, 2019. https://content.pivotal.io/cloud-native/pathway-to-cloud-native-net
522161503Thu, 09 May 2019 16:41:03 -0400How Pivotal Training and Certification Can Make a Difference for You
Pivotal Education enables you to continuously deliver business value in a rapidly evolving market by providing the modern software expertise you need to excel in a cloud-native world.
In this webina https://content.pivotal.io/cloud-native/how-pivotal-training-and-certification-can-make-a-difference-for-you
517766581Tue, 23 Apr 2019 17:32:35 -0400A Bootiful Podcast: Pivotal Field CTO and OG Cloud Native Matt Stine on Architecture
<p><p>Hi Spring fans! Welcome to another installment of a Bootiful Podcast. In this episode, recorded in lovely Johannesburg, South Africa for the SpringOne Tour event, I&rsquo;m joined by my buddy and one of the original cloud natives, Matt Stine!</p>
<ul><li><a href="http://twitter.com/mstine">Matt&rsquo;s Twitter (@mstine)</a></li>
</ul><iframe width="100%" height="300" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/607633950%3Fsecret_token%3Ds-89CQm&amp;color=%23ff5500&amp;auto_play=false&amp;hide_related=false&amp;show_comments=true&amp;show_user=true&amp;show_reposts=false&amp;show_teaser=true&amp;visual=true"></iframe></p> https://content.pivotal.io/cloud-native/a-bootiful-podcast-pivotal-field-cto-and-og-cloud-native-matt-stine-on-architecture
516505606Thu, 18 Apr 2019 21:01:00 -0400Josh LongMay 21 - Maturing Your Cloud-Native Platform for Security and Resilience Webinar (APJ)
<p><script src="https://www.brighttalk.com/clients/js/player-embed/player-embed.js" class="jsBrightTALKEmbed"> { "channelId" : 14883, "commid" : 356095
,"height" : "auto", "width" : "100%", "displayMode" : "standalone" } </script></p>
<p>&nbsp;</p> https://content.pivotal.io/cloud-native/may-21-maturing-your-cloud-native-platform-for-security-and-resilience-webinar
516112603Wed, 17 Apr 2019 13:02:32 -0400Amy Welch.NET Cloud-Native Bootcamp
Slides from the .NET Cloud-Native Bootcamp, hosted by Pivotal, Microsoft, and Magenic in New York and New Jersey on April 9th & 11th, 2019. https://content.pivotal.io/cloud-native/net-cloud-native-bootcamp
515638366Mon, 15 Apr 2019 20:11:25 -0400Metric Store: A Cloud-Native Time Series Database for Cloud Foundry
<p dir="ltr"><a href="https://www.cloudfoundry.org/">Cloud Foundry</a> strives to simplify operational tasks for the application developer whenever possible.</p>
<p>For example, Cloud Foundry (CF) makes application deployment and application monitoring relatively trivial for developers. Self-service access to telemetry is a big part of this convenience. CF serves up logs, events, and metrics so developers can better understand the health of their app.</p>
<p>This experience within CF has gotten even better recently with the addition of the <a href="https://github.com/cloudfoundry/log-cache">Log Cache</a>, an in-memory firehose cache.</p>
<p>Today, we are pleased to announce a new feature that even further improves the access to telemetry: <a href="https://github.com/cloudfoundry/metric-store-release">Metric Store</a>, a time-series database for Cloud Foundry. Let&rsquo;s talk about how this new capability improves on the idea behind Log Cache, and ultimately, the developer experience.</p>
<p>When we initially released Log Cache, one of the most frequent user requests was a longer cache duration and durability across VM restarts. We addressed some of those desires with more VMs and more memory. But we quickly understood that the community was asking for a different product altogether. When we continued hearing requests for persistence, compression, and a robust query interface, it became clear that what they really wanted was a time series database.</p>
<p>Metric Store features the auth model from Log Cache, the PromQL API from Prometheus, and the <a href="https://docs.influxdata.com/influxdb/v1.7/concepts/storage_engine/">Time-Structured Merge storage engine</a> from InfluxDB. After mixing this all together, we created Metric Store, a new component that persists all metrics from the Cloud Foundry Loggregator pipeline on its disk.</p>
<p>Here are three things you need to know about this new data store:</p>
<ol>
<li dir="ltr">
<p dir="ltr"><strong>It&rsquo;s multi-tenant aware. </strong>You only have access to metrics from your apps.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>It&rsquo;s easy to query. </strong>Metric Store is 100% compatible with the Prometheus API.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>It has a powerful storage engine. </strong>The InfluxDB storage engine has built-in compression and a memory-efficient series index.</p>
</li>
</ol>
<p>Install Metric Store, and you&rsquo;ll get a single VM to ingest all the counter and gauge metrics from the Loggregator Reverse Log Proxy. And you&rsquo;ll be able to query them immediately using the PromQL HTTP API.</p>
<p>Metric Store is now available for open source users of Cloud Foundry. You can deploy a single-node Metric Store with the BOSH release on the official <a href="https://bosh.io/releases/github.com/cloudfoundry/metric-store-release?all=1">BOSH release registry</a>. The <a href="https://github.com/cloudfoundry/metric-store-release">code is up on GitHub</a>.</p>
<p>We are also exploring a commercial version for use with <a href="https://pivotal.io/platform">Pivotal Cloud Foundry</a>. We can imagine that some customers might be interested in multi-node deployments, data replication, hinted handoff, and load balancing in a highly-available configuration. (We&rsquo;re exploring how Metric Store might work for Kubernetes as well.)</p>
<p>Now you know how Metric Store improves app observability in Cloud Foundry. Let&rsquo;s examine how it works.</p>
<h2 dir="ltr">An Inside Look at Metric Store</h2>
<p dir="ltr">Metric Store is composed of four processes:</p>
<ol>
<li dir="ltr">
<p dir="ltr">The <strong>Nozzle</strong> connects to the RLP and provides filtered and formatted data to Metric Store.</p>
</li>
<li dir="ltr">
<p dir="ltr">The <strong>Gateway</strong> is a gRPC to JSON converter that allows incoming HTTPS queries from GoRouter.</p>
</li>
<li dir="ltr">
<p dir="ltr">The <strong>Auth Proxy</strong>&nbsp;takes in valid PromQL queries and filters access based on user-provided UAA tokens.</p>
</li>
<li dir="ltr">
<p dir="ltr">And finally, <strong>Metric Store</strong> is responsible for data storage and query processing.</p>
</li>
</ol>
<p>This diagram shows how they all fit together:</p>
<p dir="ltr"><img alt="" src="https://content.cdntwrk.com/files/aHViPTYzOTc1JmNtZD1pdGVtZWRpdG9yaW1hZ2UmZmlsZW5hbWU9aXRlbWVkaXRvcmltYWdlXzVjYWU0OWJiNWUzZTIucG5nJnZlcnNpb249MDAwMCZzaWc9Y2ViYjZhZjRjNTIxYjlmOGRhYjJiOTUwMjIyYjBkMDQ%253D" /></p>
<p>With the exception of Metric Store itself, most of the other components are very similar to their counterparts in Log Cache. There were some additions made to the Auth Proxy to allow expanded PromQL support. But otherwise very little has changed.</p>
<p>The Metric Store process is where the magic happens. As mentioned above, we made the decision to use the InfluxDB storage engine for data persistence. This delivers great read and write performance in addition to native compression. We are also using the new <a href="https://docs.influxdata.com/influxdb/v1.7/concepts/time-series-index/">TSI index format</a>, which provides a tremendous reduction in the memory needed to store high-cardinality data. Additionally, on-disk shards span one day, so it&rsquo;s easy to truncate an entire day of data when it reaches the <a href="https://github.com/cloudfoundry/metric-store-release/blob/develop/jobs/metric-store/spec#L31-L33">user-configurable retention period</a>.</p>
<p>The storage engine features a flexible query interface, which in turn simplified the implementation of the PromQL query parser. The end result is a full-featured <a href="https://prometheus.io/docs/prometheus/latest/querying/api/">PromQL API</a>. That means Metric Store can operate with other Prometheus-compatible tools, such as <a href="https://grafana.com/">Grafana</a>.</p>
<h2 dir="ltr">How to Deploy Metric Store with Cloud Foundry</h2>
<p dir="ltr">Want to test Metric Store with an open-source Cloud Foundry installation? You can use the <a href="https://github.com/cloudfoundry/metric-store-release/blob/master/manifests/ops-files/add-metric-store-to-cfd.yml">operations file</a> available in the Metric Store release. We recommend you deploy this along cf-deployment. It will provide you with a metric store that is available at <code>https://ossms.SYSTEM_DOMAIN</code>. It will automatically ingest all application metrics and platform metrics.</p>
<p>Check out the <a href="https://github.com/cloudfoundry/metric-store-release/blob/master/README.md">readme of the metric-store-release</a> repository for additional details and useful information.</p>
<p dir="ltr">Once you have Metric Store up and running, you can start using it for application or platform monitoring. In the following example, we explain the basics of the Prometheus Query language. Then, we show the power of the Metric Store with the help of a few sample use cases.</p>
<h3 dir="ltr">The Basics</h3>
<p dir="ltr">The Prometheus Query Language allows you to query for a metric, and then filter the results by tag. (See <a href="https://prometheus.io/docs/prometheus/latest/querying/basics/#instant-vector-selectors">here</a> for more details). For example, when you want to see the current CPU consumption of the third instance of your app, you can use the following query:</p>
<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;"><code>cpu{source_id=APP_GUID,instance_index=3}</code></div>
<p>You can also get past data. If you are interested memory consumption of the same app instance over the last 3 hours, you can modify the above query like this:</p>
<div style="background:#eee;border:1px solid #ccc;padding:5px 10px;"><code>memory{source_id=APP_GUID,instance_index=3}[3h]</code></div>
<p><span style="color: rgb(85, 85, 85); font-size: 22px; font-weight: 700;">Use Case: Find all apps that in average used less than 25% of their allocated memory over the last six hours</span></p>
<p>Imagine you want to create a list of apps that don&rsquo;t use their allocated memory efficiently. You could downscale these apps to save money. You can run the following query against Metric Store to identify the potential candidates for downscaling:</p>
<div dir="ltr" style="background:#eee;border:1px solid #ccc;padding:5px 10px;"><code>curl -s -G -k -H &quot;Authorization: $(cf oauth-token)&quot; http://ossms.system.johannes.loggr.cf-app.com/api/v1/query --data- urlencode &nbsp;&quot;query=avg(avg_over_time(memory[5m])) by (source_id) / avg(avg_over_time(memory_quota[5m])) by (source_id) &lt; 0.25&quot; |&nbsp; jq &nbsp;.</code></div>
<p>This query provides a result like the following, which identifies overscaled applications with their application GUID&nbsp;and their current memory consumption.</p>
<div dir="ltr" style="background:#eee;border:1px solid #ccc;padding:5px 10px;">
<pre>
<code>{
&nbsp;&quot;status&quot;: &quot;success&quot;,
&nbsp;&quot;data&quot;: {
&nbsp;&nbsp;&nbsp;&quot;resultType&quot;: &quot;vector&quot;,
&nbsp;&nbsp;&nbsp;&quot;result&quot;: [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;metric&quot;: {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;source_id&quot;: &quot;a44b33e4-82dd-4566-9814-8b23a42a4558&quot;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;value&quot;: [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1553836160.157,
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;0.07624240294098855&quot;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;]
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;metric&quot;: {
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;source_id&quot;: &quot;184487e6-0153-4162-b30c-f9c1b72d9dcd&quot;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;},
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;value&quot;: [
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1553836160.157,
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&quot;0.062369791418313975&quot;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;]
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;]
&nbsp;}
}
</code></pre>
</div>
<p><em>Note: You have to have admin privileges to run this query.</em></p>
<h2 dir="ltr">What&rsquo;s Next for Metric Store</h2>
<p dir="ltr">Next up for Metric Store: operability enhancements. As part of that, we are improving the monitoring aspects of the Metric Store, and adoption of the <a href="https://github.com/pivotal/monitoring-indicator-protocol">Monitoring Indicator Protocol</a>. We also plan to continue to explore the commercial version, with enhanced replication and scaling capabilities. We&rsquo;re also looking at how this feature might be used with Kubernetes. After that, we want to add support for recording rules and ingestion of Prometheus-compatible scraping endpoints.</p>
<h2 dir="ltr">Tell Us What You Think!</h2>
<p>If you have any questions, comments, or thoughts about the new Metric Store, we would love to hear from you. You can find us in the <a href="https://cloudfoundry.slack.com/messages/CHB7BCZS8/details/">#metric-store channel</a> of the Cloud Foundry Slack. Also, feel free to open an issue in <a href="https://github.com/cloudfoundry/metric-store-release">our Github repository</a>.</p>
<p dir="ltr"><span style="font-size: 15px; line-height: 0; position: relative; vertical-align: baseline; bottom: -0.25em;"><span style="font-weight: 700;">SAFE HARBOR STATEMENT</span></span></p>
<p dir="ltr"><span style="font-size: 15px; line-height: 0; position: relative; vertical-align: baseline; bottom: -0.25em;">This blog contains statements relating to Pivotal&rsquo;s expectations, projections, beliefs and prospects which are &quot;forward-looking statements&rdquo; within the meaning of the federal securities laws and by their nature are uncertain. Words such as &quot;believe,&quot; &quot;may,&quot; &quot;will,&quot; &quot;estimate,&quot; &quot;continue,&quot; &quot;anticipate,&quot; &quot;intend,&quot; &quot;expect,&quot; &quot;plans,&quot; and similar expressions are intended to identify forward-looking statements. Such forward-looking statements are not guarantees of future performance, and you are cautioned not to place undue reliance on these forward-looking statements. Actual results could differ materially from those projected in the forward-looking statements as a result of many factors, including but not limited to: (i) our limited operating history as an independent company, which makes it difficult to evaluate our prospects; (ii) the substantial losses we have incurred and the risks of not being able to generate sufficient revenue to achieve and sustain profitability; (iii) our future success depending in large part on the growth of our target markets; (iv) our future growth depending largely on Pivotal Cloud Foundry and our platform-related services; (v) our subscription revenue growth rate not being indicative of our future performance or ability to grow; (vi) our business and prospects being harmed if our customers do not renew their subscriptions or expand their use of our platform; (vii) any failure by us to compete effectively; (viii) our long and unpredictable sales cycles that vary seasonally and which can cause significant variation in the number and size of transactions that can close in a particular quarter; (ix) our lack of control of and inability to predict the future course of open-source technologies, including those used in Pivotal Cloud Foundry; and (x) any security or privacy breaches. All information set forth in this release is current as of the date of this release. These forward-looking statements are based on current expectations and are subject to uncertainties, risks, assumptions, and changes in condition, significance, value and effect as well as other risks disclosed previously and from time to time in documents filed by us with the U.S. Securities and Exchange Commission (SEC), including our prospectus dated April 19, 2018, and filed pursuant to Rule 424(b) under the U.S. Securities Act of 1933, as amended. Additional information will be made available in our quarterly report on Form 10-Q and other future reports that we may file with the SEC, which could cause actual results to vary from expectations. We disclaim any obligation&nbsp;</span><span style="font-size: 15px; line-height: 0; position: relative; vertical-align: baseline; bottom: -0.25em;">to,</span><span style="font-size: 15px; line-height: 0; position: relative; vertical-align: baseline; bottom: -0.25em;">&nbsp;and do not currently intend to, update any such forward-looking statements, whether written or oral, that may be made from time to time except as required by law.</span></p>
<p dir="ltr"><span style="font-size: 15px; line-height: 0; position: relative; vertical-align: baseline; bottom: -0.25em;">This blog also contains statements which are intended to outline the general direction of certain of Pivotal&#39;s offerings. It is intended for information purposes only and may not be incorporated into any contract. &nbsp;Any information regarding the pre-release of Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal and is subject to change. All software releases are on an if and when available basis and are subject to change. This information is provided without warranty or any kind, express or implied, and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions regarding Pivotal&#39;s offerings. Any purchasing decisions should only be based on features currently available. &nbsp;The development, release, and timing of any features or functionality described for Pivotal&#39;s offerings in this blog remain at the sole discretion of Pivotal. Pivotal has no obligation to update forward-looking information in this blog.</span></p>
https://content.pivotal.io/cloud-native/metric-store-a-cloud-native-time-series-database-for-cloud-foundry
514206894Wed, 10 Apr 2019 17:49:26 -0400Todd PersenOvercoming the Cloud-Native Skills Shortage, with HCL's Alan Flower
<p><iframe allow="autoplay" frameborder="no" height="166" scrolling="no" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/603465027%3Fsecret_token%3Ds-e9QSP&amp;color=%2357c3bf&amp;auto_play=false&amp;hide_related=false&amp;show_comments=true&amp;show_user=true&amp;show_reposts=false&amp;show_teaser=true" width="100%"></iframe></p>
<p>Most enterprises start their cloud-native journeys with lots of enthusiasm and big plans. But reality often sets in when they try to scale transformations by modernizing hundreds, sometimes thousands of legacy apps. The biggest digital transformation roadblock? It&#39;s a lack of cloud-native skills, says HCL&#39;s Alan Flower. In this episode of Pivotal Conversations, Alan shares tips and strategies for overcoming the cloud-native skills gap.</p>
<h3>Show Notes</h3>
<ul dir="ltr">
<li>Visit&nbsp;<a href="http://pivotal.io/podcasts">http://pivotal.io/podcasts</a>&nbsp;for show notes and other episodes.</li>
<li><a href="https://soundcloud.com/pivotalconversations/overcoming-the-cloud-native-skills-shortage-with-hcls-alan-flower/s-e9QSP">Download the episode and check us out on Soundcloud</a>, subscribe to&nbsp;<a href="http://blog.pivotal.io/feed?channel=pivotal-conversations">the feed directly</a>, or on&nbsp;<a href="https://itunes.apple.com/us/podcast/pivotal-conversations/id1123116274?mt=2">iTunes</a>&nbsp;to have it automatically downloaded for you.</li>
<li>Twitter:&nbsp;<a href="https://twitter.com/jeffreyfkelly">@jeffreyfkelly</a>,&nbsp;<a href="https://twitter.com/DormainDrewitz">@dormaindrewitz</a>, <a href="https://twitter.com/hcltech">@hcltech</a></li>
<li>Feedback:&nbsp;<a href="mailto:podcast@pivotal.io?subject=Pivotal%20Insights%20feedback">podcast@pivotal.io</a></li>
</ul>
<h3>News &amp; Resources</h3>
<ul>
<li>Watch Alan&#39;s SpringOne Platform 2018 session on <a href="https://youtu.be/7XMo3NHz2ms">hitting the enterprises sweet spot with Pivotal Container Service</a>.</li>
<li>Hear about&nbsp;<a href="https://content.pivotal.io/slides/tried-and-true-approach-to-cloud-native-design-an-experienced-based-method">HCL&rsquo;s journey creating microservices and lessons learned along the way</a> with&nbsp;HCL&#39;s Rahul Kandhari.</li>
<li>Learn more about <a href="https://www.hcltech.com/about-us/alliances/pivotal">HCL&#39;s Pivotal practice and how its helping enterprises accelerate and scale their digital transformations</a>.</li>
</ul>
<p>&nbsp;</p>
https://content.pivotal.io/cloud-native/overcoming-the-cloud-native-skills-shortage-with-hcls-alan-flower
513867412Tue, 09 Apr 2019 17:54:57 -0400Jeff KellyCloud Native Buildpacks: an Industry-Standard Build Process for Kubernetes and Beyond.
<h3 dir="ltr">Cloud Native Buildpacks Unlock Developer Productivity</h3>
<p dir="ltr">If you want to make your developers more productive with Kubernetes, you&rsquo;re going to want to look at <a href="https://buildpacks.io/">Cloud Native Buildpacks</a>.</p>
<p dir="ltr">Cloud Native Buildpacks evolve a concept first pioneered by <a href="https://pivotal.io/">Pivotal</a> and <a href="https://www.heroku.com/">Heroku</a>. The big idea behind buildpacks? Building containers from source code should be completely automated.</p>
<center>
<blockquote class="twitter-tweet" data-lang="en">
<p dir="ltr" lang="en">[NEWS] <a href="https://twitter.com/CloudNativeFdn?ref_src=twsrc%5Etfw">@CloudNativeFdn</a> to Host <a href="https://twitter.com/hashtag/CloudNativeBuildpacks?src=hash&amp;ref_src=twsrc%5Etfw">#CloudNativeBuildpacks</a> in the Sandbox 🎉 <a href="https://t.co/aqHQqY5PMM">https://t.co/aqHQqY5PMM</a> <a href="https://t.co/AwQvDF7714">pic.twitter.com/AwQvDF7714</a></p>
&mdash; CNCF (@CloudNativeFdn) <a href="https://twitter.com/CloudNativeFdn/status/1047509105508868096?ref_src=twsrc%5Etfw">October 3, 2018</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></center>
<p>Why fiddle with containers built by hand, when you can just push your code and have the buildpack create the container for you? This way, you don&rsquo;t have to sweat the runtime dependencies. And it&rsquo;s push-button easy to update your container later. Just push your code, and buildpacks do the rest.</p>
<p dir="ltr">There&rsquo;s an operational and security benefit too. Buildpacks build apps in a consistent, repeatable way. This consistency makes it easy to audit and control what&rsquo;s running on your platform at any given time. You can assess your risk from a given CVE quickly, and remediate a patch moments later.</p>
<p dir="ltr">That&rsquo;s why buildpacks are so popular with high-velocity development teams. Buildpacks transform application source code into a portable artifact that can run on <a href="https://pivotal.io/platform/pivotal-application-service">Pivotal Application Service</a>, or the open-source <a href="https://www.cloudfoundry.org/application-runtime/">Cloud Foundry Application Runtime</a>.&nbsp;Since their&nbsp;<a data-saferedirecturl="https://www.google.com/url?q=https://urldefense.proofpoint.com/v2/url?u%3Dhttps-3A__blog.heroku.com_buildpacks%26d%3DDwMFaQ%26c%3Dlnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw%26r%3DvHjQyIWfYgL7j0k9boZf2VjXiwHlGWHS2xsetU-wMhI%26m%3DZooTFfaeRKeES11N4N-hXYPb4FOOX2ld1P7tw6eXKYs%26s%3DuySD9_jCIDyIVVX5GK7FrjXikdqpg5bSlZ_xSmFbWz4%26e%3D&amp;source=gmail&amp;ust=1554378940534000&amp;usg=AFQjCNF6LWlu0m70eBrGdkWcCgXKOM3oxQ" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.heroku.com_buildpacks&amp;d=DwMFaQ&amp;c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&amp;r=vHjQyIWfYgL7j0k9boZf2VjXiwHlGWHS2xsetU-wMhI&amp;m=ZooTFfaeRKeES11N4N-hXYPb4FOOX2ld1P7tw6eXKYs&amp;s=uySD9_jCIDyIVVX5GK7FrjXikdqpg5bSlZ_xSmFbWz4&amp;e=" target="_blank">introduction</a>,&nbsp;<a data-saferedirecturl="https://www.google.com/url?q=https://urldefense.proofpoint.com/v2/url?u%3Dhttps-3A__www.heroku.com_%26d%3DDwMFaQ%26c%3Dlnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw%26r%3DvHjQyIWfYgL7j0k9boZf2VjXiwHlGWHS2xsetU-wMhI%26m%3DZooTFfaeRKeES11N4N-hXYPb4FOOX2ld1P7tw6eXKYs%26s%3DKR8dJsuzDFrgpUgKrYUWoWHHBv7KwwbE9tRGjdchW6c%26e%3D&amp;source=gmail&amp;ust=1554378940534000&amp;usg=AFQjCNFYvtU6O5vG4YrhD24Ff2uPah9BTw" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.heroku.com_&amp;d=DwMFaQ&amp;c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&amp;r=vHjQyIWfYgL7j0k9boZf2VjXiwHlGWHS2xsetU-wMhI&amp;m=ZooTFfaeRKeES11N4N-hXYPb4FOOX2ld1P7tw6eXKYs&amp;s=KR8dJsuzDFrgpUgKrYUWoWHHBv7KwwbE9tRGjdchW6c&amp;e=" target="_blank">Heroku</a>&nbsp;<wbr />users have benefitted from the simplicity, usability, and flexibility of&nbsp;buildpacks&nbsp;across millions of production apps.</p>
<p dir="ltr">We want as many developers as possible to benefit from buildpacks. To this end, we teamed up with Heroku to create <a href="https://content.pivotal.io/blog/peace-of-mind-for-developers-and-operators-buildpacks-is-now-a-cncf-project-welcome-cloud-native-buildpacks">Cloud Native Buildpacks</a>.</p>
<p dir="ltr">&nbsp;</p>
<h2 dir="ltr">Cloud Native Buildpacks bring the power of buildpacks to Kubernetes</h2>
<p dir="ltr">The project aims to deliver a consistent platform-to-buildpack contract for use in more places. The interface defined by this contract is informed by learnings from maintaining production-grade buildpacks for years at both Pivotal and Heroku.</p>
<p dir="ltr">Today, the Cloud Native Buildpacks project is open for test/dev scenarios. The Cloud Foundry Buildpacks team <a href="https://hub.docker.com/r/cloudfoundry/cnb">has also released</a> a selection of next-gen Cloud Foundry buildpacks compatible with the new project. With this release you can try buildpacks out on <a href="https://pivotal.io/platform/pivotal-container-service">Pivotal Container Service</a> (PKS) and <a href="https://pivotal.io/platform/pivotal-application-service">Pivotal Application Service</a> (PAS). Some of this technology is already integrated into <a href="https://pivotal.io/platform/pivotal-function-service">Pivotal Function Service</a> (PFS) when functions are built using the <a href="https://projectriff.io/">riff</a> CLI.</p>
<p dir="ltr">Let&rsquo;s dig a little deeper into this tech. The best place to start? The current state of buildpacks.</p>
<p dir="ltr">&nbsp;</p>
<h2 dir="ltr">Buildpacks are fundamental to the Cloud Foundry &ldquo;Day 2&rdquo; experience</h2>
<p dir="ltr">Currently, buildpacks function &ldquo;under the hood&rdquo; within Cloud Foundry (CF).</p>
<p dir="ltr">When you <code>cf push</code> your custom code, buildpacks automatically add in the framework dependencies and create an application &ldquo;droplet&rdquo; that&rsquo;s ready to run on the platform. The droplet model allows Cloud Foundry to gracefully handle dependency updates. In-container OS package updates can be automatically performed for all the apps running on the platform without downtime or disruption. Application runtimes can be updated simply by pulling in the latest buildpacks and rebuilding a droplet. Buildpacks are a central component of the day-2 experience CF users love.</p>
<p dir="ltr">Now imagine an experience that expands on this idea, and builds an OCI image that can run on any platform? Locally, it might look something like this:</p>
<div dir="ltr" style="background:#eee;border:1px solid #ccc;padding:5px 10px;"><code>$ pack build&nbsp;myapp</code></div>
<p>That&rsquo;s Cloud Native Buildpacks. We believe developers will love the simplicity of this single command to get a production quality container when they prefer not to author and maintain their own Dockerfile.</p>
<p dir="ltr">Read on for more details.</p>
<p dir="ltr">&nbsp;</p>
<h2 dir="ltr">Cloud Native Buildpacks make a great idea even better</h2>
<p dir="ltr">While traditional buildpacks are wonderful, Cloud Native Buildpacks are a big step forward for the industry. Here&rsquo;s why:</p>
<ol>
<li dir="ltr">
<p dir="ltr"><strong>Portability via the OCI standard. </strong>Cloud Native Buildpacks produce OCI Images from source code. While the application droplet is tied to CF, <a href="https://github.com/opencontainers/image-spec">OCI images</a> are an open source container standard. This makes Cloud Native Buildpacks much more portable. Which is to say, they can be used by more abstractions like Kubernetes and Knative.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Greater modularity. </strong>Cloud Native Buildpacks are modular. Engineers can enjoy a higher degree of specificity in their buildpack configuration experience. More practically, this will allow platform operators more control over how developers build their code at runtime.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Speed. </strong>Cloud Native Buildpacks build exponentially faster due to advanced build caching, layer reuse, and data deduplication.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Faster troubleshooting.</strong> Cloud Native Buildpacks can be used in a developer&rsquo;s local environment. This helps troubleshoot production issues much faster.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Reproducible builds. </strong>Cloud Native Buildpacks enable reproducible container image builds.</p>
</li>
</ol>
<p>Sounds pretty good right? Now here&rsquo;s how you can get started.</p>
<p>&nbsp;</p>
<h2 dir="ltr">Get Started with Cloud Native Buildpacks</h2>
<p dir="ltr">Ready to take Cloud Native Buildpacks for a spin? You can work with Cloud Native Buildpacks locally using the <a href="https://github.com/buildpack/pack/">CLI (&lsquo;pack&rsquo;)</a>. Give it a try, and share your feedback with us on <a href="https://buildpacks.slack.com">Slack</a>.</p>
<p dir="ltr">You&rsquo;ll also want to check out the docs for a common demo scenario: <a href="https://buildpacks.io/docs/app-journey/">https://buildpacks.io/docs/app-journey</a>.</p>
<p dir="ltr">What does all this mean for Pivotal Cloud Foundry customers? We thought you might be curious about that.</p>
<p dir="ltr">&nbsp;</p>
<h2 dir="ltr">Up next: Making Cloud Native Buildpacks ready for the enterprise</h2>
<p dir="ltr">Cloud Native Buildpacks are wonderful tech. But like most open-source projects, it&rsquo;ll need some polish to be plug-and-play ready for enterprise scenarios. That&rsquo;s what Pivotal is exploring now. In fact, Pivotal is currently exploring three such scenarios: image promotion, operator control, and automated image patching. Let&rsquo;s take a deeper look at how each area could be addressed with a Pivotal build service. The features discussed below, and any other forward-looking features, will be deployed if and when available.</p>
<h3 dir="ltr">Image Promotion&mdash;No Rebuild Required</h3>
<p dir="ltr">The current CF app promotion process can be painful for developers. Today, developers must keep rebuilding the same droplet, a tedious process. Another pain point: underlying dependencies may not always align throughout the promotion process because apps may not be built using the same buildpack versions.&nbsp; Pivotal is exploring a build service with a more intelligent approach to image updating. In this new world, developers would be able to promote images through environments, and eventually, across PCF foundations.</p>
<h3 dir="ltr">Automated Image Updates Makes Developers More Productive</h3>
<p dir="ltr">Pivotal is also exploring a declarative configuration model. Tell the build service what you want your app to look like. Then, it would deliver new images to your registry whenever this configuration falls out of sync. If a new CVE is announced, new buildpack versions are made available and new images are built.</p>
<h4 dir="ltr">Operator Control</h4>
<p dir="ltr">A useful build service would provide tighter operator control by restricting buildpack usage in the apps they supervise.</p>
<p dir="ltr">With a build service, operators could create build configurations for different groups of developers within the organization. These configurations would govern the buildpacks that any given dev is allowed to use. This is a better experience for operators; they can be more confident that their apps use secure, compliant dependencies. Developers would not have to worry about what they can, and can&#39;t, use. Instead, they would just focus on their source code.</p>
<p dir="ltr">&nbsp;</p>
<h2 dir="ltr">To Remove Toil, Use Cloud Native Buildpacks</h2>
<p dir="ltr">The best developers strive to eliminate toil from their lives. These engineers figure that if a task doesn&rsquo;t add value, it should be automated so you don&rsquo;t ever have to think about it again. With Cloud Native Buildpacks, developers can happily remove that much more toil from their jobs.</p>
<p dir="ltr">&nbsp;</p>
<p dir="ltr"><sub><strong>SAFE HARBOR STATEMENT</strong></sub></p>
<p dir="ltr"><sub>This blog contains statements relating to Pivotal&rsquo;s expectations, projections, beliefs and prospects which are &quot;forward-looking statements&rdquo; within the meaning of the federal securities laws and by their nature are uncertain. Words such as &quot;believe,&quot; &quot;may,&quot; &quot;will,&quot; &quot;estimate,&quot; &quot;continue,&quot; &quot;anticipate,&quot; &quot;intend,&quot; &quot;expect,&quot; &quot;plans,&quot; and similar expressions are intended to identify forward-looking statements. Such forward-looking statements are not guarantees of future performance, and you are cautioned not to place undue reliance on these forward-looking statements. Actual results could differ materially from those projected in the forward-looking statements as a result of many factors, including but not limited to: (i) our limited operating history as an independent company, which makes it difficult to evaluate our prospects; (ii) the substantial losses we have incurred and the risks of not being able to generate sufficient revenue to achieve and sustain profitability; (iii) our future success depending in large part on the growth of our target markets; (iv) our future growth depending largely on Pivotal Cloud Foundry and our platform-related services; (v) our subscription revenue growth rate not being indicative of our future performance or ability to grow; (vi) our business and prospects being harmed if our customers do not renew their subscriptions or expand their use of our platform; (vii) any failure by us to compete effectively; (viii) our long and unpredictable sales cycles that vary seasonally and which can cause significant variation in the number and size of transactions that can close in a particular quarter; (ix) our lack of control of and inability to predict the future course of open-source technologies, including those used in Pivotal Cloud Foundry; and (x) any security or privacy breaches. All information set forth in this release is current as of the date of this release. These forward-looking statements are based on current expectations and are subject to uncertainties, risks, assumptions, and changes in condition, significance, value and effect as well as other risks disclosed previously and from time to time in documents filed by us with the U.S. Securities and Exchange Commission (SEC), including our prospectus dated April 19, 2018, and filed pursuant to Rule 424(b) under the U.S. Securities Act of 1933, as amended. Additional information will be made available in our quarterly report on Form 10-Q and other future reports that we may file with the SEC, which could cause actual results to vary from expectations. We disclaim any obligation </sub><sub>to,</sub><sub> and do not currently intend to, update any such forward-looking statements, whether written or oral, that may be made from time to time except as required by law.</sub></p>
<p dir="ltr"><sub>This blog also contains statements which are intended to outline the general direction of certain of Pivotal&#39;s offerings. It is intended for information purposes only and may not be incorporated into any contract. &nbsp;Any information regarding the pre-release of Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal and is subject to change. All software releases are on an if and when available basis and are subject to change. This information is provided without warranty or any kind, express or implied, and is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions regarding Pivotal&#39;s offerings. Any purchasing decisions should only be based on features currently available. &nbsp;The development, release, and timing of any features or functionality described for Pivotal&#39;s offerings in this blog remain at the sole discretion of Pivotal. Pivotal has no obligation to update forward-looking information in this blog.</sub></p>
https://content.pivotal.io/cloud-native/cloud-native-buildpacks-for-kubernetes-and-beyond
512155330Wed, 03 Apr 2019 00:13:00 -0400Emily CaseyTop Five Reasons Your Business Needs a Cloud-Native Strategy
Enter content here https://content.pivotal.io/cloud-native/top-five-reasons-your-business-needs-a-cloud-native-strategy
504746417Sun, 03 Mar 2019 16:22:11 -0500Improving the DevOps Metrics that Matter with Cloud Native Patterns
<p dir="ltr">I&rsquo;m a glass-half-full kind of person. When I hear the real-life stories of complex, treacherous paths to production (with inevitable delays, failures and fire drills), I tend to think <em>&ldquo;OMG, what potential!&rdquo;</em> If you&rsquo;re like most organizations, you have so much upside by transforming how you deliver software. But it <em>is</em> a journey&mdash;not a destination. It&rsquo;s about setting goals and doing the work. Along the way, you should track your progress, and measure yourself against your peers and industry benchmarks, refining and improving as you go.</p>
<p dir="ltr">One essential benchmark is the <a href="https://cloudplatformonline.com/2018-state-of-devops.html">Accelerate: State of DevOps</a>. It&rsquo;s the longest-running research on software delivery performance. It can validate your progress and help you set goals for improvement around the delivery metrics that matter: throughput, stability, and availability. And if you&rsquo;re that company thinking your glass is half empty, this report can give you hope.</p>
<p dir="ltr">In a <a href="https://www.brighttalk.com/webcast/14891/332828/the-accelerate-state-of-devops-report">Pivotal webinar covering findings from the State of DevOps</a> report, lead author Nicole Forsgren made the ultimate positive statement:</p>
<blockquote>
<p dir="ltr"><em>&ldquo;High performance is available for everyone.... Anyone can do this.&rdquo;</em></p>
</blockquote>
<p>She&rsquo;s confident in that because she&rsquo;s seen the numbers. In the 2018 report, there are more high performers in all industries. In fact, 48% of respondents were categorized as high performers. The growing number of high performers led the authors to carve out an &lsquo;elite&rsquo; group in order to distinguish those really pushing the boundaries.</p>
<p dir="ltr">A new finding for the 2018 report is that those most adept at cloud computing were very likely to be among that elite group. As an example, platform-as-a-service users were 1.5 times more likely to be elite performers.</p>
<p dir="ltr">In the spirit of positive reinforcement with real-world data, I wanted to take a look at how you can improve in the three metric areas discussed in the report (throughput, stability, and availability). I&rsquo;ll bring in some data points for how companies are leading the way for each area of measurement. And I&rsquo;ll share some recommendations on how cloud-native approaches combined with continuous delivery best practices can help you see results.</p>
<h2 dir="ltr">Metric One: Throughput</h2>
<p dir="ltr">Companies can measure the speed and efficiency of delivering value (whether that&rsquo;s a new feature or a bug fix) to their customers in a number of ways. In the State of DevOps report, the authors focus on throughput metrics, which include:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><strong>Lead time for the change:</strong> how long it takes from code commit to production run</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Deployment frequency:</strong> how often you deploy to production</p>
</li>
</ul>
<p dir="ltr">You could also include metrics around &ldquo;developer work&rdquo;&mdash;producing smaller, modular batches of deployable code more often. After all, if development is not agile, then your delivery certainly won&rsquo;t be.</p>
<p dir="ltr">Pivotal customers have demonstrated some remarkable results around speed to market:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><a href="https://www.altoros.com/blog/csaa-deploys-three-times-a-day-with-cloud-foundry/">CSAA Insurance</a> experienced a 205 percent increase in developer productivity and increased deployment frequency by 1,400 percent.</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/videos/crossing-the-ci-cd-devops-chasm-miranda-leblanc?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">Liberty Mutual</a> reported that it is deploying 1,000 times a day to production on 2,500 daily builds across 600 production apps.</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/videos/day-2-keynote-lauren-knausenberger-and-bryon-kroger?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">United States Air Force</a> increased release frequency to 30.5 releases per month.&nbsp;&nbsp; &nbsp;</p>
</li>
</ul>
<p>How do organizations achieve these types of results? The actual work of improving throughput can include:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><strong>Self-serve developer experience</strong>&mdash;It starts with the code. Do developers have easy access to the libraries and services they need to create <a href="https://pivotal.io/cloud-native?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">cloud-native apps</a>? Your team will also need to automate their build and test process through <a href="https://pivotal.io/concourse/developers?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">continuous integration (CI)</a> and have instant access to development and test environments that are at parity with production.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>End-to-end automated CI/CD pipeline</strong>&mdash;Automating every facet of delivery, from development hand-off to production, is critical. Are you automating deployments and testing? Do you automate time-intensive tasks like feedback notifications and change tickets? Through a visible end-to-end pipeline, Dev and Ops teams can work together to get code to staging and production several times a day.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Shift-left testing, database changes, security scans</strong>&mdash;Does your pipeline stall waiting for testing, the DB team, or the security team? Do you attend change review meetings? You should integrate and automate these activities in your delivery pipeline. This way, they can be done earlier and in parallel to other activities. The end result: you avoid manual hand-overs and delay.</p>
</li>
</ul>
<p dir="ltr" style="text-align: center;"><img alt="" src="https://content.cdntwrk.com/files/aHViPTYzOTc1JmNtZD1pdGVtZWRpdG9yaW1hZ2UmZmlsZW5hbWU9aXRlbWVkaXRvcmltYWdlXzVjNzZmYzczZTJlMGIuanBnJnZlcnNpb249MDAwMCZzaWc9MjNiMjQxYjRlYWNmMGZmZmE1MTliMDIyNTEwZjE0NGY%253D" /></p>
<p dir="ltr" style="text-align: center;"><em>An example of an automated CI/CD Pipeline Using <a href="https://pivotal.io/concourse">Concourse</a>.</em></p>
<h2 dir="ltr">Metric Two: Stability&nbsp;</h2>
<p dir="ltr">As your team speeds up software delivery, they can also reduce errors and remediate faster. Does this conclusion surprise you? It shouldn&rsquo;t.</p>
<p dir="ltr">The State of DevOps report shows that as high performers increase their speed, they simultaneously improve their stability. The report measures stability through two metrics: <strong>mean time to repair</strong> (MTTR) and <strong>change failure rate</strong> (changes that degrade service to the point of remediation or that cause failure).</p>
<p dir="ltr">What does this look like in the real world? Here are a few instructive case studies:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/videos/numbers-in-the-hidden-a-pragmatic-view-of-nirvana?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">Cerner Healthcare</a> was able to recover from a production cell loss in 5-15 minutes with zero humans involved. This previously would have taken them 6-8 hours and four humans.&nbsp;&nbsp; &nbsp;</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://www.youtube.com/watch?v=pfqSsjwCOqA">Comcast</a> reduced incident frequency by 44 percent and MTTR by 47 percent, which amounted to an 81 percent decrease in customer-facing downtime.</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/videos/zero-to-12-million-brendan-aye?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">T-Mobile</a> reduced product defect incident frequency by 83 percent and reduced incident resolution time by 67 percent (going from 340 minutes to 112 minutes to resolve).</p>
</li>
</ul>
<p dir="ltr">What drives software stability?</p>
<ul>
<li dir="ltr">
<p dir="ltr"><strong>Cloud-native architecture</strong>&mdash;Are you sitting on a complex, monolithic application portfolio with a mandate to move to the cloud? You can start by <a href="https://pivotal.io/application-transformation?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">replatforming</a> suitable applications to run on the cloud. But to take full advantage of cloud infrastructure, you must modernize those monoliths as loosely coupled, lightweight microservices that follow <a href="https://12factor.net/">12-factor principles</a>.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Bullet-proofed CI/CD pipeline</strong>&mdash;Make your pipeline the standard, reliable path to production. It starts with automating the manual tasks in your application delivery process to remove human error. Does your pipeline include integrations with process checks, approval gates, and final artifact testing? All of these steps validate production readiness. Are your pipelines declarative (&ldquo;as code&rdquo;) for easier traceability, version control, and remediation? They should be!</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Immutable, always secure infrastructure</strong>&mdash;Are you worried that your servers are behind on security patching? If you&rsquo;re not applying patches as soon as they are issued, your systems and customer data are at risk. With an automated patching process, you can sleep that much easier at night. You can use deployment automation to regularly &ldquo;repave&rdquo; your infrastructure during business hours to fight against advanced persistent threats. By deploying new infrastructure every time you deploy a new application, deployments are more reliable and predictable. You can be more confident in your releases.</p>
</li>
</ul>
<h2 dir="ltr">Metric Three: Availability</h2>
<p dir="ltr">Availability is a new area of measurement in the State of DevOps report for 2018. It&rsquo;s a recognition that the ultimate marker of software delivery performance is that users can reliably access an application or service.</p>
<p dir="ltr">Of course, metrics like <strong>availability</strong> open the door to thinking about software delivery through an operational lens. After all, continuous delivery is never really done. Production provides valuable insights for improving the customer experience.</p>
<p dir="ltr">Pivotal customers really excel at keeping software available to their users, measured in areas of application scaling and downtime in particular:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><a href="https://www.youtube.com/watch?v=pfqSsjwCOqA">Comcast</a> reduced the time to scale their application by 90 percent and increased their number of transactions by 238 percent.</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/springone-platform-2018/day-3-keynote-siew-choo-soh&amp;utm_medium=blog&amp;utm_campaign=blog">DBS</a> has experienced zero downtime in production over the past 2.5 years.</p>
</li>
<li dir="ltr">
<p dir="ltr"><a href="https://content.pivotal.io/videos/automation-and-culture-changes-for-40m-subscriber-platform-operation&amp;utm_medium=blog&amp;utm_campaign=blog">Yahoo Japan Technology</a> reports zero downtime in production with PCF.&nbsp;&nbsp; &nbsp;</p>
</li>
</ul>
<p>How do you deliver availability and accessibility for your customers? These practices can help:</p>
<ul>
<li dir="ltr">
<p dir="ltr"><strong>Low-risk deployment strategies</strong>&mdash;Start your applications off right by de-risking the cut-over to live production with <a href="https://content.pivotal.io/blog/create-customer-value-like-faang-continuous-delivery-via-spinnaker&amp;utm_medium=blog&amp;utm_campaign=blog">deployment strategies</a> that gently move applications into full production run. Are you leveraging automated blue/green and canary deployments to minimize risk and downtime? Are you able to roll-back automatically when a deployment does not succeed? Use safe deployment strategies to increase confidence and reduce risk. This approach boosts your throughput while offering a path to continuous deployment when you&rsquo;re ready.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>High-availability (HA) by design</strong>&mdash;Does your infrastructure include redundancies? How does your stack handle failure at the availability zone, VM, application and process level? How do you monitor and manage the health of your services? Redundancy and distribution minimize downtime during ongoing operation, security updates, and platform upgrades.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Dynamically scalable applications</strong>&mdash;Scaling up or down without disruption keeps everyone happy&mdash;especially during peak traffic times. Can you automatically scale up to handle a big traffic event? Can you automatically scale back down to save costs? Having an elastic infrastructure, based on thresholds you set, helps keep your apps online in the face of unpredictable traffic.</p>
</li>
</ul>
<h2 dir="ltr">Don&rsquo;t Forget Culture: The Leading Indicator of DevOps Performance</h2>
<p dir="ltr">Tools and tech are essential to becoming a high performer in software delivery, but <a href="https://content.pivotal.io/blog/containers-tech-digital-transformation&amp;utm_medium=blog&amp;utm_campaign=blog">culture is perhaps the most important</a> element. While it may be harder to define a clear measure for culture, there are many indicators of what drives a happier, more productive culture.</p>
<p dir="ltr">For example the <a href="https://cloudplatformonline.com/2018-state-of-devops.html">State of DevOps</a> report talks about outsourcing as an anti-pattern to high performance, because of added overhead and greater functional divide. Instead, <a href="https://pivotal.io/agile">cross-functional teams and agile practices</a> are correlated with better performance.</p>
<p dir="ltr">It&rsquo;s also clear that implementing <a href="https://pivotal.io/cicd">continuous delivery</a> (defined in the report as &ldquo;Technical practices in delivery and deployment that reduce the risk and cost of performing releases&rdquo;) boosts team morale and performance improvement. Better visibility across teams and faster feedback loops can help break down silos.</p>
<h2 dir="ltr">Let&rsquo;s Get Started</h2>
<p dir="ltr">We&rsquo;ve helped organizations like yours transform how they develop and deliver software. Here are some suggestions on how to get started:</p>
<ol>
<li dir="ltr">
<p dir="ltr"><strong>Whiteboard session with apps and ops teams. </strong>Here, we explore the areas of impact as part of a <a href="https://pivotal.io/labs">Pivotal Labs engagement</a>. What parts of your application portfolio or process need the most improvement?</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Get an application running on a modern platform.</strong> Remember those monolithic apps we mentioned? Let&rsquo;s start a quick project to decompose it, and get it up and running on <a href="http://pivotal.io/platform">Pivotal Cloud Foundry</a>. This is an <a href="https://pivotal.io/application-transformation">Application Transformation engagement</a>. Here, we help you realize greater throughput, stability, and availability, and show you proof of what&rsquo;s possible.</p>
</li>
<li dir="ltr">
<p dir="ltr"><strong>Value stream assessment.</strong> What does your path to production look like today? Where are blocks and inefficiencies? Let&rsquo;s analyze your status quo, and make a plan to get better. <a href="https://content.pivotal.io/white-papers/crossing-the-value-stream-improving-development-with-pivotal-and-cloud-foundry?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">Read the whitepaper</a>.</p>
</li>
</ol>
<p dir="ltr">Let us help you <a href="https://pivotal.io/contact?utm_source=blog&amp;utm_medium=blog&amp;utm_campaign=blog">get started</a> on achieving your DevOps performance goals today.</p>
<p><img alt="" src="https://content.cdntwrk.com/files/aHViPTYzOTc1JmNtZD1pdGVtZWRpdG9yaW1hZ2UmZmlsZW5hbWU9aXRlbWVkaXRvcmltYWdlXzVjNzZmYzU1MDE5ODgucG5nJnZlcnNpb249MDAwMCZzaWc9NmE2ZWRhMmQwNWUyYmY4ZmExMmVlZjRjZDNlMWFkY2I%253D" /></p>
<p dir="ltr" style="text-align: center;"><em>Deliver Cloud Native Software with Pivotal</em></p>
<div>&nbsp;</div>
https://content.pivotal.io/cloud-native/improving-the-devops-metrics-that-matter-with-cloud-native-patterns
503788418Thu, 28 Feb 2019 14:06:22 -0500Patricia JohnsonFeb 20 - Cloud-Native Security: Processes and Tools for Real-World Transformation Webinar
<p><script src="https://www.brighttalk.com/clients/js/player-embed/player-embed.js" class="jsBrightTALKEmbed"> { "channelId" : 14883, "commid" : 348286
,"height" : "auto", "width" : "100%", "displayMode" : "standalone" } </script></p>
<p>&nbsp;</p>
https://content.pivotal.io/cloud-native/feb-20-cloud-native-security-processes-and-tools-for-real-world-transformation-webinar
496724424Tue, 29 Jan 2019 14:27:28 -0500Amy WelchFeb 7 - How to Ensure the Performance of Your Cloud-Native Apps Webinar
<p>Join Jon Hodgson, Principal Scientist of Riverbed Technology, and Koundinya Srinivasa Rao, Senior Platform Architect of Pivotal, to learn why you should be putting big data and automation at the core of your cloud-native strategy.</p>
<p><a href="https://www.riverbed.com/forms/webinars/how-to-ensure-the-performance-of-your-cloud-native-apps.html?utm_source=pivotal" target=”_blank">Watch Now</a></p>
https://content.pivotal.io/cloud-native/feb-7-how-to-ensure-the-performance-of-your-cloud-native-apps-webinar
494140443Fri, 18 Jan 2019 16:47:43 -0500Amy WelchEvolving to Cloud-Native - Nate Schutta 2/2
SpringOne Tour Toronto 2018 by Pivotal
Evolving to Cloud-Native by Nate Schutta
2/2 https://content.pivotal.io/cloud-native/evolving-to-cloud-native-nate-schutta-2-2-2
486197813Sat, 15 Dec 2018 11:28:15 -0500Evolving to Cloud-Native - Nate Schutta 1/2
SpringOne Tour Toronto 2018 by Pivotal
Evolving to Cloud-Native by Nate Schutta
1/2 https://content.pivotal.io/cloud-native/evolving-to-cloud-native-nate-schutta-1-2
486197816Sat, 15 Dec 2018 11:26:07 -0500A Planet-Scale Database for Low Latency Transactional Apps by Yugabyte
Cloud-Native Data Day by Pivotal
A Planet-Scale Database for Low Latency Transactional Apps by Yugabyte https://content.pivotal.io/cloud-native/a-planet-scale-database-for-low-latency-transactional-apps-by-yugabyte
485213852Fri, 07 Dec 2018 21:02:00 -0500Orchestrating stateful applications with PKS and Portworx
Cloud-Native Data Day by Pivotal
Orchestrating stateful applications with PKS and Portworx https://content.pivotal.io/cloud-native/orchestrating-stateful-applications-with-pks-and-portworx
485213855Fri, 07 Dec 2018 21:00:31 -0500High performance Spark distribution on PKS by SnappyData
Cloud-Native Data Day by Pivotal
High performance Spark distribution on PKS by SnappyData https://content.pivotal.io/cloud-native/high-performance-spark-distribution-on-pks-by-snappydata
485213858Fri, 07 Dec 2018 20:58:31 -0500PostgreSQL-as-a-Service with Crunchy PostgreSQL for PKS
Cloud-Native Data Day by Pivotal
PostgreSQL-as-a-Service with Crunchy PostgreSQL for PKS by Crunchy https://content.pivotal.io/cloud-native/postgresql-as-a-service-with-crunchy-postgresql-for-pks
485213861Fri, 07 Dec 2018 20:57:25 -0500