DEV Community: Dmytro Golodiuk

Introduction to Mechanical Keyboards

Dmytro Golodiuk — Tue, 13 Aug 2024 20:35:01 +0000

I recently added a new mechanical keyboard to my collection, and it just arrived (it’s on the poster to this blog post). This one isn’t meant to replace my main keyboard at home — it’s more of an option for working in the office. I might do a full review of this keyboard later on, but that’s not what I’m here to talk about today. Instead, I want to take a moment to introduce you to the world of mechanical keyboards and share why they’ve become one of my favorite hobbies.

If you’ve never used a mechanical keyboard before, this post might just inspire you to give one a try. After all, who knows? You might end up enjoying them as much as I do.

As someone who spends a lot of time in front of a computer, you know how important it is to have the right tools. Whether you’re coding, writing documentation, or just getting through a long day of emails, the keyboard you use plays a huge role in your daily experience. For a lot of people, keyboards are an afterthought — just a basic input device that came with the computer. But for those of us who have discovered the world of mechanical keyboards, it’s a bit more than that. It’s become a bit of a passion.

What Exactly Is a Mechanical Keyboard?

At a basic level, a mechanical keyboard is different from the usual cheap keyboards because it uses individual mechanical switches under each key instead of a single sheet of rubber membranes. That might sound a bit technical, but the difference is pretty straightforward: each key on a mechanical keyboard has its own mechanism that makes it work. This gives each key a more distinct feel and sound when you press it.

There are different types of switches used in mechanical keyboards. Some are smooth and quiet (called linear switches), some give you a little bump to let you know the key has been activated (tactile switches), and others add an audible click along with that bump (clicky switches). Each type of switch offers a different typing experience, and part of the fun is figuring out which one feels best for you.

Why Do Mechanical Keyboards Cost More?

If you’ve looked into mechanical keyboards before, you might have noticed that they’re generally more expensive than the average keyboard. There are a few reasons for this:

Build Quality: Mechanical keyboards are built to last. The switches themselves are designed to handle millions of keypresses, far outlasting those cheap rubber dome keyboards.
Materials: Higher-end materials are used, from the keycaps to the frame. This makes the keyboard feel more solid and durable.
Customization: There’s also a lot more room for customization with mechanical keyboards, from choosing the type of switch to selecting custom keycaps.

It’s not just about paying more for the sake of it. The higher price often reflects the better build quality and the specific features that make a mechanical keyboard more enjoyable to use day in and day out.

Mechanical Keyboards vs. Gaming Keyboards

Mechanical keyboards often get lumped together with gaming keyboards, and while there’s definitely some overlap, they’re not the same thing.

Gaming Keyboards: These are often designed with extra features that gamers might want, like RGB lighting, macro keys, and sometimes even built-in screens or extra ports. They tend to prioritize quick response times and flashy looks, which are great if you’re into gaming but might be overkill for everyday work.
Mechanical Keyboards: While many gaming keyboards use mechanical switches, mechanical keyboards themselves aren’t just for gamers. They’re more about the typing experience — how it feels to press each key and the overall build quality. If you’re spending hours typing, a mechanical keyboard is worth considering, even if you’re not a gamer.

The Rabbit Hole of Custom Mechanical Keyboards

Once you start getting into mechanical keyboards, you might find yourself drawn into the world of custom keyboards. This is where things get really interesting (and maybe a bit obsessive).

With custom keyboards, you can choose everything: the case, the type of switches, the keycaps, and even the layout. It’s kind of like building your own PC but on a smaller scale. For example, if you prefer a more compact keyboard, you can build one with a 60% layout, which drops the number pad and function keys, making it smaller and easier to transport. Or if you need something specific for your workflow, you can add extra keys or create custom key bindings.

It’s not just about the technical side, either. Custom keycaps come in all sorts of designs and materials, so you can make your keyboard look as unique as you want. Some people even get into custom painting or engraving their keyboards.

Why Should You Care?

So, why bother with all of this? If you spend most of your day typing, a mechanical keyboard can make that experience more enjoyable. It’s not just about having a fancier tool; it’s about finding something that feels good to use, day after day. Whether it’s the satisfying click of a switch, the feel of a solid metal case, or the look of custom keycaps, there’s something about a well-made mechanical keyboard that just makes typing more satisfying.

And who knows? Maybe, like me, you’ll find yourself getting deeper into the hobby, experimenting with different switches, layouts, and designs. Or maybe you’ll just find one keyboard that you love and stick with it. Either way, it’s worth exploring if you haven’t already.

Conclusion

In the end, it’s not about selling you on mechanical keyboards — it’s about sharing something that has made a difference in my daily routine a long time ago, and something I think could do the same for you.

Thank you!

Introducing My New Project - EU GovTech Knowledge Base

Dmytro Golodiuk — Fri, 19 Jul 2024 19:42:57 +0000

Today, I am thrilled to announce the launch of my latest project, the GovTech Knowledge Base , a structured resource dedicated to GovTech within the European Union 🇪🇺. This initiative is born out of my year’s worth of immersion and hands-on experience in the public sector, a new and enriching journey for myself who had previous background primarily rooted in IT solutions for private business.

The Journey So Far

One year ago, I transitioned from developing IT solutions for private businesses and product companies, where I served as a Solution, Cloud, and Enterprise Architect, to working on a software projects within the public sector. This new role introduced me to complex business domains such as finance, banking, and the EU regulations. The shift required a significant investment of time and effort to understand the EU’s structure, procedures, directives, and regulations.

The Challenges

Despite the abundance of information available, especially in the highly regulated public sector, I encountered two primary challenges:

Information Filtering and Organization: The need to sift through vast amounts of data and transform it into a structured, well-organized knowledge base.
Beyond Bookmarks: The desire for a dynamic database where I could define necessary entities, establish relationships between them, and implement a robust search index — essentially, my own tailored large language model (LLM).

The Solution: Notion

Given my experience of using Notion to structure my notes and manage information, it was a natural choice for this project. Notion’s flexibility and powerful features make it an ideal platform for creating a comprehensive and user-friendly knowledge base.

The GovTech Knowledge Base

I am excited to make the GovTech Knowledge Base publicly available, even though it remains a work in progress. This resource is designed for anyone interested in GovTech, IT development within the public sector, and understanding how the EU implements its IT projects.

What You’ll Find

The knowledge base is focused on several key aspects of the European Union’s activities:

Technology Regulations: Detailed information on the regulations governing technology use within the EU.
IT Strategy: Insights into the EU’s IT strategies, including goals, plans, and implementation roadmaps.
Programmes and Projects: Comprehensive coverage of ongoing IT programmes and projects within the EU.
EU Organizational Structure: An overview of the EU’s organizational framework and how it influences IT initiatives.
EU Digital Services: Information on the various digital services provided by the EU.
Adopted Technologies: A look at the technologies being used and adopted, from developers to developers.

Access the Knowledge Base

The GovTech Knowledge Base is available through the following link: GovTech Knowledge Base. I hope you find it a valuable resource as you navigate the complex and fascinating world of GovTech and IT in the public sector.

I look forward to your feedback and hope this knowledge base becomes an indispensable tool for professionals and enthusiasts alike, providing clarity and insight into the EU’s approach to technology and digital transformation.

Thank you!

Jack of All Trades, Master of None: When Solution Architects Lose Their Way

Dmytro Golodiuk — Wed, 10 Jul 2024 16:06:48 +0000

☝️ The role of an IT Architect is often misunderstood and sometimes misrepresented. While some may believe that being a “jack of all trades” is beneficial, it can lead to becoming a “master of none.”

This blog post aims to clarify the real responsibilities of an IT Architect and provide recommendations for those aspiring to excel in this field or for those who may have lost their way.

The Real Role of an IT Architect

At its core, the role of an IT Architect – whether a Solution Architect, Enterprise Architect, or Security Architect – is to solve business problems through technology. This involves planning and designing the technological architecture, which includes the components, their combinations, interconnections, and integrations. An IT Architect is not about selling themselves or their theoretical knowledge; they are about selling practical solutions to business problems.

Signs of a Struggling IT Architect

Here are some negative indicators that an IT Architect may be off track, along with their positive counterparts:

1. Endless Meetings with No Results

👎 Destructive Indicator : Numerous large meetings that result in stagnation or further complications.

👍 Constructive Indicator : Well-planned, concise, and effective meetings that generate solutions rather than additional problems.

2. Overemphasis on Theoretical Knowledge

👎 Destructive Indicator : Architects boasting about their theoretical knowledge and using buzzwords without practical application.

👌 Constructive Indicator : Architects focused on team collaboration and practical solutions, understanding that there is rarely a single “correct” answer in IT architecture.

3. Selling Buzzwords Over Solutions

👎 Destructive Indicator : Using flashy buzzwords to sell abstract solutions to both real and imaginary problems.

🤙 Constructive Indicator : Implementing decision-making methods in practice, recognizing that technology alone doesn’t solve problems. The correct approach involves People –> Process –> and Products (technologies) in that order.

Common Pitfalls

Many IT Architects can fall into the trap of drifting too far from their core responsibilities. It’s essential to maintain a focus on IT architecture rather than straying into roles that are better suited for other professions. Here are some common mistakes:

1. Focusing on Self-Promotion Over Problem-Solving

Mistake : Prioritizing personal branding and self-promotion.

Recommendation : Shift focus to solving business problems with well-planned technological solutions.

2. Taking on Non-Architectural Roles

Mistake : Attempting to take on responsibilities of marketers or sales representatives, such as brand management or direct selling.

Recommendation : Stay within the realm of IT architecture, focusing on designing and implementing technology solutions. Leave marketing to marketers and sales to sales professionals.

3. Misaligned Problem-Solving Process

Mistake : A disorganized approach to problem-solving.

Recommendation : Organize the problem-solving process in a structured and proactive way, using methods like the 5 Whys or the ODSC (Objective, Data, Solution, Check) framework.

Conclusion: Be a Master Problem Solver

To be a successful IT Architect, one must master the art of problem-solving. This means moving beyond theoretical knowledge and marketing gimmicks to focus on practical, effective solutions that address real business needs. An IT Architect should strive to be a master in their field, not just a jack of all trades. By doing so, they will not only become more valuable to their organization and partners but also avoid the pitfall of having to sell themselves rather than their solutions.

