Subscription – IT Innovation & Management

newsletter subscription


  1. Great article. Would love to see the PEs updated after today. Why do you believe we haven’t seen more M&A activity with cash hoards of both buyers and sellers given depressed valuations? For the acquirer it solves for new tech, users, rev growth, and perhaps most valuable of all – plug and play tech talent with the option to cut dead weight)? Furthermore, many would be bringing a sizable chunk of cash and minimal debt to balance sheet.

  2. After reading this, we have a better understanding of which approach is right for our company. In the world of cloud computing, there are two major camps: cloud-native and cloud-agnostic. Both approaches have their advantages and disadvantages. Thanks!

  3. Thank you for this comprehensive article!

    The new deployment pipeline reference architecture and reference implementations provide an architecture and implementations for deploying applications and infrastructures into AWS. The architecture document and diagram describes the mandatory and optional components of the architecture, and the implementations provide reference implementations for each type of pipeline.


  4. Cheers! I’m so thankful I stumbled across this blog – it’s been a real eye opener and provided me with a lot of new knowledge.

    In this digital transformation, one of the most important aspects was to chose an architecture that would be open and flexible, allowing for the construction of solutions using the best cloud-native products and services available. Additionally, the architecture should be able to meet the needs of secure integration between products and tools, as well as the simplification of data, analytics, and ML workloads. Finally, the solution is unified by using the same codebase to manage the ingestion and processing of both workloads.


  5. This post has really opened my eyes to a fresh way of looking into the topic. Thank you for taking the time to create this content and share your understanding. It is really appreciated!
    This article is part three of a series that addresses disaster recovery (DR) strategies with the help of AWS-managed services. It introduces a DR strategy that utilizes managed services through a backup and restores strategy with multiple regions. The multi-site active/passive approach is best suited for customers who have business-critical workloads with high availability requirements. The article covers the components of an application that processes payment transactions, as well as how managed services behave in a multi-site environment. This active/passive approach covers building a DR solution using a mix of native and non-native cross-region replication methods. Using managed services, this strategy becomes simpler through automation of service updates, deployment using Infrastructure as Code (IaaC), and general management of the two environments.

  6. It’s been a pleasure to read. Thanks for taking the time to share your expertise! This is an incredibly useful blog post.
    The development of incident handling procedures and effective incident response planning is vital to any good security program, especially as cloud services become more prevalent. This article explains the differences between cloud incident response and traditional incident response and outlines some of the benefits and challenges of employing cloud incident response, as well as providing a framework for implementing best practices for cloud incident response. These best practices include enabling cloud-wide logging where possible, utilising identity and access management and role-based access controls, having incident response team members attend CSP training, and collaborating with cloud engineering and DevOps teams.

  7. This is a first-class post!
    The article discusses “Architecture Erosion” and “Technical Debt” with the Armchair Architects, Uli Homann, and Eric Charran. Architecture erosion occurs when architectural principles that were originally put in place are no longer in sync with changes in requirements, infrastructure, or customer habits. Technical debt occurs when tactical decisions are made fast and cheaply, not necessarily the “right way”. Three levels of erosion are identified: large technology disruptions, slow erosion, and living architecture. Technical and business disruptions can lead to architecture erosion. Business models take longer to change than the technical model, so it is important to have a research organization or read trade articles and stay informed. To prevent architecture erosion, it is important to pay attention and be rigorous through architectural reviews, calibration sessions, meeting with engineering counterparts, and correlating back to the business architecture.

  8. had me thinking this ! This Got Me Thinking.
    Sequoia China has raised $725m for a new fund, HongShan, which will focus on high-growth companies in China. The fund will be led by Neil Shen, founder of Sequoia China, and seeks to capitalise on the country’s booming technology industry.
    Struggling to manage debt? provides personalized assistance to help you regain financial stability.

  9. Great insights on the ethics and governance of AI and data, and how they’re interconnected. Important points raised on the need for organisations to focus on their internal data governance controls to ensure compliance with regulatory requirements across different jurisdictions. Valuable read!
    founder of balance thy life

  10. Amazing post! I’m so glad to have come across this site and read this post. It’s been a real aid to me and I’m sure it will be for lots of others, too. Thanks for putting in the effort.
    The US National Security Council will soon roll out new labeling requirements for Internet of Things (IoT) devices. The White House’s National Institute of Standards and Technology (NIST) has released minimum security requirements for IoT devices, including a requirement for “asset identification” to distinguish IoT devices by certified digital identity. NIST also recommends that devices be configurable and able to restore to a default secure setting by an authorized individual. The US IoT labeling scheme is expected to be rolled out in the coming months, although details of the new program are still unclear. Other countries, including Singapore, have initiated IoT labeling programs, with varying degrees of tiers of grading. To secure the IoT, labeling schemes should also accommodate IoT diversity, adapt to a constantly moving target, and consider the complex supply chain of manufacturers, developers, and vendors that contribute to IoT insecurity. Labels may help consumers make informed decisions about IoT purchases and incentivize good security practices for IoT manufacturers and vendors.

  11. Great article! It provides a clear and organized overview of the key requirements for ISO 27001 certification. The explanations and practical tips are very helpful for organizations at different stages of their certification journey.