The AWS Well-Architected Framework helps us to understand the pros and cons of decisions we make while building systems on AWS.
AWS has created the AWS Well-Architected Framework, which provides a consistent set of best practices for us to evaluate architecture and provides a set of questions we can use to evaluate how well an architecture is aligned to AWS best practices.

The AWS Well-Architected Framework is based on six pillars.

• Operational excellence: The ability to support development and run workloads effectively.

• Security: Describe how to take advantage of cloud technologies to protect data, systems, and assets in a way that can improve security posture.

• Reliability: The ability of a workload to perform its intended function correctly and consistently when it's expected to. This includes the ability to operate and test the workload through its total lifecycle.

• Performance efficiency: The ability to use computing resources to meet system requirements and to maintain that efficiency as demand and technology evolve.

• Cost optimization: The ability to run systems to deliver business value at the lowest price point.

• Sustainability: The ability to continually improve sustainability impact by reducing energy consumption and increasing efficiency across all components of a workload by maximizing the benefits from the provisioned resources and minimizing the total resources required.

General Design Principles The Well-Architecture Framework identifies a set of general design principles to facilitate a good design in the cloud:

• Stop guessing capacity needs: Poor capacity design when deploying a workload might end up on expensive idle resources or deal with the performance implications of limited capacity.

• Test systems at production scale: In the cloud, we can create a production-scale test environment on demand, complete our testing, and then decommission the resources.

• Automate with architectural experimentation in mind: Automation permits us to create and replicate our workload at low cost and avoid the expense of manual effort. We can track changes to our automation, audit the impact, and revert to previous parameters when necessary.

• Consider evolutionary architectures: In a traditional environment, architectural decisions are often implemented as static, onetime events, with a few major versions of a system during its lifetime. As a business and its context continue to evolve, these initial decisions might hinder the system's ability to deliver change by changing business requirements. In the cloud, the capability to automate and test on demand lowers the risk of impact design changes. This permits systems to evolve over time so that businesses can take advantage of innovations as a standard practice.

• Drive architecture using data: In the cloud, we can collect data on how your architectural choices affect the behavior of our workload. This lets us make fact-based decisions on how to improve our workload.

• Improve through game days: Test how our architecture and process perform by regularly scheduling game days to simulate events in production. This will help us understand where improvements can be made and can help develop organizational experience in dealing with events.

The Pillars of the framework

Creating a software system is a lot like constructing a building. If the foundation is not solid, structural problems can undermine the integrity and functions of the building.

Incorporating these pillars into our architecture will help us to produce stable and efficient systems.

Pillars:

• Operational excellence

• Security

• Reliability

• Performance efficiency

• Cost optimization

• Sustainability

Operational Excellence

This contains best practice for organizing team, designing workload, operating it at scale, and evolving it over time

Design principles

• Organizing teams around business outcomes

• Implement observability for actionable insight

• Safely automate where possible

• Make frequent, small, reversible changes

• Refine operations procedures frequently

• Anticipate failure

• Learn from all operational events and metrics

• Use managed services

  Learn more

Security

This pillar encompasses the ability to protect data, systems, and assets to take advantage of cloud technologies to improve our security.

Design principles

• Implement a strong identity foundation

• Maintain traceability

• Apply security at all layers

• Automate security best practice

• Protect data in transit and at rest

• Keep people away from data

• Prepare for security events

  Learn more

Reliability

This pillar encompasses the ability of a workload to perform its intended function correctly and consistently when it's expected to. This includes the ability to operate and test the workload through its total lifecycle.

Design principles

• Automatically recover from failure

• Test recovery procedures

• Scale horizontally to increase aggregate workload availability

• Stop guessing capacity

• Manage change through automation

  Learn more

Performance Efficiency

This pillar includes the ability to use cloud resources efficiently to meet performance requirements and to maintain the efficiency as demand changes and technology evolves.

Design principles

• Democratize advance technologies

• Go global in minutes

• Use serverless architecture

• Experiment more often

• Consider mechanical sympathy

  Learn more

Cost Optimization

This pillar includes the ability to run systems to deliver business value at the lowest price point.

Design principles

• Implement Cloud Financial Management

• Adopt a consumption model

• Measure overall efficiency

• Stop spending money on undifferentiated heavy lifting

• Analyze and attribute expenditure

  Learn more

Sustainability

This pillar focuses on environmental impacts, especially energy consumption and efficiency, since they are important levers for architects to inform direct action to reduce resource usage

Design principles

• Understand your impact

• Establish sustainability goals

• Maximize utilization

• Anticipate and adopt new, more efficient hardware and software offerings

• Use managed services