In the words of Henry Ford, “Most people spend more time and energy going around problems than in trying to solve them.” As an IT Architect, your goal should be to spend your energy solving problems, not just talking about them. So, be diligent, stay focused, and always prioritize the business needs above all else.

For those looking to refine their skills or get back on track, remember: an effective IT Architect doesn’t just understand technology – they understand how to leverage it to solve real business problems.

Bonus: Self-Assessment

I wanted to share a helpful framework that categorizes the maturity of problem-solving processes based on their structure and proactivity. Understanding this framework can help you identify where your current processes stand and how you can improve them.

Where's your problem-solving process?

Stay sharp and stay dedicated to mastering your craft.

Thank you!

The Nine Pillars to Architectural Excellence

Dmytro Golodiuk — Sat, 25 Nov 2023 20:33:58 +0000

Becoming a better Solution Architect involves a mix of technical expertise, soft skills, and continuous improvement. In this blog article, I’ll examine nine things and practices that can help you excel in the Solution Architect role.

This blog post is the second in the series “Mastering the Craft: A Deep Dive into Common Pitfalls for Architects.” The first post was Architectural Red Flags: 10 Mistakes Undermining Solution Architects.

Preface

As a Solution Architect, your role is the bridge between creativity and practicality, transforming complex challenges into intelligent solutions. Embracing continuous improvement isn’t just a choice; it’s the foundation that strengthens your ability to innovate, adapt, and lead in a constantly changing tech world. By aiming for improvement, you’re polishing your skills and nurturing a mindset that thrives on fresh ideas and resilience. Every effort you put into your growth expands the range of possibilities, ensuring your solutions remain cutting-edge, adaptable, and vital to the success of the projects you handle. Remember, in this dynamic field, your dedication to continuous improvement isn’t just a journey; it’s the driving force that pushes you toward being a trailblazer in innovation and excellence in solution architecture.

Let’s use the 3 Horizons model to structure the steps to the Solution Architects’ growth goals. What are the 3 Horizons?

The 3 Horizons represent:

current opportunities,

future opportunities that require more investment (time, effort, experience),

and ideas for future opportunities that can be used as experiments, pilots, or minority stakes in new projects or businesses.

The Nine Pillars to Architectural Excellence

The x-axis represents the focus area (technical expertise and soft skills), but remember that it does not indicate what you should think about now vs. later. You should be thinking about all three horizons at the same time. You will always want to cycle between where you are strong now, which opportunities you believe will be successful in the future, and which opportunities you’d like to explore further.

1. Learn from your mistakes and failures

You need to be able to analyze what went wrong, identify the root causes, and implement corrective actions to prevent or mitigate similar issues in the future.

As Solution Architects, our journey toward excellence isn’t just about the successes we achieve and the valuable lessons we gather from our failures. Mistakes are not roadblocks; they are signposts guiding us toward improvement and innovation. Embracing our failures allows us to dissect and understand what went wrong, enabling us to refine our approaches and solutions. These experiences give us deeper insights, learn what doesn’t work, and discover new paths toward success. By acknowledging and learning from our mistakes, we become better problem solvers and fortify our ability to design more robust and efficient solutions in the future. Every setback is an opportunity for growth , and leveraging these lessons will undoubtedly pave the way for us to excel as Solution Architects.

Ignoring the recommendation to learn from mistakes and failures can have several negative consequences for IT Solution Architects:

Repetition of Errors: Without acknowledging and learning from mistakes, there’s a high likelihood of repeating them. This can lead to a cycle of inefficiency, wasted time, and resources as similar issues resurface in different projects.
Stagnation and Lack of Innovation: Failure to learn from mistakes can result in a stagnant approach to problem-solving. It hampers the ability to innovate and devise novel solutions, hindering professional growth and advancement.
Diminished Trust and Credibility: Continually making the same mistakes can erode trust among team members and stakeholders. It can damage the architect’s credibility, potentially impacting their reputation and opportunities for leadership roles or crucial project responsibilities.

💡 If you haven’t read the first article of this series, “Mastering the Craft: A Deep Dive into Common Pitfalls for Architects,” I welcome you to do it. In the article Architectural Red Flags: 10 Mistakes Undermining Solution Architects. I examined prevalent mistakes made by Solution Architects and offered detailed insights, strategies, and examples to navigate these challenges effectively.

2. Be a perfectionist, paranoid, and have an appreciation for aesthetics

Characteristics like being a perfectionist, paranoid (in a vigilant, cautious sense), and having an appreciation for aesthetics (esthete) have remarkably positive implication for an IT Solution Architect role.

Perfectionist Traits. Being detail-oriented and striving for excellence can result in meticulously designed solutions. It can ensure that the architecture is robust, efficient, and meets high-quality standards.

Paranoia (Vigilance and Caution). A cautious mindset can be beneficial in foreseeing and mitigating potential risks or security threats in the architecture. It could lead to a more resilient system design with built-in contingencies.

Esthete (Appreciation for Aesthetics). Having an eye for aesthetics can result in architecturally pleasing and user-friendly designs. It can contribute to better user adoption and satisfaction with the solutions.

While these characteristics can bring certain advantages, it’s crucial to strike a balance. Utilizing these traits effectively can result in well-crafted, secure, and user-friendly solutions. However, excessive focus on perfection, caution, or aesthetics without considering practicality, innovation, and broader project goals could potentially limit the effectiveness of the architect’s contributions. Therefore, a balanced approach that harnesses the positive aspects of these traits while mitigating their potential downsides is essential in the role of an IT Solution Architect.

🤔 Now, please take a look at these architectural solutions. What do you think? I reckon, it’s evident that traits like perfectionism, paranoia, and an appreciation for aesthetics would never endorse such work.

Samples of Bad Architecture Solutions (click to 🔎)

BARRIO DE CARACAS

RAY AND MARIA STATA CENTER

BIG BALL OF MUD

3. Technical Proficiency, Continuous Learning, and Skill Development

Stay updated with the latest technologies, architectures, and tools relevant to your field. Continuous learning and hands-on experience are crucial for staying at the forefront of technology.

Invest time in continuous learning through courses, certifications, workshops, and hands-on practice.

Keep up with the latest trends and technologies in your domain. You need to know the current and emerging tools, frameworks, methodologies, and platforms to help you design and implement effective and efficient solutions.
Continuously update and refine your skills and knowledge. You need to be proactive in pursuing learning opportunities that can help you enhance your competencies and qualifications. You can also seek certification or accreditation from reputable organizations or institutions that can validate your expertise.

4. Problem-Solving Skills

Develop strong analytical and problem-solving abilities. Develop a problem-solving mindset. Solution Architects face various challenges; being adept at problem-solving and decision-making is crucial for success.

Experiment with different approaches and solutions. You must be creative and innovative in finding the best ways to solve problems and meet challenges. You can also try to apply your skills and knowledge to different domains or contexts that can broaden your perspective and experience.

Problem-solving is critical for IT Solution Architects due to several reasons:

Complexity of Projects: IT Solution Architects deal with intricate technological challenges within projects. They must analyze complex systems, understand diverse requirements, and design comprehensive solutions that address these complexities.
Meeting Business Objectives: Architects must align technological solutions with the overarching business goals. Effective problem-solving ensures that the proposed solutions resolve technical issues and contribute to achieving the business objectives efficiently.
Innovation and Adaptability: Problem-solving drives innovation in the field of technology. Architects must constantly innovate to create functional solutions and incorporate new technologies, methodologies, and best practices.
Optimization and Efficiency: Solutions must be optimized for performance, scalability, security, and cost-effectiveness. Problem-solving skills help architects find the most efficient and effective solutions that meet these criteria.
Risk Mitigation: Architects must foresee risks and issues within a system or project. Effective problem-solving helps identify, analyze, and mitigate risks before they impact the project’s success.
Client Satisfaction: The ability to solve complex problems efficiently and effectively ensures client satisfaction. Clients expect solutions that not only meet their requirements but also surpass their expectations in terms of reliability and usability.
Adapting to Change: In the ever-evolving IT landscape, problem-solving skills allow architects to adapt to new technologies, changing requirements, and unforeseen challenges during the project lifecycle.

💡 To hone your problem-solving skills for Solution Architects, I recommend the book “Technology Strategy Patterns: Architecture as Strategy”.

“Technology Strategy Patterns” is a book offering substantial guidance for IT Strategists and Architects to perform their roles effectively and efficiently. At the core of this work lies the crucial task of choice and roadmap creation. This book meticulously details patterns and their sequential application for devising strategies, specifically from a technological standpoint. It encapsulates patterns that can swiftly guide you through the path: “problem formulation -> analysis (including context) -> synthesis -> validation -> communicating recommendations (including roadmaps).” This resource serves as a comprehensive guide, offering a structured approach that facilitates the development of effective architectural solutions for success in our field.

The Book 'Technology Strategy Patterns'

5. Communication Skills

Effective communication is essential. Develop strong communication skills, both verbal and written. As a Solution Architect, you’ll often need to convey complex technical concepts to various stakeholders with different levels of technical understanding.

Communicate clearly and effectively with your team and other parties involved in the project. You need to be able to articulate your ideas, explain your decisions, solicit feedback, and resolve conflicts in a respectful and collaborative manner.
You must communicate architectural decisions and problems clearly and understandably to technical and non-technical people.

And here I must recommend the book “Illuminate: Ignite Change Through Speeches, Stories, Ceremonies, and Symbols” - one of my absolute favorites. This book is about people, relationships between people in the company, and leaders. It is about leaders who are genuine, brave, and reliable, leading others to change the company or department for the better.

💡 Please read through my overview of the book “Illuminate” by Nancy Duarte and Patt Sanches: Book summary: ‘ILLUMINATE’ by Nancy Duarte and Patt Sanches.

6. Business Acumen

Understand the business needs and objectives thoroughly. Aligning technological solutions with business goals is fundamental to the Solution Architect role. You need to align your solutions with the stakeholders’ vision, needs, expectations, industry standards, and best practices.

For Solution Architects, possessing business acumen is immensely valuable for several reasons:

Aligning Technology with Business Objectives: Solution Architects need to design systems and solutions that align with the business’s overarching goals. Understanding the business context allows architects to create solutions directly contributing to the company’s success.
Cost-Effectiveness and Resource Allocation: Architects with business acumen can make informed decisions regarding resource allocation. They understand the financial implications of different technology choices, optimizing solutions to achieve the best results within budget constraints.
Risk Management: Understanding the business landscape helps architects identify and mitigate risks effectively. They can anticipate potential challenges and align technology choices to minimize disruptions to business operations.

