3 Things You Should Be Doing in Cloud Native in 2021

Share on facebook
Share on twitter
Share on linkedin
As we wrap up the first quarter of 2021, we wanted to talk about things we should be doing as part of a cloud native strategy for the remaining 3/4 of the year. Moving from traditional monolithic. architectures to a modern microservices approach has many benefits, but still has the greater majority of us baffled in terms of tapping into its full potential.
1. Anticipating the Next Big Hill in CI/CD

The first cloud native strategy has to do with anticipating and preparing for the next CI/CD challenge. Many traditional CI/CD solutions or approaches were developed with traditional or legacy application architectures in mind, and many of those approaches may be well suited for a monolithic application deployment, but may not be well suited for Kubernetes or Cloud Native environments. What hills are approaching in cloud native CI/CD, and how can we be prepared?

2. Application Policy Management

Cloud native strategy number two focuses on building a trusted and secure process. From development to deployment, we need to ensure that all mandates and policies are followed and that no steps in the process introduce new vulnerabilities, and just as importantly, that no steps are skipped. This is particularly true in highly regulated industries such as banking, but with all of the data everyone is storing these days, penalties for a breach, loss in revenue/customer confidence, etc, this really just as important for everyone building and deploying software. What strategies are there for tackling this challenge?

3. Reducing the Human Element (again)

The final cloud native strategy brings us back to the days before any of us were saying “DevOps.” If we go all the way back to the beginning of CI and build automation, eliminating the human error aspect was arguably the biggest win. Speed was an added bonus, and speed really just helped to shift the bottleneck a little more to the right. In cloud native, we are seeing history repeat itself with a lot of manual effort going into Kubernetes deployments. Teams are approaching Kubernetes deployments with Helm, YAML, scripting, etc which all take a high level of manual effort to maintain. What should we be doing to reduce the risk of a manual approach, and how do we ultimately get to a trusted and repeatable process where the promises of speed in Kubernetes are realized?

cgilcher

cgilcher

Leave a Reply

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

About Dr.-Ing Christian Gilcher

With a strong background both in Business Engineering and Technology, i combine both conceptual and practical skills that are essential for designing modern AI-native business software. Main experiences include “Global Head of IT Business Management” at Dresdner Kleinwort Investment Bank and Commerzbank as well as building AI-centric Digital products with German “Mittelstand” clients with DDG AG. I always strive to combine clean architectures as well as effective functionality.

Recent Posts

Predictive Analytics World 2020

Join our Community now

This centros Community License v1.0 (“this Agreement”) sets forth the terms and conditions on which centros GmbH (“the Licensor”) makes available this software (“the Software”).

 

BY INSTALLING, DOWNLOADING, ACCESSING, USING OR DISTRIBUTING THE SOFTWARE YOU INDICATE YOUR ACCEPTANCE TO, AND ARE ENTERING INTO A CONTRACT WITH, THE LICENSOR ON THE TERMS SET OUT IN THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, YOU MUST NOT USE THE SOFTWARE. IF YOU ARE RECEIVING THE SOFTWARE ON BEHALF OF A LEGAL ENTITY, YOU REPRESENT AND WARRANT THAT YOU HAVE THE ACTUAL AUTHORITY TO AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT ON BEHALF OF SUCH ENTITY.

 

“Licensee” means you, an individual, or the entity on whose behalf you are receiving the Software.

 

Permission is hereby granted, free of charge, to the Licensee obtaining a copy of this Software and associated documentation files, to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject in each case to the following conditions:

 

 

Condition 1: If the Licensee distributes the Software or any derivative works of the Software, the Licensee must attach this Agreement.

 

Condition 2: Without limiting other conditions in this Agreement, the grant of rights under this Agreement does not include the right to provide a Commercial Managed Service Offering of the centros Framework.

 

A “Managed Service Offering” is a service intended for or directed towards commercial advantage or monetary compensation for the provider of the service enabling third parties (other than the provider’s employees or Contractors) to consume any services that are in direct competition with any commercial cloud-based services that are offered to the market by the Licensor.

 

If the Licensee is in breach of the Conditions, this Agreement, including the rights granted under it, will automatically terminate with immediate effect.

 

SUBJECT AS SET OUT BELOW, THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

 

NOTHING IN THIS AGREEMENT EXCLUDES OR RESTRICTS A PARTY’S LIABILITY FOR (A) DEATH OR PERSONAL INJURY CAUSED BY THAT PARTY’S NEGLIGENCE, (B) FRAUD, OR (C) ANY OTHER LIABILITY TO THE EXTENT THAT IT CANNOT BE LAWFULLY EXCLUDED OR RESTRICTED.