 Quality Control in Digital Transformation: Strategies for Ensuring a Positive Outcome Jun 7th 2023, 01:27, by Anusha K What Is Digital Transformation? Digital transformation is a process that prioritizes a customer-centric and technology-focused approach to all aspects of a business. It leverages advanced technologies such as AI, automation, and cloud computing to optimize data usage, improve decision-making, and enhance customer experiences. This process not only transforms customer expectations but also generates new business opportunities. While many organizations initiate digital transformation to address a specific market challenge, it is not a one-time solution. Instead, it is a continuous adaptation to a dynamic environment that aims to establish a technical and operational foundation for a flexible response to changing customer needs, market conditions, and global events. |  How to Implement Istio in Multicloud and Multicluster Jun 6th 2023, 21:06, by Ravi Verma Today every application has microservices architecture where individual services are spread across public clouds and multiple Kubernetes clusters. Since all the communication of messages among services happens over the internet, it is very important to ensure the security of your data. You don't want any malicious guy to read and record the data-in-transit (known as packet sniffing), or intervene in between the communication as someone you trust (IP spoofing), or perform a DoS attack such as bandwidth flooding or connection flooding, etc. The idea is security should always be developed in a layered approach to build defense in depth. When software engineers are developing containerized applications they need to think about security at Code, Container, Cluster, and Cloud levels (read 4 C's of container security). |  Why I Prefer Trunk-Based Development Jun 6th 2023, 20:49, by Trisha Gee These days, distributed version control systems like Git have "won the war" of version control. One of the arguments I used to hear when DVCSs were gaining traction was around how easy it is to branch and merge with a VCS like Git. However, I'm a big fan of Trunk-Based Development (TBD), and I want to tell you why. With trunk-based development, all developers work on a single branch (e.g., 'main'). You might have read or heard Martin Fowler or Dave Farley talking about it. It was when I was working with Dave (around about the time that Git was rapidly becoming the "go-to" version control system) that I really saw the benefits of trunk-based development for the team, particularly in an environment that was pioneering continuous delivery (Dave was writing the book with Jez Humble while I worked with him). |  Introduction to Domain-Driven Design Jun 6th 2023, 20:35, by Aditya Bhuyan Domain-driven design (DDD) is an approach to software development that focuses on understanding the domain of the problem being solved, and using that understanding to guide the design of the software. This approach is particularly well-suited to microservices architectures, where services are designed to be small, autonomous, and focused on a specific business capability. In this article, we will explore how domain-driven design can be used to design microservices, and why this approach is beneficial for building complex software systems. |  Idempotent Liquibase Changesets Jun 6th 2023, 20:16, by Horatiu Dan Abstract "Idempotence is the property of certain operations in mathematics and computer science whereby they can be applied multiple times without changing the result beyond the initial application" [Resource 3]. The purpose of this article is to outline a few ways of creating idempotent changes when the database modifications are managed with Liquibase. Throughout the lifetime of a software product that has such tier, various database modifications are being applied as it evolves. The more robust the modifications are, the more maintainable the solution is. In order to accomplish such a way of working, it is usually a good practice to design the executed changesets to have zero side effects, that is, to be able to be run as many times as needed with the same end result. |  Adding Mermaid Diagrams to Markdown Documents Jun 6th 2023, 17:44, by Peter Verhas Mermaid is a trendy diagramming tool. A year ago, it was integrated into the Markdown rendering of GitHub. It is also integrated into several editors (see "Include diagrams in your Markdown files with Mermaid" for more information). What can you do, however, if you use a different editor? What if you want to use your Markdown document in an environment that does not integrate Mermaid yet? What can you do if the diagram is not Mermaid but PlantUML, Graphviz, or any other diagramming tool? |  Understanding Data Compaction in 3 Minutes Jun 6th 2023, 15:39, by Frank Z What is compaction in the database? Think of your disks as a warehouse: The compaction mechanism is like a team of storekeepers (with genius organizing skills like Marie Kondo) who help put away the incoming data. In particular, the data (which is the inflowing cargo in this metaphor) comes in on a "conveyor belt," which does not allow cutting in line. This is how the LSM-Tree (Log Structured-Merge Tree) works: In data storage, data is written into MemTables in an append-only manner, and then the MemTables are flushed to disks to form files. (These files go by different names in different databases. In my community, we call them Rowsets). Just like putting small boxes of cargo into a large container, compaction means merging multiple small rowset files into a big one, but it does much more than that. As I said, the compaction mechanism is an organizing magician: | |
Comments
Post a Comment