7. Collaboration and Teamwork

Work closely with different teams - developers, designers, managers, and clients. Collaborative skills are essential for successful project outcomes.

Collaborate with other solution architects and professionals in your field. You need to be part of a network or community that can provide support, guidance, resources, and opportunities.
You can also share your insights, experiences, and best practices with others who can benefit from them.

💡 Advice.

Share your projects on GitHub, organize an online community (on Facebook or WhatsApp, whatever), write a blog, make a podcast, etc.

Give and take, - to put it briefly.

8. Strategic Thinking

Develop a strategic mindset to anticipate future needs and design scalable and flexible solutions that can evolve as the business grows or changes.

Strategic thinking empowers IT Solution Architects to go beyond technical expertise, enabling them to envision, plan, and implement solutions that address current challenges and align with the broader organizational strategy. It helps architects be proactive, innovative, and effective in driving technological initiatives that contribute significantly to the business’s success.

9. Architecture Modeling, Diagramming and Documentation

Cultivate the habit of maintaining thorough and well-organized documentation.

Focus on creating clear and comprehensive documentation for your architectural designs. A well-documented architecture helps in understanding, implementation, and future enhancements.

Honing skills like architecture modeling, diagramming, documentation, and using documentation tools can significantly elevate the capabilities of IT Solution Architects in several ways:

Clarity in Communication: Proficiency in architecture modeling and diagramming enables architects to visually represent complex technical concepts, system structures, and relationships. This clarity aids in effective communication with both technical and non-technical stakeholders, ensuring a shared understanding of the architecture.
Improved Decision-Making: Thorough documentation allows architects to outline design decisions, rationale, and dependencies. This comprehensive documentation serves as a reference, aiding in informed decision-making during the project lifecycle.
Enhanced Collaboration: Utilizing documentation tools fosters collaboration among multidisciplinary teams. Shared documentation allows team members to collaborate efficiently, align on design strategies, and contribute to the architectural vision.
Facilitating Knowledge Transfer: Well-documented architectures serve as valuable resources for onboarding new team members. It helps in transferring knowledge about design principles, patterns, and system components, ensuring continuity in project development.
Supporting Compliance and Governance: Comprehensive documentation aids in compliance with industry standards, regulations, and best practices. It enables architects to align the architecture with governance requirements and ensures adherence to established guidelines.

Bonus

Enjoy what you do and have fun. You need to be passionate and enthusiastic about your work and find satisfaction and fulfillment in creating solutions that can positively impact the world.

Conclusion

Remember, Solution Architecture success requires combining technical expertise, soft skills, and a holistic understanding of business objectives. Continuously refining these skills and adapting to evolving technology landscapes will contribute significantly to your professional growth.

Thank you!

Architectural Red Flags: 10 Mistakes Undermining Solution Architects

Dmytro Golodiuk — Thu, 16 Nov 2023 00:00:00 +0000

In the ever-evolving realm of Information Technology, Solution Architects play a significant role in guiding projects. However, similar to any multifaceted role, there are common challenges encountered by architects and their organizations. In this blog article, I’ll examine prevalent mistakes made by Solution Architects and offer detailed insights, strategies, and examples to navigate these challenges effectively.

1. Over-specialization and Narrow Perspectives

One of the most prevalent missteps is the tendency to apply specialized knowledge in a broader context. Solution Architects, including those transitioning from roles like Database Administrator, System Analyst, or Network Engineer, may inadvertently view problems through a narrow lens. The essence of architecture lies in adopting a holistic perspective. It’s not just about programming or database administration; it’s about viewing problems from a broader angle. An architect’s essential skill lies in their ability to operate across a spectrum of technologies and tools, collaborating effectively with domain specialists.

Example:

Imagine a Solution Architect who served as a Database Administrator for several years before transitioning into the broader role of Solution Architect. Given their extensive experience in database programming and administration, these individuals tend to view all challenges primarily through the narrow scope of databases. Whether faced with data storage, retrieval, or system performance issues, their default approach is to lean heavily on database-centric solutions, often overlooking alternative approaches.

For instance, when presented with a project requiring intricate integration between multiple systems, the over-reliance on database-focused solutions might overshadow the consideration of more diverse or innovative technologies that could better suit the project’s complex needs. This rigid mindset limits their architectural vision, potentially leading to suboptimal outcomes. They may favor database-oriented solutions even when a more comprehensive, cross-functional approach involving various technologies could offer a more robust and adaptable solution.

Consequently, this over-specialization could result in missed opportunities for a more holistic architectural strategy. The architect’s inclination to apply database principles to every problem might lead to solutions lacking the flexibility, scalability, or efficiency required for specific project aspects. By fixating on database-oriented resolutions, they might neglect broader architectural considerations such as system interoperability, user experience, or overall system performance. In essence, while the architect’s background in database administration is valuable, relying solely on this expertise may limit their ability to craft diverse and innovative architectural solutions.

Advise:

Embracing a more open-minded and comprehensive approach incorporating a broader spectrum of technologies and methodologies could significantly enhance their capacity to deliver more effective and adaptable architectural strategies.

2. Ignoring Platform Potential and Limitations

Understanding the complexities and inner details of platforms is paramount. Integrating platforms such as Dynamics 365, Salesforce, OpenText, etc. requires a nuanced approach. Inexperienced architects might misuse these platforms by disregarding their intended use or, more detrimentally, devising unnecessary solutions.

Example:

An organization incorporates Microsoft Dynamics 365 into its architecture without thoroughly understanding its capabilities and limitations. This lack of awareness leads to architects breaking the platform’s inherent design, resulting in inefficiencies and potential project setbacks. Let’s look at some of them:

Misalignment with Out-of-the-Box Functionality:
Neglecting Security Model:
Overlooking Customization Best Practices:

3. Ineffectiveness and Anti-patterns

Effectiveness in the role of a Solution Architect is multifaceted and often undermined by common anti-patterns. These include:

Inefficient Meetings: Large (many participants), unproductive meetings with minimal active contributors can significantly impede progress. Architects should ensure that discussions are purposeful and involve individuals actively contributing to the conversation.
Fear of Responsibility: Shared responsibilities without clear ownership can lead to confusion and accountability issues. Architects should embrace accountability instead of relying on collective responsibility, ensuring clear and transparent architecture and its deliverables.
Reluctance (or fear) to Delegate: Unnecessary restrictions on the responsibilities of team members hinder progress. Architects (and IT Managers) should empower their team members, allowing them to take ownership of specific tasks.

The most ineffective decision, in my opinion, often masquerades as a “generic,” “unified,” “common,” or “universal” architectural “masterpiece.”

It’s an entirely inefficient solution that fails to address practical problems in the real world. Finally, time is wasted, and despite the illusion and self-pride of the architect-author for their aka-universal solution, it remains impractical in real-world applications. Other architects are constructing their own “universal masterpieces,” while competent architects tackle real-world problems here and now instead of engaging in endless discussions attempting to sell their “generic architectures.”

Example:

Imagine an architect tasked with designing a content management system (CMS) for a large corporation. Instead of delving into the organization’s specific needs, this architect decides to create a one-size-fits-all CMS solution. They develop a generic framework that claims to cater to every potential requirement across various departments without considering the diverse needs of each division.

However, this generic CMS lacks the specificity needed for individual departments. It doesn’t adequately address the nuanced requirements of the marketing, sales, or finance departments. While the architect might take pride in proposing a universal CMS solution, it fails to serve the practical needs of the organization. Other specialized architects might recognize this flaw and opt to build tailored solutions for each department, addressing their unique challenges effectively.

Ultimately, while the generic solution may seem comprehensive on paper, it lacks the practicality and functionality to address the diverse and specific needs of the organization’s various departments. This exemplifies the pitfalls of prioritizing a universal solution over tailored, practical, and specialized architectures for specific business functions.

At the same time, the “universal” solutions have their unique place and relevance. However, the context in which generic solutions are appropriate is distinct and often differs significantly from traditional, specific, and point solutions. Generic solutions are often considered platforms with highly sophisticated architectures.

I’m going to write a dedicated article about platform architecting and where the complexity is. About understanding the challenges, innovations, and strategic nuances that architects grapple with while navigating the platform development. The article will be available by link The Dilemma of “Universal” Architectures: Balancing Efficacy with Practicality. Stay tuned!

4. Valuing Seniority Over Expertise

A common misjudgment in the corporate sphere is the tendency to prioritize seniority over technological expertise. Placing architects with insufficient knowledge in critical roles can result in suboptimal solutions.

When organizations place architects in pivotal roles based primarily on their longevity within the company rather than their depth of technological proficiency, it poses a substantial risk. The assumption that years of service equate to mastering critical and cutting-edge technologies may not always hold true. This practice can result in architects overseeing projects without specialization in the critical and necessary technologies.

While longevity within an organization is undoubtedly valuable, it should not be the sole criterion for entrusting architects with pivotal roles. A well-rounded evaluation considering experience and technological expertise is crucial for fostering a dynamic, innovative, and adaptive environment where Solution Architects can genuinely excel in steering organizations toward technological excellence.

Example:

A senior Solution Architect is assigned to a project without a deep understanding of the technologies involved. Despite their experience, they struggle to provide effective and practical solutions, highlighting the importance of relevance and up-to-date knowledge in the fast-paced IT landscape.

5. Lack of Continuous Learning

In the rapidly changing world of technology, stagnation is a dangerous path. Solution Architects who become complacent and fail to stay abreast of emerging technologies risk becoming obsolete.

Example:

An architect who neglects continuous learning cannot recommend or implement cutting-edge solutions, limiting the organization’s ability to innovate and stay competitive.

6. Lack of Communication and Collaboration

Effective communication and collaboration are the cornerstones of successful architecture. Architects must communicate their ideas clearly and actively collaborate with cross-functional teams. Failure in communication can lead to misunderstandings, delays, and, ultimately, project failures.

Example:

An architect fails to communicate crucial design decisions to the development team, resulting in implementing features that deviate from the intended architecture. This lack of communication can lead to rework, wasted resources, and a compromised project timeline.

7. Insufficient Focus on Non-Functional Requirements