• Reduce the downstream impact of your cloud workloads

  Learn more

Conclusion

This framework provides architectural best practices across the six pillars for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems in the cloud.

Disclaimer, saya bukanlah seorang software developer. Saya mengikut acara ini karena tertarik, ingin menambah wawasan terkait software development, pengen mengerti sudut pandang seorang software developer, dan pengen mendengarkan speaker-speaker hebat yang ada di acara tersebut.

Berangkat

Acara dimulai pada pukul 10:00 WIB, dan registrasi dimulai pukul 8:00 WIB. Untuk menghindari antrean panjang saat registrasi, saya berangkat lebih awal. Dan saya tiba di lokasi pada pukul kurang lebih 8:15.

Boom, ternyata saya terlalu cepat. Memang sudah banyak yang datang dan saya tidak perlu mengantre untuk registrasi. Tapi ini masih terlalu jauh untuk dari waktu acara dimulai, jadi saya punya cukup waktu untuk bengong yang lama 😂.

Saya agak bingung, karena saya sendirian. Jadi saya gunakan waktu untuk membuka laptop, membaca buku, sambil sesekali berjalan melihat-lihat lokasi kalau punggung sudah terasa capek.

Dan akhirnya acaranya dimulai.

Acara Mulai

Ada 2 event agenda. Main Forum dan Community Forum.

Saya tidak akan menceritakan semua yang saya dengar disini. Tapi saya akan menceritakan hal yang menarik bagi saya saja.

Bikin AI Sendiri: from zero to hero

Topik ini diisi oleh Pak Onno W. Purbo. Ya, Pak Onno. Semua orang IT pasti tahu tentang beliau.

Mirip seperti materi-materi di youtube, beliau menjelaskan mengenai AI, beliau juga berbagi mengenai buku-buku terkait AI untuk SMP, SMA & SMK.

Kurang lebih penjelasanya hanya terkait apa yang sudah beliau praktekan untuk mengajar mengenai AI. Tidak banyak hal yang bisa saya share mengenai topik ini.

Vibe Coding

Topik ini diisi oleh Rizqinofa Putra Muliawan.

Topik ini yang paling menarik perhatian saya. Selama penjelasan saya menulis poin-poin yang menurut saya penting dan bisa saya pelajari.

Topik ini memberikan sudut pandang baru mengenai cara coding menggunakan AI. Beberapa kali saya membuat program ataupun sekedar scripting dengan bantuan AI tapi tidak pernah memanfaatkan AI secara maksimal, saya hanya bertanya ke LLM. Misal: buat function untuk fitur A. Kemudian saya hanya copas, dan menyesuaikan beberapa hal yang kurang pas. Tapi Vibe Coding benar-benar memanfaatkan AI secara maksimal. Mulai dari planing sampai dengan coding-nya.

Acara Selesai

Selain 2 topik diatas, saya juga mengikut beberapa topik lain, tapi tidak saya tulis karena tidak begitu menarik buat saya.

Acaranya sampai sore, tapi saya tidak mengikutinya sampai selesai walaupun ada doorprize di akhir acara. Saya putuskan untuk pulang lebih awal.

Apa yang saya dapatkan?

Merchandise.

Tentu saja bukan cuma itu, saya mendapatkan banyak wawasan terutama terkait AI. Serta mengingatkan saya kembali betapa cepatnya perkembangan dunia IT. Ini menjadi bahan bakar saya untuk terus belajar jika ingin survive di bidang ini.

Assume we have a service/app repository. We want to automate the versioning and CHANGELOG generation. How to achieve this? In this article, I will explain how to automate versioning and CHANGELOG generation using commit-and-tag-version.

Prerequisites

• commit-and-tag-version

• Git Repository

How to

Installing commit-and-tag-version

npm i -g commit-and-tag-version

Preparing Configuration files

assume you already have git repository

1. Create configuration file .versionrc

2. Create version.json file.

3. Run first release

4. Test create commit

5. Run release

example file .versionrc and version.json

// .versionrc
{
  "packageFiles": [
    {
      "filename": "version.json",
      "type": "json"
    }
  ],
  "bumpFiles": [
    {
      "filename": "version.json",
      "type": "json"
    }
  ]
}

// version.json
{
    "version": "1.0.0"
}

Run First Release

commit-and-tag-version --first-release

Test Create Commit

You can add a new file and then commit or create an empty commit. To create empty commit, you can follow this example command

git commit --allow-empty -m "feat: add feature A"

Run Release

commit-and-tag-version

After you run first release, you can see CHANGELOG.md file is created and version.json file is update.

If you want to read more about commit-and-tag-version, you can check the github repository.