Embracing DevOps at enterprise scale requires a seismic shift in the way an organization plans, builds, tests, releases, and manages applications. Here are four ways to ensure your enterprise DevOps transformation is a success ...
Please observe the following editorial guidelines when submitting blogs to DEVOPSdigest:
DEVOPSdigest recommends that you send an abstract or outline of your potential blog submission to Pete Goldin, Editor and Publisher of DEVOPSdigest, before you start writing the blog, to ensure it is something we would publish.
The following guidelines apply to non-vendors — such as analysts, consultants, integrators and users — who would like to post a blog on DEVOPSdigest. Non-vendor blogs are posted in the BIZDEVOPS Blog.
Blogs from DEVOPSdigest sponsors are also posted in the Vendor Forum, but sponsors gain certain benefits when blogging. If you work for or represent a sponsor of DEVOPSdigest, click here for the Sponsor Blog Guidelines.
If you are a PR or Communications Manager or Agency, click here for some tips on how to interact with DEVOPSdigest.
If you are submitting a quote for a DEVOPSdigest list, such as our annual DevOps Predictions list, click here for guidelines on APMdigest.
All blogs submitted to DEVOPSdigest must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not pitch DEVOPSdigest to re-post your blog.
Standard word count for a blog is 500-1000 words. This is not a strict rule. Word counts can be longer if the topic warrants more content. If your blog is longer than 1000 words, however, you may want to consider breaking it into multiple parts. Editorial decisions relating to word count are made on a case-by-case basis.
DEVOPSdigest does not follow an editorial calendar, and usually does not assign a deadline. We post content as we receive it.
DEVOPSdigest posts 1-3 items of primary content — blog or feature — per week. Consequently, there is often a queue of content waiting to be posted.
DEVOPSdigest content is featured in APMdigest e-mails, which go out twice per month, and the current mailing includes content posted since the last mailing.
DEVOPSdigest accepts blogs on topics relating to DevOps including:
■ Development Processes
■ Development Technology
■ Development Automation
■ Agile Development
■ Continuous Development
■ API (Application Program Interface)
■ Development Monitoring and Analytics
■ Application Performance and Quality Testing
If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.
Blogs should be objective, vendor-neutral, thought leadership pieces. Topics should be general industry interest to educate and enlighten our readers. Please do not promote your company, products, partners or any vendor — or criticize the competition — in the blog copy or in related graphics submitted with the blog.
Author and Company Profile
If this is your first blog for DEVOPSdigest, send a one paragraph bio of the author and one paragraph profile of the company, along with the blog.
On The BIZDEVOPS Blog, non-vendor bloggers are welcome to include links at the end of the blog to link to their home page, or other relevant information such as research or events.
Do not place any hyperlinks in the body copy of the blog linking to your company's web pages or any other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making.
All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Related links included with the blog are also subject to DEVOPSdigest approval.
If you contribute to DEVOPSdigest, you are free to re-post your own blog on your own website, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site.
However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.
Are applications teams prepared to manage the chaos arising from an ever-growing landscape of heterogeneous deployment types? A recent survey of application and operations professionals sought to better understand how the industry is shifting and what the future of DevOps might look like. Here is what the survey uncovered ...
More than half of organizations have a dedicated DevOps team to help them better implement agile strategies, accelerate release cycles and ensure continuous development. However, databases have a habit of holding DevOps back ...
Test Environment Management can save organizations close to $10,000 for each release, yet only four percent of large enterprises have fully integrated TEM processes into organizational DNA, according to the 2018 Test Environment Management Survey released by EMA and Plutora ...
How do you integrate tools to enable shift-left performance? The following tools will simplify maintenance, can be managed in a centralized way, and provide an easy-to-use UI to comprehend results ...
Focusing at the API layer of an application can help enable a scalable testing practice that can be efficiently executed as part of an accelerated delivery process, and is a practice that can be adopted and enabled at the earliest possible stages of development — truly shifting left functional testing. But what about performance testing? How do we enable the shift left of nonfunctional testing? Here, we explore what this means and how to enable it in your organization ...
As businesses look to capitalize on the benefits offered by the cloud, we've seen the rise of the DevOps practice which, in common with the cloud, offers businesses the advantages of greater agility, speed, quality and efficiency. However, achieving this agility requires end-to-end visibility based on continuous monitoring of the developed applications as part of the software development life cycle ...
Imagine that you are tasked with architecting a mission-critical cloud application. Or migrating an on-premise app to the cloud. You may ask yourself, "how do the cloud savvy companies like Airbnb, Adobe, SalesForce, etc. build and manage their modern applications?" ...