While functional requirements are essential, neglecting non-functional requirements can lead to architectural deficiencies. To ensure a robust and well-rounded solution, architects must balance their focus on functional and non-functional aspects, such as performance, scalability, and security.

Example:

An architect designs a system with a strong emphasis on functionality but overlooks scalability considerations. As a result, the system struggles to handle increased user loads, impacting its performance and user experience.

8. Overlooking the Human Element

Architects are responsible for designing technical solutions and understanding and addressing the human aspect of technology implementation. Neglecting the user experience, feedback, and the solution’s impact on end-users can lead to suboptimal solutions.

Example:

An architect designs a complex system without considering the end-users level of technical expertise. This oversight leads to a solution that could be more challenging for users to adopt, resulting in resistance and decreased overall productivity.

9. Failure to Iterate and Adapt

The iterative nature of architecture demands continuous refinement and adaptation. Architects who stick rigidly to initial designs without considering evolving project requirements or emerging technologies may find their solutions outdated and inefficient.

Example:

An architect adheres strictly to the initial design without incorporating feedback from ongoing development. This lack of iteration results in a solution that aligns differently with the evolving project needs, leading to increased project costs and a less-than-optimal outcome.

10. Ignoring Industry Best Practices and Standards

Architects may sometimes disregard established industry best practices and standards in pursuing innovation. While creativity is encouraged, ignoring proven methodologies can lead to unanticipated challenges and compatibility issues.

Example:

An architect decides to implement a custom authentication mechanism instead of using established industry standards. This deviation introduces security vulnerabilities and complicates integrating the solution with existing systems.

Bonus

And finally, never, ever do this. There is a “special” category (or species) of colleagues. When meeting them in person, everything seems agreeable—they engage in friendly conversation, affirm your statements, and positively respond to your project development requests. However, when they open Outlook or any other mail client, it’s as if a mask is mysteriously lifted, and a cringeworthy transformation unfolds, literally and figuratively. What seemed like a friendly conversation just minutes ago abruptly shifts into a distortion of facts, a renouncement of previously stated agreements, and an outright disregard for mutual understanding. It’s disheartening, to say the least, to find yourself in such circumstances with these pseudo-colleagues.

Example:

I’ll do without providing examples here.

Conclusion

Mastering the craft of IT Solution Architecture requires a holistic understanding of technical, organizational, and human elements.
By delving into the intricacies of these ten common mistakes, architects can gain valuable insights into the nuances of their role.
Avoiding these pitfalls, embracing continuous learning, and fostering effective communication and collaboration are pivotal steps toward becoming an exceptional Solution Architect.
This extensive exploration serves as a comprehensive resource, offering a roadmap for architects to navigate the complexities and challenges inherent in their crucial position within the ever-evolving landscape of Information Technology.

Thank you!

Azure for Architects: My Journey to Mastering the Cloud Certification

Dmytro Golodiuk — Wed, 08 Nov 2023 22:07:33 +0000

In today’s fast-changing tech world, staying on top of your game is crucial, especially for Solution Architects. The cloud has become the backbone of modern IT solutions, and Microsoft’s Azure Cloud is leading the charge. Let me take you on a journey to explore why Azure Cloud is a game-changer for Solution Architects like us and how I’m working on leveling up my skills with it.

My Journey, Not a Sales Pitch

Before we dive in, I want to clarify: I’m not here to recite Microsoft’s marketing pitch or certification guides. You can easily find those on your own. Instead, I want to share my thoughts on the learning and practical aspects. Certifications are a part of the journey, not the destination. It’s all about getting our hands dirty and applying what we’ve learned in the real world.

I’ve been through my fair share of exams and certifications. I’m gearing up for the Azure Solutions Architect Expert Microsoft Certification, and I’d love to take you along on my roadmap.

In one of my previous posts “Certification for Architects: Unveiling 10 Expert Tips and Tricks” I was sharing the recommendations how to efficiently organize the preparation process for the certification. I use Notion software for structuring my projects and tasks.

Certifications aren’t one-size-fits-all; they should be a deliberate choice that adds value to your professional journey. One common pitfall in preparation is skimming through learning modules without getting hands-on. Trust me, that approach won’t cut it. To succeed, you need a deep understanding of the subject matter and the ability to apply that knowledge in the real world. Practical experience is just as valuable as what you find in the textbooks.

Certification: IS and ISN’T

IS	ISN’T
The validation of your expertise in cutting-edge technologies	An endpoint but a continuous journey of learning and growth.
Your commitment to staying at the forefront of innovation.	A substitute for real-world experience, but it complements and validates your practical skills.
The foundation for building trust and credibility with clients and employers.	About memorizing facts but understanding and applying concepts effectively.

Azure Cloud Certifications

So, what’s in it for Solution Architects like us in the Azure Cloud realm? Well, there are several Azure Cloud certifications to choose from:

Microsoft Certified: Azure Solutions Architect Expert : This one is for the seasoned pros who’ve got it all – advanced IT operations knowledge, including networking, virtualization, security, and more. You’re the go-to person for translating business requirements into Azure solutions that align with the Azure Well-Architected Framework. You must pass Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions to earn this certification.
Microsoft Certified: Azure Administrator Associate : If you’re more into implementing, managing, and monitoring an organization’s Azure environment, this certification is your jam. You’ve got to pass the AZ-104 exam to earn this one.
Microsoft Certified: Azure Network Engineer Associate : This one’s all about designing efficient, secure, and well-architected Azure solutions involving network components. It’s like becoming a networking wizard in the Azure ecosystem. To snag this, you’ll need to pass the AZ-700 exam.
Microsoft Certified: Cybersecurity Architect Expert : This certification is your gateway to becoming a security maestro. It equips you to design solutions with security at the forefront, ensuring data and systems stay safe and sound.
Microsoft Certified: Power Platform Solution Architect Expert : If you’re all about creating custom business solutions, automating processes, and providing valuable data insights, this one’s for you. It’s all about leveraging the Power Platform to meet unique business needs.

Azure Cloud: Elevating Solution Architects

Embracing Azure Cloud opens a world of benefits for Solution Architects like us. Let’s take a quick peek.

Sharper Skills

Tech never stands still, and neither should we. Azure is the perfect playground for keeping our skills razor-sharp. It’s an innovation hub, with services and features constantly evolving. So, by diving into Azure, we’re not just encouraged but pushed to keep learning. As we interact with Azure’s diverse offerings, we develop the skills to design more efficient, cost-effective, and secure solutions.

Fortified Security

In today’s digital landscape, data security is a top priority. Azure is renowned for its robust security features, guarding against cyber threats. It offers encryption, identity and access management, compliance, and monitoring tools to protect an organization’s data and applications. By embracing Azure, we contribute to a safer digital environment for our employees.

Structured Learning

Azure isn’t just a platform; it’s a goldmine of learning resources. You’ll find online courses, in-depth documentation, and certification exams to help you level up your knowledge. Azure’s documentation is a gem known for its depth and clarity. And those certifications? They’re like badges of honor, boosting your career. With Azure’s structured learning environment, you’ve got all the tools you need to reach your professional goals.

.NET Nirvana

For those of us working with .NET, Azure Cloud is a dream come true. Azure and .NET work like a charm together, making developing and deploying applications a breeze. It simplifies creating solutions for .NET-based apps, leveraging Azure’s robust infrastructure and tools.

AI Awesomeness

Artificial Intelligence is the future, and Azure is at the forefront. Azure offers various AI services, including machine learning, cognitive, and bot services. As Solution Architects, we can tap into these offerings to develop intelligent applications that automate tasks, analyze data, and provide valuable insights. By integrating AI into our solutions, we stay on the cutting edge of technology.

Azure Cloud Adoption Frameworks

Azure offers various services and frameworks to support us on our cloud journey. Two standouts are:

The Azure Well-Architected Framework : This gem provides a structured methodology for designing secure, high-performing, resilient, and efficient solutions on Azure. It ensures you’re in line with best practices and Azure’s standards, helping you build solutions that are not just effective but also sustainable, secure, and cost-efficient.
The Azure Cloud Adoption Framework : Think of this one as your roadmap for success. It helps you navigate the complexities of cloud adoption and ensures it aligns with your client’s business goals and requirements. It’s a handy guide to have in your back pocket.

So, Azure Cloud adoption is a game-changer for us Solution Architects. It equips us with the tools and knowledge to thrive in a dynamic and competitive landscape. From honing our skills to enhancing security measures and diving into the world of AI, Azure Cloud opens up a world of possibilities. With the support of frameworks like the Azure Well-Architected Framework and the Azure Cloud Adoption Framework, we can confidently embark on this journey, knowing we’ve got the resources and guidance needed for success.

Azure Learn: Your Gateway to Cloud Mastery

Azure Learn is Microsoft’s free online learning platform with many courses, learning paths, and certifications for Azure Cloud. It’s designed to help professionals learn new skills and advance their careers in Azure Cloud.

Benefits for Solution Architects

Azure Learn is a goldmine of resources for us Solution Architects:

Flexible Learning : You can learn at your own pace, fitting it into your schedule.
Hands-on Experience : Azure Learn gives you hands-on experience with Azure Cloud services, helping you develop practical skills for real-world scenarios.
Community : Connect with fellow professionals passionate about Azure Cloud. Learn from their experiences and expand your network.

Relevant Modules for Solution Architects

Here are some Azure Learn modules tailored just for us:

Architect modern applications in Azure learning path : Learn how to build modern applications using Azure’s PaaS services for applications, caching, containers, and Kubernetes.
Microsoft Azure Solutions Architect: Design an Application Architecture : Dive into designing application architecture in Azure. It covers microservice architecture, orchestration, automation solutions, and API integration using Azure API Management.
Infrastructure Solutions for Microsoft Azure Architecture : This course is all about designing reliable, scalable, and secure solutions as an Azure Architect.

… and One More Thing: Microsoft Applied Skills

And just when you thought it couldn’t get any better, Microsoft has rolled out “Microsoft Applied Skills.” It’s all about showcasing your real-world technical skills. With the ever-evolving landscape of AI, cloud computing, and emerging tech, there’s a growing demand to prove your proficiency in these areas.

Microsoft Applied Skills lets you validate and align your skills with your business goals. It empowers you to stand out when working on critical projects within your organization. These credentials cover various technical areas, like securing Azure Files, configuring secure access using Azure networking, deploying and configuring Azure Monitor, and more.

