Microservices are a hot topic in IT circles these days. The idea of a modular approach to system building – where you have numerous, smaller software services that talk to each other instead of monolithic components – has many benefits ...
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.
Agile is expanding within the enterprise. Agile adoption is growing within organizations, both more broadly and deeply, according to the 12th annual State of Agile report from CollabNet VersionOne. A higher percentage of respondents this year report that "all or almost all" of their teams are agile, and that agile principles and practices are being adopted at higher levels in the organization ...
For the past 13 years, the Ponemon Institute has examined the cost associated with data breaches of less than 100,000 records, finding that the costs have steadily risen over the course of the study. The average cost of a data breach was $3.86 million in the 2018 study, compared to $3.50 million in 2014 – representing nearly 10 percent net increase over the past 5 years of the study ...
Hidden costs in data breaches – such as lost business, negative impact on reputation and employee time spent on recovery – are difficult and expensive to manage, according to the 2018 Cost of a Data Breach Study, sponsored by IBM Security and conducted by Ponemon Institute. The study found that the average cost of a data breach globally is $3.86 million ...
The previous chapter in this WhiteHat Security series discussed dependencies as the second step of the Twelve-Factor App. This next chapter examines the security component of step three of the Twelve-Factor methodology — storing configurations within the environment.
Results from new Forrester Consulting research reveal the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile experts from their less advanced peers ...
Even organizations that understand the importance of cybersecurity in theory often stumble when it comes to marrying security initiatives with their development and operations processes. Most businesses agree that everyone should be responsible for security, but this principle is not being upheld on a day-to-day basis in many organizations. That’s bad news for everyone. Here are some best practices for implementing SecOps ...
While the technologies, processes, and cultural shifts of DevOps have improved the ability of software teams to deliver reliable work rapidly and effectively, security has not been a focal point in the transformation of cloud IT infrastructure. SecOps is a methodology that seeks to address this by operationalizing and hardening security throughout the software lifecycle ...
Organizations are shifting away from traditional, monolithic architectures, with three-quarters of survey respondents delivering at least some of their applications and more than one-third delivering most of their applications as microservices, according to the State of DevOps Observability Report from Scalyr ...
What top considerations must companies make to ensure – or at least help improve – Agile at scale? The following are key techniques and practices to help accelerate Agile delivery rollouts and scale Agile and DevOps in the Enterprise ...