To earn these credentials, you can prepare with optional training, including self-paced learning paths on Microsoft Learn and instructor-led training. After preparation, you’ll take an online, interactive, lab-based assessment within Microsoft Azure or Microsoft Power Platform products. Once earned, you can display these credentials on your LinkedIn profile to showcase your skills to your professional network.

Microsoft Credentials feature comparison.

Summary

So, there you have it, my journey into Azure Cloud and how it’s making a difference for Solution Architects like us. From mastering the latest tech to beefing up security and delving into AI, Azure Cloud is the key to unlocking new possibilities. And with Azure Learn and Microsoft Applied Skills, the sky’s the limit for what we can achieve. Let’s keep learning and evolving in this exciting tech world!

Useful Links

Announcing Microsoft Applied Skills, the new credentials to verify in-demand technical skills
John Savill’s Technical Training: This Youtube channel focuses on videos designed to help you learn. Big focus on Azure, DevOps, PowerShell and other Microsoft technologies.
John Savill’s Onboard Azure Website
Book: Azure for Architects: Create secure, scalable, high-availability applications on the cloud, 3rd Edition
Azure Well-Architected Framework
Azure Cloud Adoption Framework
Microsoft Certified: Power Platform Solution Architect Expert
Microsoft Certified: Cybersecurity Architect Expert
Microsoft Certified: Azure Solutions Architect Expert

Thank you!

Exploring European Digital Identity Wallet

Dmytro Golodiuk — Fri, 20 Oct 2023 11:26:20 +0000

Hey there! So, I recently got my hands on the 2023 Report on the state of the Digital Decade, and it’s packed with exciting stuff. This report gives us a comprehensive overview of the progress towards achieving digital transformation within the Digital Europe Programme, and European Digital Identity particularly.

Preface

The Digital Europe Programme (DIGITAL) is this new EU funding program, and it’s all about bringing digital tech to businesses, citizens, and public administrations. They’re supporting projects in five key areas: supercomputing, artificial intelligence, cybersecurity, advanced digital skills.

On the 19th of December 2022, a game-changer dropped – Decision (EU) 2022/2481. It’s like the blueprint for the Digital Decade Policy Programme 2030. This is where things get interesting.

The Digital Decade is the roadmap for all things digital in the EU. It’s got Digital Decade Policy Programme that allows the EU and Member States to join forces and hit those Digital Decade targets. Plus, it’s got a system to track progress until 2030. The Commission is on it, they promise an annual progress report!

Speaking of exciting updates, here’s something you might find interesting. Mykhailo Fedorov, Deputy Prime Minister of Ukraine for Innovation, Education, Science, and Technology, shared some surprising news on July 12 this year. He shared that Diia (the Ukrainian digital ecosystem) is part of the team developing the European Digital Wallet.

Now, let’s delve into the key aspect – the European Digital Identity Wallet. It’s part of the Digitalization of public services, just as I mentioned earlier in the Digital Decade EU Framework. So, what’s the deal with this wallet?

Source: ec.europa.eu

Background

Imagine a Digital Identity for every European. It’s like your personal digital wallet, available for EU citizens, residents, and businesses to prove who they are and share certain personal info. Online, offline, all over the EU. It’s quite remarkable, don’t you think?

And guess what? Every EU citizen and resident in the Union will have their very own personal digital wallet. No more fussing with paper documents! Say goodbye to forgotten passports at the airport, endless back-and-forth at banks when applying for a loan, and those dreaded delays at the doctor’s office waiting for your medical records to arrive.

Ursula von der Leyen, President of the European Commission

“Every time an App or website asks us to create a new digital identity or to easily log on via a big platform, we have no idea what happens to our data in reality. That is why the Commission will propose a secure European e-identity. One that we trust and that any citizen can use anywhere in Europe to do anything from paying your taxes to renting a bicycle. A technology where we can control ourselves what data is used and how.”

– Ursula von der Leyen, President of the European Commission, in her State of the Union address, 16 September 2020,

Now, creating a National Digital Identity system is no walk in the park. It comes with costs, technical challenges, and potential adoption issues. But I am sure, the end result is totally worth it. As a tech enthusiast and user of the Ukrainian Diia Service , which is like a “State in a Smartphone,” I can tell you, it’s a game-changer. You can store your driver’s license, passports, and more on your phone. As well as to share the documents’ copies when obtaining banking or postal services, checking into a hotel, and in other life situations. Additionally, through “Diia” (the application and portal), you can access state services for child birth, register a business and individual entrepreneur online, pay taxes and submit declarations, sign any documents, change your place of registration, and more.

Benefits of the European Digital Identity

Everyone gets a digital identity that works anywhere in the EU.
You’re in control of what you share with services.
It’s all in a digital wallet, right on your phone, for identifying, sharing info, and confirming rights in a Member State.

Practical Use Cases

Now, this digital wallet isn’t just for show. You can use it for a bunch of things – from filing tax returns hassle-free, applying for a university, whether you’re doing it from home or in another Member State of the EU, storing a medical prescription, proving your age without digging out your ID, renting a car using a digital driving license, and making hotel check-ins a breeze.

Timeline / Roadmap

Let’s take a closer look at the roadmap.

Timeline: Digital Identity in Europe

It all started back in June 2021 when the European initiative took its first steps. Back then, the European Commission intends to implement its cross-border European Digital Identity Wallet vision fully. The European Commission made a significant move by adopting a Recommendation. This called upon Member States to collaboratively develop a ‘Toolbox,’ a comprehensive package comprising a technical Architecture and Reference Framework (ARF), a set of common standards and technical specifications, and a collection of common guidelines and best practices. All these elements would serve as the groundwork for implementing the European Digital Identity Framework proposal.

But here’s where things get really interesting: On February 10, 2023 , the Commission unveiled the first-ever ’technical Toolbox’ for the prototypes of European Digital Identity Wallets. This technical backbone, developed by Member States in close cooperation with the Commission, forms the very foundation for engineering a prototype Wallet that can be tested across various use cases. It’s important to note that the requirements and specifications within this Toolbox will become mandatory once the legislative process on the European Digital Identity framework has been finalized.

Come April 2023 , the stage was set for the commencement of pilot projects. The Commission is investing €46 million from the Digital Europe Programme in four large-scale pilot programs.

With all this work in progress, the current plan is to make the first nationwide wallets available to citizens by 2025.

EU Digital Identity Wallet Pilot Implementation

| Wallet Prototype

The European Commission will provide a prototype of an EU Digital Identity Wallet (EUDI) set out in the proposed European Digital Identity Regulation. An initial version of the reference implementation will be made available on GitHub with the first complete version of the common EU Toolbox to implement the EU Digital Identity Wallet in September 2023.

When writing this post, only the initial version of Architecture and Reference Framework (v1.0.0) was published on 26 January 2023. The minor update (v1.1.0) was introduced on 20 April 2023 and included the addition of service blueprints for use cases on Identification & authentication to access online services and Mobile driving license.

| Large Scale Pilots

Before rolling it out to Member States, the EU Digital Identity Wallet is being put through its paces in four substantial pilot projects that kicked off on April 1, 2023. These pilots aim to put the EU Digital Identity Wallet to the test in a variety of real-life scenarios. They’re covering everything from Mobile Driving Licences to eHealth, payments, and education and professional qualifications. The ‘Pilots’ phase is all about preparing, developing, and rigorously testing these pilot programs, ensuring they seamlessly integrate into the European Digital Identity Wallet.

The 4 pilot projects involve more than 250 private companies and public authorities from over 25 Member States, Norway, Iceland, and Ukraine! These pilots will run for a minimum of 2 years.

POTENTIAL – Pilots for European Digital Identity Wallet Consortium

EWC – EU Digital Identity Wallet Consortium

NOBID – Nordic-Baltic eID Wallet Consortium

DC4EU – Digital Credentials for Europe Consortium

These consortiums are tackling 11 priority use cases, all with the aim of improving citizens’ access to highly trusted and secure electronic identity solutions. These pilot projects cover the full spectrum, from the issuance of the wallet to the end-users and the integration of personal identity information, additional documents, and how this information is presented to service providers.

So what are these 11 use cases, you ask? They’re diving into:

Access to Electronic Government services
Opening a Bank Account
Registration for Mobile SIM
Mobile driving license
Remote Qualified Electronic Signature
ePrescription
Digital Travel Credentials
Organizational Digital Identities
Payments (Account-to-Account, Card-Based, Possibly Token-based)
Educational credentials and professional qualifications
Portable Document A1 (PDA1) & European Health Insurance Card (EHIC)

The 4 pilot projects are implemented by the respective consortium bringing together public and private actors from different Member States. You can see the areas and use cases they explore in the table below.

Country	POTENTIAL	NOBID	DC4EU	EWC
Belgium	1,4,5
Bulgaria
Czech Republic	3,6	9		8
Germany	1,2,3,4,5		10	7,8,9
Denmark		9	10, 11
Estonia	4
Ireland			11
Greece	1,2,3,4,5,6		10	7,8
Spain	4,6		10	7
France	1,2,3,4,5,6			8,9
Croatia
Italy	1,4,6	9		8
Cyprus	1,4,5,6
Latvia		9
Lithuania	4		10
Luxembourg	1,2,3,4,5		10	7
Hungary	6			7
Malta			10
Netherlands	1,3,4	9	11	8
Austria	1,2,3,4,5,6		11
Poland	1,3,4,6			7
Portugal	1,2,4,5,6		10,11
Romania			10	9
Slovenia	1,2,5		10
Slovakia	1,4,5
Finland	1,4			7,8
Sweden			10	8,9
Norway		9	10	8
Iceland	9
Switzerland				7
Ukraine	1,2,3,4,5,6			9

About DIIA

This post isn’t about the Ukrainian Diia program, which is an initiative that truly deserves its own dedicated post. Don’t worry, though – I promise to dive deep into its history, the services it offers, and how it’s transforming the user experience for Ukrainian citizens in their interactions with the government. Stay tuned for that!

For some background, Diia first stepped onto the scene on September 27, 2019, thanks to the Ministry of Digital Transformation of Ukraine. It was introduced as part of the “State in a Smartphone” project, a bold move by Vice Prime Minister and Minister of Digital Transformation Mykhailo Fedorov. The vision? To create a mobile app and web portal that would bring together all the services provided by the state to citizens and businesses, all in one convenient place.

Ukraine’s Vice Prime Minister and Minister of Digital Transformation Mykhailo Fedorov presents Diia, Ukraine’s groundbreaking e-governance app

🎉 Fast forward to February 6, 2020, and the official launch of the Diia mobile app. It’s been a game-changer ever since, making life easier for Ukrainians in countless ways.

And guess what? This year, Diia is stepping into the European Digital Wallet development game. Right now, the POTENTIAL consortium (PilOTs for European Digital Identity Wallet) is at work, creating a European service that makes opening bank accounts online and storing documents on your smartphone a breeze. The Ministry of Digital Transformation team, Mykhailo Fedorov, showcased the Diia’s capabilities to their European counterparts in Paris, demonstrating how you can open a bank account in minutes, create an electronic signature, and harness the power of digital documents.

Exciting times are ahead. Stay tuned for more updates as this EU digital journey unfolds! 🚀🌍🇪🇺

Conclusion

The 2030 Digital Decade policy program is like Europe’s roadmap to digital transformation. The EU Digital Identity Wallet is there to support the journey. By 2030, key public services should be online, everyone should access their health records, and we should all have secure privacy-enhancing eIDs.

This wallet builds on the cross-border legal framework called eIDAS Regulation (European Electronic Identification and Trust Services Initiative) that’s been adopted since 2014. It’s like the backbone for cross-border electronic identification and authentication in the EU.

To keep tabs on the digital journey, the Commission is using the Digital Economy and Society Index (DESI) for their annual check-up on Europe’s digital performance.

So, that’s the overview of the Digital Decade and the European Digital Identity Wallet.

Before we wrap things up, I’d like to invite you to stay in the loop with all the latest updates. Feel free to connect with me on social media and join my new channel ‘ArchiCrаft Corner’, available on both WhatsApp and Telegram. Let’s keep this conversation going and explore the digital world together! 🚀📲"

Lear More

Thank you!

Certification for Architects: Unveiling 10 Expert Tips and Tricks

Dmytro Golodiuk — Mon, 09 Oct 2023 00:00:00 +0000

Efficiently organizing the preparation process for the Microsoft Certified: Azure Solutions Architect Expert certification, or any certification, involves a mix of strategies and techniques. Here are some recommendations, tips, and tricks to help you make the most of your preparation.

1. Create a Study Plan

Begin by setting clear goals and a realistic timeline for your preparation.
Break down the syllabus into manageable sections and allocate time for each.

I use Notion software for structuring my projects and tasks. Notion offers a practical solution for project and task management, seamlessly integrated with notes and documents. It provides a centralized platform where I can efficiently manage my work without the need to switch between multiple tools. Notion’s customizable templates and flexible views make it user-friendly, allowing to tailor it to my specific project management needs. It’s especially beneficial for breaking down large projects into manageable tasks and maintaining clarity and collaboration within teams. Here is how it looks. Please overview several screenshots of my setup.

My Projects in Notion.

My Project Tasks in Notion.

2. Utilize Official Documentation and Resources

Microsoft provides official documentation and training materials. These should be your primary sources for study.
Take advantage of virtual labs and hands-on exercises to gain practical experience.

3. Mind Maps and Note-taking

Creating mind maps can be an excellent way to visualize complex concepts and their relationships.
Additionally, maintain organized notes summarizing key points and essential details.

I prefer using the Miro. Miro streamlines mind mapping with templates, real-time collaboration, and integration with productivity tools. It enables easy creation, sharing, and enhancement of mind maps for efficient teamwork and idea visualization. I am sharing with you one of my Miro boards with mind map that I made when preparing to AZ-700 and AZ-104 exams, specifically for Azure Networking.

Azure Networking: mind map in Miro.

4. Practice with Sample Exams

Seek out practice exams and questions related to the certification. These can help you gauge your knowledge and test-taking skills.
Analyze your mistakes and areas where you need improvement.

5. Join Online Communities

Participate in forums, discussion groups, or social media communities dedicated to Azure and the certification.
You can gain insights, share experiences, and ask questions to clarify doubts.

6. Hands-On Practice

Apply what you learn by working on real-world scenarios. Build and manage Azure solutions to reinforce your understanding.
Consider setting up a personal Azure sandbox environment for experimentation.
Take practice exams under timed, exam-like conditions to get a feel for the test environment.
Periodically review previously covered topics to reinforce your memory and understanding.

Here, it’s worth mentioning that Microsoft Azure provides plenty of services available for free. That’s enough to try Azure solutions and hone your hands-on experience.

Azure Free Resources.

7. Stay Consistent

Stick to your study plan and maintain a regular study schedule. Consistency is key to retaining information.
Avoid cramming, as it may lead to temporary retention without a deep understanding.

8. Seek Guidance and Mentorship

Connect with experienced Azure professionals who can offer guidance and mentorship.
They can provide valuable insights and advice based on their certification journeys.

9. Stay Updated

Keep up with Azure-related news, updates, and trends. Microsoft Azure is a dynamic platform, and staying informed is essential.

🛜 Subscribe to my channels and never miss an update about cutting-edge architecture, especially when it comes to the powerful world of Microsoft Azure!

💬 Messengers: WhatsApp | Telegram

👥 Social platforms: LinkedIn | Pinterest | Facebook | Instagram | X (Twitter)

For those who prefer to get their updates via RSS, subscribe to the feed at RSS Feed.

10. Use Online Learning Platforms

Explore online learning platforms like Pluralsight, Udemy, or Coursera, which offer courses tailored to Azure certifications.
These platforms often include video lectures, quizzes, and practical exercises.
Explore Youtube channels devoted to specific technologies.

💡 Bonus Tip: Celebrate Milestones

Acknowledge your achievements along the way, whether completing a challenging module or passing a practice exam. Reward yourself for your hard work.

In Conclusion,

Remember that the journey towards certification is as important as the destination. Stay motivated, adapt your study methods as needed, and approach your preparation with a growth mindset. With dedication and effective organization, you’ll be well-prepared to ace the Microsoft Certified: Azure Solutions Architect Expert certification.

Bonus Tip: Celebrate Milestones: Acknowledge your achievements along the way, whether completing a challenging module or passing a practice exam. Reward yourself for your hard work. a

Remember that the journey towards certification is as important as the destination. Stay motivated, adapt your study methods as needed, and approach your preparation with a growth mindset. With dedication and effective organization, you’ll be well-prepared to ace the Microsoft Certified: Azure Solutions Architect Expert certification.

Helpful materials

Thank you!

Certification for Architects: A Career Catalyst or Just Empty Credentials? Let's Deliberate

Dmytro Golodiuk — Fri, 06 Oct 2023 00:00:00 +0000

In the fast-paced era of the digital revolution, where information technology is at the heart of business and industry, the role of IT Solutions architects has become more critical than ever. These architects are the masterminds behind the intricate systems that power our modern world. However, in the pursuit of excellence in this field, one question often arises: Is certification essential for senior IT architects? In this blog post, we will explore the significance of certification, with a particular focus on the Microsoft Certified: Azure Solutions Architect Expert, and whether it’s a worthwhile endeavor for senior developers.

Defining the Target Audience: Who Needs Azure Solutions Architect Expert Certification?

Before diving into the world of certifications, it’s crucial to understand who exactly benefits from the Microsoft Certified: Azure Solutions Architect Expert certification. This certification is tailor-made for professionals looking to design and manage solutions in the realm of cloud computing, specifically on the Azure platform. It’s ideal for architects, system engineers, and other IT professionals with aspirations to specialize in Azure. For these individuals, this certification can be an auxiliary step (but IMHO not pivotal) step in their career, offering them recognition and trust from both employers and clients alike.

The Importance of Strategic Alignment

However, not all senior IT system architects need to embark on the journey towards the Azure Solutions Architect Expert certification. It’s vital to consider whether this certification aligns with your career goals and specialization. If your daily work doesn’t involve Azure or you have no intention of venturing in that direction, investing valuable time and resources into this certification can be counterproductive.

Certifications can be potent tools for career progression, but they should serve a purpose in your professional journey. It’s advisable to have a strategic plan that outlines your career goals and how certifications fit into this roadmap. For instance, if your current or future role involves Azure-based solutions, then pursuing this certification can be a game-changer. On the other hand, if your expertise lies elsewhere, it’s wise to explore certifications that directly complement your chosen path.

The Path to Certification Excellence

For those who find themselves in the Azure realm and decide to pursue the Microsoft Certified: Azure Solutions Architect Expert certification, it’s not a journey to be taken lightly. This certification demands significant effort and dedication.

Preparation for this certification goes beyond mere memorization of answers; it requires a deep dive into every facet of cloud computing on the Azure platform. Microsoft offers a wealth of resources to aid in your preparation, including documentation, training materials, and virtual labs. Leveraging these resources is crucial to building a strong foundation of knowledge.

One common pitfall during preparation is the temptation to take shortcuts or skim over critical details. To succeed, a profound understanding of the subject matter and the ability to apply that knowledge in real-world scenarios is paramount. Real-world experience and hands-on practice can be as valuable as book knowledge when it comes to certification exams.

In Conclusion

In the realm of IT system architecture, the Microsoft Certified: Azure Solutions Architect Expert certification can be a game-changer. It opens doors to new opportunities, enhances your credibility, and showcases your expertise in the Azure ecosystem. However, it’s vital to evaluate whether this certification aligns with your career goals and aspirations.

Certifications are not one-size-fits-all; they should be a deliberate choice that contributes meaningfully to your professional journey. If Azure is your domain, investing the necessary effort in preparing for this certification can lead to a successful outcome. Ultimately, the path to certification excellence lies in thoughtful consideration, strategic alignment, and unwavering dedication to your chosen specialization.

In the next post I will tell how I organize the preparation process for such mid- and long-term endeavors like certification or learning new fields. Stay tuned!

Thank you!

Explore the Cutting-Edge Technology Behind My Personal Website Built on Hugo

Dmytro Golodiuk — Fri, 29 Sep 2023 23:00:00 +0000

In the ever-evolving world of web development, the choice of technology stack can make all the difference in how your website performs and how easy it is to manage. For my website, I decided to go with Hugo, a static site generator that has gained popularity for its speed and simplicity. In this blog post, I will walk you through the architecture of my website, highlighting the key components and tools that make it all come together seamlessly.

Introduction to Hugo

Hugo is a static site generator written in Go. It’s known for its blazing-fast build times and the ability to create incredibly lightweight websites. Hugo doesn’t require a database or server-side processing, making it a perfect choice for blogs, portfolios, and personal websites. It uses Markdown for content and provides a highly customizable templating system.

Logical Architecture

My website comprises several components and subsystems that work together to deliver a fast and reliable web experience. Here’s a breakdown of these elements:

Hugo - The Static Site Generator

At the heart of my website is Hugo. It transforms my content in Markdown and the website’s templates into static HTML files. This approach ensures rapid loading times and enhances security by eliminating common vulnerabilities associated with dynamic sites.

Azure Storage Account

I’ve chosen an Azure Storage Account with the “Static Website” feature enabled for hosting. This setup provides a cost-effective and scalable hosting solution. Azure Storage serves as the storage medium for my website’s static assets and HTML files.

Cloudflare

To manage domain registration, content delivery, SSL/TLS certificates, DNS management, analytics, and logs monitoring, I’ve integrated Cloudflare. Cloudflare is a Content Delivery Network (CDN) to distribute my website’s content globally, ensuring low latency and high availability.

Source Code Repository

I store the source code of my website in a GitHub repository. This allows me to easily track changes, and leverage GitHub’s robust version control features.

CI/CD with GitHub Actions

To automate the build and deployment process, I use GitHub Actions. This CI/CD pipeline is triggered automatically on each push to the repository’s master branch and scheduled nightly to keep the website up-to-date. Here’s a snippet of my GitHub Actions workflow:

This workflow involves setting up Hugo, determining whether it’s a production build, initializing Azure variables, building the site, purging Cloudflare CDN cache, and deploying the build artifacts to the Azure Storage Account.

Hosting and Deployment

The hosting and deployment process for my website is orchestrated by GitHub Actions and involves several steps:

Checkout Code : The workflow begins by checking out the latest code from the GitHub repository.
Set up Hugo : Hugo is set up with the specified version.
Determine Production Build : The workflow checks whether the current build is for production. It uses the master branch as a reference for production builds.
Initialize Azure Variables : Azure variables are initialized based on whether it’s a production or test build.
Build Site with Hugo : Hugo is used to build the website, and the appropriate base URL is configured.
See the Changes without Deployment : A dry run is performed to see the changes without actual deployment.
Purge Cloudflare CDN Cache : Cloudflare CDN cache is purged to ensure the latest content is served.
Deploy Build to Site : The final step deploys the build to the Azure Storage Account.

This CI/CD setup ensures that my website is continuously updated with the latest changes and delivers to users with minimal latency and maximum security.

In conclusion,

the architecture of my website, built on Hugo, is a testament to the power of static site generation and modern DevOps practices. With Hugo as the backbone, Azure Storage for hosting, and Cloudflare for content delivery, my website combines speed, security, and scalability into a harmonious web presence. GitHub Actions streamlines the development process, making maintaining and updating my site easy. By sharing this architecture, I inspire others to explore the world of static websites and discover their benefits for personal and professional projects. Content

Thank you!

How to prepare Software Architecture Diagrams automatically, easily and skillfully

Dmytro Golodiuk — Tue, 04 Aug 2020 13:52:29 +0000

Article about IT Architecture Diagrams. Why, when and how to deal with them. How to create diagrams from text. Tools for writing architectural diagrams.

Being engaged in IT Architecture, you certainly deal with documenting the architecture. Looking ahead, I notice that in this article I am not writing about the methodology, styles, and practices in the preparation of architectural documentation. Instead of this, I’d recommend a great book, “Documenting Software Architectures: Views and Beyond, Second Edition,” if the topic is interesting to you to invest some time into it.

I am focusing your attention on one aspect - diagrams. I will tell you a story about how to cook them (I mean diagrams) efficiently and skillfully so that you don’t waste time on “work for work”. Architects usually “draw shapes and lines” - it is thus that we are explained the role of IT architect in software development. Frankly speaking, this is hard to argue with. Indeed, architects prepare product roadmaps, flow diagrams, deployment diagrams, state diagrams, reference architects, etc.

More in detail about the role of IT Architects please go to my article using the link.

Diagrams, Do You Need Them?

Working with different teams on different products, I often catch myself thinking that it is not easy to create architectural “pictures” so that they are clear to stakeholders. But if they raise more questions than they answer, it means they are “unnecessary.” Here are some typical indicators:

What does this figure mean?
What does the different shape of the outline mean in the figures?
What does this line or arrow mean?
What type of communication/association is represented by this arrow or line?
What does this color mean?
Lack of connections between chart elements: are they isolated entities?
What do these abbreviations mean? (ambiguous / undocumented abbreviations)

If you document the architecture in such a way that the above questions do not arise in the readers, then we move on - the necessity for diagrams. Here, in practice, opinions are often divided into two opposing groups. The first is that you need to prepare as many architectural documents as possible, so to speak, just in case. Alternative opinion - no documentation is required, let’s leave it at that. By the way, such a situation is not only about IT architecture: business analysis documents, specifications, user manuals - all the same. Let’s go into details of this topic one by one.

Why Do We Prepare Architectural Diagrams?

Let’s start with the general overview. IT Architecture is roughly the partitioning of a whole into parts, with relations between these parts. The larger and more complex the system, the more critical the partitioning into pieces, and hence the architecture itself. Architecture is what makes the sets of these parts interact and work together successfully as a whole. Architectural documentation helps to:

make the right decisions by architects;
explain to developers how to implement such solutions;
tell the evidence and root cause of such decisions.

Merely creating an IT product architecture is not something self-sufficient. You should appropriately communicate it to those stakeholders who need it to turn it into a real product. The documentation “speaks” for the architect today. It is necessary so that the architect does not have to answer the same questions a hundred times. The documentation “speaks” for the architect tomorrow — when he or she will no longer work on this product.

Making an architecture without documentation is like doing business without advertising. Only you know what you are doing, no one else. Neither the company nor the product nor you need it!

When Do You Need To Work On Architectural Documentation? - Definitely Not After Development

Documentation is often interpreted in practice as “afterthought” — something people do because they have to do it. Something that needs to be done because “it’s okay.” Maybe a contract demands it. Perhaps a customer requires it. It might be required by internal policies or standards. This may all seem like the truth. I do not deny the fact that such reasons are justifiable. But I know for sure that with such a vision and attitude, you cannot count on success and high-quality documentation. Why should the architect spend time and energy just because the manager has a specific item called “architectural documentation” in the delivery checklist ?!

The best architects make the best architectural documentation, not because it’s “required,” but because they see that it’s essential for a particular case: creating a high-quality product and with as little “re-do” as possible.

The documentation helps an architect while the architecting is _ in progress, not after. _

A Picture’s Worth A Thousand Words — It’s About Architectural Diagrams

So, we got a sense of the question why? you need to document the architecture and when? you need to do it. But what should be placed in this documentation, how to find a balance between quality and quantity? I remind you that our primary focus is on architectural diagrams.

“A Picture’S Worth A Thousand Words” — the same applies to architectural diagrams. I am convinced that an epicenter of any architectural document is diagrams. By creating architectural diagrams, we reflect the internal structure and behavior of the IT product. But unfortunately, very often, the result is a far cry from the desired state. Either these diagrams are too detailed and overloaded, or on the contrary - indistinct and irrelevant. Such “pictures” cause more questions than give answers. They don’t have a value at all - as a result, we waste time.

Even when we have managed to find a balance between quantity and quality, and the architect and team have created the diagrams that are really needed and relevant, we rarely keep such documentation updated according to product changes. Why is this happening? I see the following reasons:

developers are often not in favor of ideas to create and maintain technical documentation; they consider it a redundant, exhausting and time-consuming process, arguing that the source code is enough;
costs for documentation support are not budgeted;
high costs for documentation support;
product life cycle management processes do not include aspects for updating and synchronizing documentation (and not only architectural) by the product changes (functional and non-functional requirements).

_ Disclaimer: _ This list does not claim to be full, and at the same time, I admit that there are always exceptions.

7 Rules To Make Your Architectural Diagrams Much Better

Let’s summarise the preceding. I offer the following 7 rules of “well-cooked” diagrams:

Write documentation from the reader’s perspective (developers, testers, business analysts, IT engineers, IT managers, etc.).
Avoid unnecessary repetitions and duplication in diagrams.
Avoid ambiguity.
Use and follow accepted standards.
Record the rationale of a decision (versioning, binding to a road map of a product).
Keep the documentation up to date.
Review the documentation for suitability.

How Can You Prepare Architectural Diagrams Better, But In Less Time?

Now we have the answers to the question what? should be diagrams so that they are valuable for the team, for the stakeholders. It is time to move on to how you can improve the process of creating and, more importantly, updating architectural diagrams.

Having limited the context of the article to diagrams, I will now focus exclusively on how you can optimize the process of their creation.

The benefits of having architectural documentation, including architectural diagrams, should outweigh the cost of creating them. The cost of documentation is primarily a human cost. Therefore, I realize that appropriate tools in the production process can support us and reduce our efforts in diagrams creation and maintenance. How is this possible?

The tool can generate diagrams from information already present as a result of design and development project activities.
As the IT solution evolves, the correspondent architectural diagrams should simultaneously evolve. The updating of architectural artifacts can be a part of Continuous Integration and run at the stage of building and preparing product artifacts for delivery.
A text editor is enough to create some diagrams.

It is difficult to find a team that does not use a version control system to manage the source code. Many organizations no longer even separate documentation from the source code repositories, and that’s great (hello GitHub, Azure DevOps, etc.). It’s just as convenient to write *.md files next to the source code files. And diagrams are an integral part of most architectural documents. What is the reason to prepare architectural diagrams somewhere in another editor, save them somewhere, and then just insert the final exported version into the markdown-file of the documentation ?! It seems inconvenient and illogical to me. I want to “write” diagrams in text, i.e., in markdown. And I do it in such a way, and I recommend the same to everybody of you.

How To Create Diagrams From Text

I suppose that you, as an architect, have your favorite set of modeling languages (AML - Architecture Modeling Language) and diagram types. There is something to choose from, there are no problems here. Then the logical question arises: how now to replace (partially, not wholly) MS Visio and switch to the Markdown editor? The answer is simple — markdown-like scripting languages for generating diagrams, graphs, charts, etc. from a text description. And here, I assure you that for almost any type of diagram, you will find a solution that allows you to declaratively describe your future visualizations. All this is also available through the CLI (Client User Interface) and on all platforms.

How not to hint at the pain when you live in two worlds simultaneously (Windows and macOS), and you’re used to MS Visio. Well, experts, of course, will now say that there is already MS Visio Online. I agree here that it’s like a breath of fresh air, but still, I don’t get tired of waiting for Visio for macOS.

Tools For “Writing” Architectural Diagrams

Here are some tools that you can use to prepare the diagrams by writing code (all as we love).

Mermaid

Mermaid — is a syntax similar to Markdown where you can use text to describe and automatically generate diagrams. With Mermaid’s Markdown-inspired syntax, you can generate flow charts, UML diagrams, pie charts, Gantt charts, and more. Moreover, it is already integrated with a massive number of different services and platforms, such as GitHub, Azure DevOps, Atlassian products, and many others.

Sample 1 — UML Flowchart

Flowchart — Mermaid

Sample 2 — Git Graph (I use it quite often to prepare the process documentation about software development teams collaboration)

GitGraph — Mermaid

PlantUML

PlantUML — allows to quickly “write” UML diagrams, Archimate diagrams, ERD-diagrams, С4-diagrams, Ditaa diagrams, Gantt diagrams, MinMap diagrams, WBS-diagrams, AsciiMath і JLaTeXMath notation.

Sample — ERD

ERD diagram — PlantUML

Nomnoml

Nomnoml — one more tool to create UML diagrams from text.

Sample.

UML Diagram — Nomnoml

BlockDiag

BlockDiag — simple diagram images generator, supports UML diagrams creation.

Sample.

Blockdiag

WaveDrom

WaveDrom — draws your Timing Diagram or Waveform from simple textual description.

Sample.

Wavedrom

GraphViz

GraphViz — open source graph visualization software.

Sample — Data Structures.

Data Structures — GraphViz

There are many other similar tools. I mentioned here only those ones I really use and can recommend.

I 🖤 (Mermaid, GraphViz <3 Azure DevOps)

My scenarios for using diagram generators are as follows:

A simple scenario – is a manual “writing” of diagrams, using the semantics of a tool. Most of all, I prefer Mermaid. I can create a visualization directly on the wiki page in Azure DevOps, instead of inserting a ready-made PNG or SVG image, after converting the “raw” diagram file.
Complex scenario – auto-documentation. I have solutions and products for which the documentation includes many different diagrams. Without revealing the details, I will give an abstract example. Suppose a solution architecture involves the use of Enterprise Service Bus for data exchange between several business systems. All the logic of system integration is implemented in the so-called integration packages, which essentially perform ETL operations on business data. The documentation is built automatically during the continuous delivery phase of each new version of the product. The following technologies are used:

Azure DevOps Pipelines (continuous integration & continuous delivery);
GraphViz for building the diagrams from XML-based data integration packages;
documentation is built by a library written in PowerShell (internal development), it also interacts with GraphViz.

Thus, using the tools for diagrams generating mentioned above (and similar ones) made it possible:

Significantly reduce the efforts on “manual” creation and maintenance of diagrams that reflect the structure and behavior of individual components.
Generate documentation in a fully automatic mode, without human cost.
Diagrams as code – is a way to get all the benefits of using version control systems while creating and maintaining architectural diagrams. To evaluate the effect, just imagine that your team missed the opportunity to use Git during development.

Kroki.io – A Unified API For Working With Architectural Diagram Generators

It would seem that this could be the end, if not for one moment. The variety of tools is, of course, a big deal. However, each of them requires some routine setup actions, such as installation, upgrade, configuration. And each of them brings its dependencies, according to the used technology stack: Ruby on Rails, Python, Java,…. As a result, I discovered for myself a hidden gem – Kroki.io. It is a tool that simply provides a unified API for interacting with BlockDiag (BlockDiag, SeqDiag, ActDiag, NwDiag, PacketDiag, RackDiag), BPMN, Bytefield, C4 (via PlantUML), Ditaa, Erd, GraphViz , Mermaid, Nomnoml, PlantUML, SvgBob, UMLet, Vega, Vega-Lite, WaveDrom … And much more is ahead!

A Few Words About Kroki.io

supports a vast number of tools for creating diagrams, graphs, charts, other visualizations from the text;
free;
open-source;
supports export to PNG, SVG, JPEG, PDF, BASE64;
available as a service (you do not need to do anything before start using it). But it is not production-ready, only as a demo version;
also available as self-hosted - you can install and configure for yourself. That’s what I did. All you need is Docker, Docker Compose. The installation and setup process takes a few minutes.

4 Steps To Starting Using Kroki.io

Install Docker. To check the installed version, run the following command in the terminal: docker —version
Launch the kroki container. At once I give the command with all parameters to start the container in detached mode, and to map your local port 8080 on port 8000 in the container. Execute the command in the terminal docker run -p8080:8000 -d yuzutech/kroki
Done. To check, run ‘/path/to/kroki version’ in termial. If the installation is successful, you will see the Kroki CLI version.
The command interface for interaction with Kroki looks like this: /path/to/kroki <command> [options] <arguments>

Let’s Move On To Practice

And this is how the work looks in practice.

Write code of ERD diagram in code editor -- file sample.erd

Run kroki convert on sample.erd

Docker image yuzutech/kroki allows you to work not with the whole set of available diagrams, only with the following:

/c4plantuml
/ditaa
/erd
/graphviz
/dot
/nomnoml
/plantuml
/svgbob
/umlet
/vega
/vegalite

In order to use BlockDiag, ActDiag, NwDiag, SeqDiag, Mermaid or BPMN you have to run additional set of containers: yuzutech/kroki-blockdiag, yuzutech/kroki-mermaid, yuzutech/kroki-bpmnTo simplify the process you can use docker-compose up -d to run few containers at once, using the already prepared file docker-compose.yml with the appropriate instructions. You will find all references to the documentation at the end of the article ⬇.

I have prepared a repository on GitHub, where you can find more than a dozen examples of different types of charts, their description in various notations, their graphical representation. The link is also at the end of the article.

Summing Up

Keep on developing your IT solutions by using just enough architectural documentation, diagrams. Don’t create them for any other reasons, especially if the team doesn’t need them.
“Manual” creation and maintenance of diagrams that reflect the structure and behavior of individual components in most cases is not an optimal approach and is a waste of time. Generate diagrams from code you already have in your repositories.
Instead of creating an excessive number of diagrams, focus on two or three ones that comprehensively describe the product from different levels of abstraction and are really necessary.
Always keep diagrams updated. This task is made more accessible if it doesn’t contain too many details – just prefer abstractions.
Educate the internal culture of the team to understand the need for architectural documents, including diagrams.
Never create architectural diagrams just “to be” to justify your role as an architect.
Try kroki.io - I like it.

Useful Links

Book “Documenting Software Architectures: Views and Beyond, Second Edition.”
My overview of IT Architect role.
Mermaid, PlantUML, UMLlet, Nomnoml, BlockDiag, WaveDrom, GraphViz, — tools I mentioned in this article to generate architectural diagrams from the text.
Kroki.io — API for interacting with BlockDiag (BlockDiag, SeqDiag, ActDiag, NwDiag, PacketDiag, RackDiag), BPMN, Bytefield, C4 (using PlantUML), Ditaa, Erd, GraphViz, Mermaid, Nomnoml, PlantUML, SvgBob, UMLet, Vega, Vega-Lite, WaveDrom…
How to use Kroki.io — user manual.
Installation guide for kroki.io.
Kroki CLI.
My GitHub repository with samples.

Thank you!

My Manner of Reading the Books. What Services Do I Use?

Dmytro Golodiuk — Sun, 03 May 2020 20:16:13 +0000

Article about my habits and preferences in books reading.

Paper vs “E-”

Today I am starting one of my favorite topics – “My Style.” Under the tag #my_style," I will share with you about my habits, software tools, and services I use, self-management, etc.

A few years ago, I set a goal to refuse paper books and to read e-books only. That experiment didn’t come off, and I decided to back to the paper books. Why is this?

⚠ No tactual sense.
⚠ No high-quality paper, perfect print, beautiful book cover – all are essential to me.
⚠ Lack of focus. In my case, I usually download a lot of books and magazines and drop them into the cloud (iCloud, OneDrive, etc.). It is so easy to shift a focus from an exciting and worthwhile book amid many others. Recently I have removed a few hundreds of unread books only because the newer version is released.
⚠ Not all books are equally convenient for reading on different devices.
⚠ I love to write on the margins by liners – making notes cannot replace this process.

For sure, there are a lot of advantages to e-books reading. So I can’t refuse from e-books, mainly owing to:

✅ E-books are published very often earlier.
✅ Book’s size and weight can make difficulties and inconvenience to take it with me. In that case, I usually practice a mixed approach to the reading combining a paper book with e-book (sometimes audiobook as well). Service Goodreads is of great help here.
✅ E-books allow searching.

My favorite Services

And for your attention, the list of services I use for reading the books.

🔴 GOODREADS (https://www.goodreads.com) – a list of my books I have read, I am reading now, and I am going to read. As well, it is a social network: you can make friendship with other users, follow the authors and readers, write a book review, share your reading list, and others. Killer feature 👉 – add your book just by scanning the book cover. Brilliant, isn’t it?

🔴 CALIBRE (https://calibre-ebook.com) – IMHO the best service for e-book management. It provides the mega-huge amount of features for different groups of users, from the beginner level to advanced. I use the following features:

👉 editing e-book metadata (manually, from the Internet, bulk edit)
👉 e-book conversion (a lot of formats)
👉 e-book viewer
👉 integration with devices (amazon kindle, phones, tablets, …)
👉 for more functions, watch the tour video (https://calibre-ebook.com/demo#tour) and tutorials (https://calibre-ebook.com/help).

🔴 AUDIBLE (https://www.audible.com/) – I use it for buying and listening to the audiobooks.

🔴 PLEX (https://www.plex.tv/) – I found it convenient to organize my library of audiobooks. Plex allows streaming your audiobooks from anywhere in the world.

🔴 PROLOGUE App (https://prologue-app.com/) – listen to your books from Plex.

🔴 Amazon KINDLE – it is about device and ecosystem for reading books.

🔴 Apple BOOKS – it is about reading books on iPhone and iPad.

P.S. Please take into consideration that I focused only on books reading, because news feeds, articles, notes, and other sources of reading – it’s a horse of another color.