<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eky Pradhana on Medium]]></title>
        <description><![CDATA[Stories by Eky Pradhana on Medium]]></description>
        <link>https://medium.com/@ekypradhana?source=rss-d8bdc6760704------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6DjBPCc67WzBPHj8ml328g.jpeg</url>
            <title>Stories by Eky Pradhana on Medium</title>
            <link>https://medium.com/@ekypradhana?source=rss-d8bdc6760704------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:26:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ekypradhana/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building your own chat app without backend? Here we go!]]></title>
            <link>https://ekypradhana.medium.com/building-your-own-chat-app-without-backend-here-we-go-75954af2d734?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/75954af2d734</guid>
            <category><![CDATA[firestore]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Wed, 17 May 2023 00:52:04 GMT</pubDate>
            <atom:updated>2023-05-17T09:31:10.338Z</atom:updated>
            <content:encoded><![CDATA[<p>tl;dr : using ReactJS and Firebase, it’s enough! oh wait.. and a cup of Mixue I guess.</p><p>Still bringing the spirit of sharing small things, give something back to society. Because I used to be there when I knew nothing about something I wanted to know, about where to start, where to go, I hope this post will help someone out there about how to build a chat app. This time I’ll show you how to do it without any backend codes at all. We will use the power of <a href="https://react.dev/">ReactJS</a> combined with <a href="https://firebase.google.com/">Firebase</a>.</p><h4>First thing first, begin with the end in mind!</h4><p>You can find the demo of this app here : <a href="https://master--candid-muffin-cdbe2c.netlify.app/">https://master--candid-muffin-cdbe2c.netlify.app/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74o0mRxBJ974GAFYBf8pqQ.gif" /><figcaption>INDONESIAAA!!!</figcaption></figure><h3>Feeling challenged? Let’s roll!</h3><p>I will make it covered, so here are the things we will do in this post:</p><ol><li>Initialize the project</li><li>Install dependencies (firebase, universal cookie, material-ui)</li><li>Setup firebase</li><li>Create auth component</li><li>Setup firestore</li><li>Create room and chat component</li></ol><p>p.s : I assume you have installed npm and create-react-app in your local, if you don’t have it, <a href="https://www.freecodecamp.org/news/install-react-with-create-react-app/">follow this link</a>.</p><p>Ready? Let’s get started..</p><h3>Initialize the project</h3><p>Go to your designated folder, then initialize react project using command below :</p><pre>create-react-app chat-app</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvrKIcsFSf_H53gZSr21HA.gif" /><figcaption>it will take couple of minutes</figcaption></figure><p>Your installation is succeed once you find this kind of screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Odo6KVhP2gQaCUmVGRdR9A.png" /><figcaption>react project installation succeed</figcaption></figure><p>Now let’s jump into chat-app folder, and you will find some files created already</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9B4KilKW3PwnRm17LPmlEw.png" /></figure><p><strong>Okay we’re good now. Let’s go to next step!</strong></p><h3>Install Dependencies</h3><p>This time, we need 3 dependencies / libraries to be installed for this project:</p><ol><li>Firebase : to manage connection to firebase service</li><li>Universal cookie : simple library to maintain cookie in our app</li><li>Material UI : common UI library for react project</li></ol><p>Type command below to install those libraries :</p><pre>npm install firebase universal-cookie @mui/material @emotion/react @emotion/styled</pre><p>It will also takes several minutes (depending your internet connection). Now let’s make sure our react project is initiated with this command :</p><pre>npm run start</pre><p>It will automatically open the browser and access the app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CDWm10qzac3vDDGeyKahGg.png" /></figure><h3>Setup Firebase</h3><p>To setup Firebase, go to this link : <a href="https://console.firebase.google.com/">https://console.firebase.google.com/</a>, then follow this step :</p><ol><li>Click : Create a Project</li><li>Fill the project name, let’s use “chat-app” for now</li><li>Check all required term and conditions</li><li>Click : Continue</li><li>On the next screen, uncheck “Enable Google Analytics for this project” (we don’t need it for now)</li><li>Click : Create Project</li></ol><p><strong>Or you can simply follow this short vid :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nrUBJWuALgtzR0k_dHjMBw.gif" /><figcaption>Setup Firebase</figcaption></figure><p>There are many services in Firebase. To make this project more attractive, we will add google authentication so we will know who’s join in the chat room. For that, we will use Authentication service from Firebase. And later in this post, we will also take benefit of Firestore (Firebase database service) to save the chat data.</p><p>Now let’s go back to our code editor to create authentication page.</p><h3>Create Auth Component</h3><h4>1. Setup App on Firebase to get Firebase Config</h4><p>Simply follow this short vid to get firebase config</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HnovJ8D4UFPJ-SwEl1YyHA.gif" /><figcaption>get firebase config</figcaption></figure><h4>2. Create file firebase-config.js under folder ./src</h4><p>The code will be like below, you must change the value of firebaseConfig following your own</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/607fcdd3f484b5496a4290ca9d211932/href">https://medium.com/media/607fcdd3f484b5496a4290ca9d211932/href</a></iframe><h4>3. Create folder “components” under ./src, and create file “Auth.js”</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/64df3bf1eee136afd80a781ff90eec71/href">https://medium.com/media/64df3bf1eee136afd80a781ff90eec71/href</a></iframe><h4>4. Then, edit your App.js under ./src</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/425e9f515f949770ffa8dc5b67f0fe0c/href">https://medium.com/media/425e9f515f949770ffa8dc5b67f0fe0c/href</a></iframe><p>Should be fine now, start your app again using : npm run start</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O1XwO4b5CHeAbMYLPpnDZg.gif" /></figure><p>Okay, we have created our google auth page using Firebase. Next, let’s handle the room component.</p><h3>Create Chat and Room Component</h3><p>First, we have to setup Firestore as a data storage for our apps. Again, simply follow this short clip to go :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvSFpN_Vqy4AnUmG3I6Kuw.gif" /><figcaption>activate Firestore database</figcaption></figure><p>Next, back to your code editor and follow these steps.</p><h4>1. Create Room.js under folder components</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ec6e4aafe2aefb146deda96336021e7/href">https://medium.com/media/2ec6e4aafe2aefb146deda96336021e7/href</a></iframe><h4>2. Create Chat.js under folder components</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f9e75914000d4c28d895c71d85b86c8/href">https://medium.com/media/5f9e75914000d4c28d895c71d85b86c8/href</a></iframe><h4>3. Add little bit css to give styling on chat box, put it under ./src/styles/Chat.css</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/22836c3769ac69a1ac5696c854d0ee2c/href">https://medium.com/media/22836c3769ac69a1ac5696c854d0ee2c/href</a></iframe><h4>4. Finally, modify your App.js to attach the room component</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/913d89e6d0c5e4696e6a4d73c68d17ee/href">https://medium.com/media/913d89e6d0c5e4696e6a4d73c68d17ee/href</a></iframe><h3>And it’s done!</h3><p>Run your npm run start again to view the result.</p><p>Sure there should be many optimizations need to be added here and there (e.g: in-app validation control, using websocket, etc), but since it is only simple chat-app, I think that should be enough.</p><p>I don’t include the code repository URL with purpose, so you can try it yourself from start and understand it.</p><p>Have a good day and keep sharing small things! Let’s make the world a better place together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75954af2d734" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying Scrum: An Agile Framework for Collaborative Project Management]]></title>
            <link>https://ekypradhana.medium.com/demystifying-scrum-an-agile-framework-for-collaborative-project-management-e053a06d89ed?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/e053a06d89ed</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Sat, 13 May 2023 02:24:10 GMT</pubDate>
            <atom:updated>2023-05-13T02:41:54.789Z</atom:updated>
            <content:encoded><![CDATA[<p>Wohohoho finally I can make a cool title!</p><p>This post is related to my previous post <a href="https://medium.com/@ekypradhana/about-lean-agile-scrum-kanban-waterfall-40b660e9e41e">About Lean, Agile, Scrum, Kanban, Waterfall here</a>. Please read that to get insights about Lean and Agile.</p><p>Now I will continue talking about Scrum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8Ct0aLazMAgWKIa2.jpg" /><figcaption>credit : <a href="https://scrum.org/">Scrum.org</a></figcaption></figure><p>In today’s fast-paced and ever-changing business landscape, organizations are seeking efficient and adaptable project management methodologies. Agile frameworks have emerged as a popular solution, enabling teams to navigate complex projects while embracing collaboration and iterative development. One such framework is Scrum, a powerful approach that emphasizes flexibility, transparency, and delivering incremental value. In this article, we will delve into the world of Scrum, unravel its principles, explore its benefits, showcase its application through a real-world case study, and examine the core Scrum ceremonies and roles.</p><h3>Embracing Agile Project Management with Scrum</h3><p>Agile project management has revolutionized the way organizations tackle projects, providing an alternative to traditional waterfall methodologies. Scrum, an agile framework rooted in collaboration, has gained widespread adoption due to its ability to adapt to evolving requirements, foster cross-functional teamwork, and deliver tangible results in shorter timeframes. By breaking down complex projects into manageable sprints, Scrum allows teams to prioritize tasks, respond to feedback, and course-correct as needed. This iterative approach empowers teams to embrace change, reduce risk, and deliver high-quality products that align with customer needs. Now, let’s dive deeper into the inner workings of Scrum and explore how it can transform project management practices.</p><h3>The Scrum Framework: Fostering Collaboration and Delivering Value</h3><p>At the core of Scrum lies a robust framework that empowers teams to collaborate effectively, adapt to changing requirements, and deliver incremental value. The Scrum framework consists of three key roles: the Product Owner, the Scrum Master, and the Development Team. Let’s delve into the responsibilities of each role and understand how they contribute to the success of Scrum projects:</p><ul><li><strong>The Product Owner</strong> plays a crucial role in representing the stakeholders and ensuring that their needs are understood and translated into actionable items. With a deep understanding of the product vision, market demands, and customer expectations, the Product Owner is responsible for managing the product backlog, prioritizing features, and defining the project’s direction.</li><li><strong>The Scrum Master</strong> acts as a facilitator and coach, guiding the team in embracing Scrum principles and practices. They foster a collaborative work environment, remove any obstacles that hinder progress, and empower the team to self-organize and make effective decisions. The Scrum Master plays a vital role in ensuring that the Scrum process is followed, enabling the team to maximize its potential.</li><li><strong>The Development Team</strong> consists of professionals with diverse skills who are responsible for turning the product backlog into working increments. They collaborate closely, using their collective expertise to deliver high-quality, potentially shippable increments at the end of each sprint. With a focus on self-management, accountability, and continuous improvement, the Development Team embodies the spirit of cross-functional collaboration and shared ownership.</li></ul><p>These three roles form the foundation of a successful Scrum team, where collaboration, communication, and shared responsibility are paramount. By embracing their respective responsibilities and working together seamlessly, the Scrum Team is equipped to navigate complex projects, adapt to evolving requirements, and deliver incremental value to stakeholders.</p><p>Now let’s talk about some ceremonies in Scrum framework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LITipJh3ZOmG8EpJ.png" /><figcaption>credit : <a href="https://www.parabol.co/blog/scrum-ceremonies-for-remote-teams/">parabol.co</a></figcaption></figure><h3>Scrum Ceremonies: Driving Collaboration and Adaptability</h3><p>To facilitate effective communication and collaboration within the Scrum framework, a set of ceremonies or meetings are held at key stages of the project. These ceremonies play a vital role in promoting transparency, aligning team members, and enabling adaptability. Let’s explore the core Scrum ceremonies that drive the iterative and collaborative nature of the framework:</p><ul><li><strong>Sprint Planning:</strong> Sprint Planning is a collaborative meeting held at the beginning of each sprint. During this ceremony, the Product Owner and Development Team collaborate to define the sprint goal and determine which product backlog items will be included in the upcoming sprint. By collectively deciding on the work to be done and estimating the effort required, the team establishes a shared understanding of the sprint’s objectives and sets the stage for successful execution.</li><li><strong>Daily Scrum:</strong> The Daily Scrum, also known as the daily stand-up, is a short and focused meeting that brings the Scrum Team together. It provides an opportunity for team members to synchronize their activities, discuss progress, and identify any impediments. By sharing updates and aligning their efforts, the team can maintain a clear understanding of the project’s direction and address any challenges that may arise.</li><li><strong>Sprint Review:</strong> The Sprint Review is a pivotal ceremony that takes place at the end of each sprint. It provides an opportunity for the Scrum Team to showcase the increment they have developed and gather valuable feedback from stakeholders and end-users. By demonstrating the product’s functionality and gathering insights, the team can validate their progress, make necessary adjustments, and ensure that the product aligns with customer expectations.</li><li><strong>Sprint Retrospective: </strong>The Sprint Retrospective (or just Sprint Retro) is a reflective ceremony that occurs after the Sprint Review. In this meeting, the Scrum Team reflects on the sprint’s successes, challenges, and areas for improvement. Through open and honest discussions, the team identifies process enhancements, team dynamics, and tools or practices that can be adjusted in the next sprint. The retrospective promotes a culture of continuous learning and improvement, enabling the team to refine their processes and increase productivity over time.</li><li><strong>Backlog Refinement:</strong> Backlog refinement is an essential practice in Scrum that involves continuously reviewing, prioritizing, and clarifying items in the product backlog. It is a collaborative activity that ensures the product backlog remains relevant, well-defined, and ready for the upcoming sprints. During backlog refinement, the Scrum team, including the Product Owner and Development Team, comes together to discuss and refine user stories, epics, and other items in the backlog. This process helps in gaining a shared understanding of the requirements, breaking down larger items into smaller, actionable user stories, and estimating the effort needed for each item. By regularly refining the backlog, the team ensures that the highest-priority items are well-defined and ready for inclusion in future sprints, enabling a smoother sprint planning process and maximizing the team’s productivity. Backlog refinement also allows for the identification of new items, reprioritization based on changing needs, and alignment with the overall product vision. It is a collaborative and iterative process that ensures the backlog remains a valuable and dynamic tool for the team throughout the project lifecycle.</li></ul><p>These Scrum ceremonies form the backbone of effective collaboration, communication, and adaptation within the framework. By embracing these meetings and utilizing them to their full potential, teams can maximize the benefits of Scrum and enhance their project outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/0*P0BjSEsEBbxb6ZTQ.jpg" /><figcaption>credit: <a href="https://wisdomplexus.com/">wisdomplexus.com</a></figcaption></figure><h3>The Balancing Act: Exploring the Pros and Cons of Scrum in Project Management</h3><p>In project management, Scrum has gained popularity as an agile framework with its iterative approach and collaborative principles. While offering numerous benefits, it also presents certain challenges. This part explores the pros and cons of using Scrum, providing insights to help project managers and organizations determine its suitability for their projects.</p><h4>Pros of Using Scrum:</h4><ol><li>Flexibility and Adaptability: Scrum embraces change and allows for flexibility in project requirements. With its iterative approach, teams can continuously refine and reprioritize their backlog based on evolving customer needs and market dynamics.</li><li>Transparency and Collaboration: Scrum promotes transparency through its ceremonies and artifacts, ensuring all team members have visibility into the project’s progress. It encourages collaboration and frequent communication, fostering a shared understanding and collective ownership among team members.</li><li>Faster Time-to-Market: Scrum’s time-boxed sprints enable teams to deliver working increments of a product at the end of each iteration. This iterative development approach leads to faster time-to-market, allowing organizations to gather early feedback and make timely adjustments.</li><li>Focus on Customer Value: Scrum prioritizes delivering value to the customer by focusing on building the most important features first. The Product Owner plays a critical role in ensuring that customer needs are understood and incorporated into the product backlog.</li></ol><h4>Cons of Using Scrum:</h4><ol><li>Complexity and Learning Curve: Scrum introduces new roles, ceremonies, and artifacts, which can initially be overwhelming for teams unfamiliar with the framework. The learning curve associated with implementing Scrum may require additional time and effort.</li><li>Dependencies and Integration Challenges: Scrum’s focus on individual team autonomy can sometimes lead to challenges in managing dependencies with other teams or systems. Ensuring smooth integration and coordination across multiple teams or projects may require careful planning and communication.</li><li>Emphasis on Planning and Documentation: Scrum places importance on planning and documentation, which can be perceived as time-consuming by some teams. Balancing the need for planning and documentation with the actual development work can be a challenge for some organizations.</li><li>Need for Dedicated Scrum Master and Product Owner: Scrum requires dedicated roles for the Scrum Master and Product Owner, which may require additional resources or adjustments in the team structure. Finding individuals who can effectively fulfill these roles and have the necessary skills and knowledge can be a challenge.</li></ol><h3>Case Study: Implementation of Scrum at XYZ Company</h3><p>To gain a deeper understanding of Scrum’s practical application, let’s explore a real-world case study showcasing its successful implementation. XYZ Company, a leading software development firm, faced the challenge of developing a cutting-edge mobile application within a tight deadline. The project required collaboration among cross-functional teams, frequent customer feedback, and the ability to adapt to changing requirements. To address these challenges, XYZ Company adopted Scrum as their project management framework.</p><p>The implementation of Scrum began with the formation of a dedicated Scrum team consisting of a Product Owner, a Scrum Master, and a skilled Development Team. The Product Owner worked closely with stakeholders to define and prioritize the product backlog, ensuring that the team had a clear understanding of customer needs and expectations. The Scrum Master facilitated the team’s adoption of Scrum principles, removing impediments, and fostering a collaborative work environment.</p><p>Throughout the project, Scrum ceremonies played a crucial role in driving progress and enabling adaptation. Daily Scrums allowed team members to synchronize their efforts, share updates, and identify any roadblocks. Sprint Planning meetings facilitated collaboration between the Product Owner and the Development Team to define the sprint goal and select the tasks to be completed. Regular Sprint Reviews provided an opportunity to gather valuable feedback from stakeholders and end-users, enabling the team to make necessary adjustments and ensure that the product aligned with customer expectations. Sprint Retrospectives allowed the team to reflect on their processes, identify areas for improvement, and continuously enhance their performance.</p><p>The implementation of Scrum at XYZ Company yielded remarkable results. By embracing an iterative development approach, the team achieved a faster time-to-market while maintaining high product quality. Collaboration among team members significantly improved, with enhanced communication, knowledge sharing, and collective problem-solving. The customer feedback loop became an integral part of the development process, ensuring that the final product met customer expectations.</p><p>The successful implementation of Scrum transformed XYZ Company’s project management practices. It enabled the team to navigate complexities, adapt to changing requirements, and deliver a high-quality mobile application within the tight deadline. The experience showcased the power of Scrum in fostering collaboration, promoting transparency, and driving customer-focused development.</p><p>By providing a detailed case study, we can illustrate how Scrum can be effectively applied in real-world scenarios, emphasizing its impact on project outcomes, team dynamics, and customer satisfaction.</p><h3>Tools for Streamlining Scrum Processes</h3><p>To streamline and enhance the Scrum process, teams often leverage a variety of tools and software solutions. These tools provide valuable support for managing backlogs, tracking progress, and facilitating effective collaboration. Here are a few commonly used tools in the Scrum ecosystem:</p><ul><li><a href="https://jira.atlassian.com/">Jira Software</a>: Jira Software is a widely adopted project management tool that offers robust features for backlog management, sprint planning, and issue tracking. It provides a centralized platform for Scrum teams to visualize and manage their work, enabling efficient collaboration and progress tracking.</li><li><a href="https://trello.com/">Trello</a>: Trello is a popular and user-friendly task management tool that employs Kanban boards to visualize workflows. It allows teams to create and organize tasks, track progress through different stages, and collaborate effectively. Trello’s intuitive interface makes it easy to adopt for teams new to Scrum.</li><li><a href="https://asana.com/">Asana</a>: Asana is a popular project management and collaboration tool that helps teams streamline their workflows and increase productivity. With features like task management, project organization, collaboration capabilities, and integrations with other tools, Asana provides a centralized hub for teams to track, manage, and communicate about their work. Its user-friendly interface and versatile functionality make it a valuable tool for individuals and teams seeking to improve project visibility, enhance communication, and stay organized.</li><li><a href="https://azure.microsoft.com/en-us/products/devops">Azure DevOps</a>: Azure DevOps, formerly known as Visual Studio Team Services (VSTS), is a comprehensive suite of tools designed to support the entire Scrum lifecycle. It offers features for backlog management, version control, continuous integration, and more. With Azure DevOps, teams can streamline their development process and ensure seamless collaboration.</li><li><a href="https://slack.com/">Slack</a>: Slack is a team communication and collaboration platform that provides real-time messaging, file sharing, and integrations with other productivity tools. Teams can create dedicated channels for Scrum ceremonies, share updates, and facilitate quick and efficient communication within the Scrum team.</li><li><a href="https://confluence.atlassian.com/">Confluence</a>: Confluence is a collaboration and documentation platform that allows teams to create, share, and organize project-related documentation. It serves as a centralized knowledge base where teams can store meeting notes, project plans, and other important resources, promoting transparency and knowledge sharing.</li></ul><p>These tools are just a few examples of the many options available to enhance Scrum processes. The choice of tools depends on team preferences, project requirements, and organizational needs. By leveraging these tools effectively, teams can streamline their Scrum practices, improve collaboration, and maximize productivity.</p><p>Integrating these tools into the Scrum workflow can further optimize the project management process, enabling teams to work more efficiently and effectively. However, it’s important to remember that tools are enablers, and their successful implementation relies on understanding and embracing the underlying principles and values of Scrum.</p><p>In the end, selecting the right tools and utilizing them in conjunction with Scrum’s collaborative framework can greatly contribute to the success of projects and the achievement of organizational goals.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxT1XGOGdyDrL2BTfxK%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZDEwZTFlZjU3ZDhlYTc4MWY0OWE1ZDc3ZDIxOTQ3NmVkZmVhMGFkMCZlcD12MV9pbnRlcm5hbF9naWZzX2dpZklkJmN0PWc%2FxT1XGOGdyDrL2BTfxK%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FxT1XGOGdyDrL2BTfxK%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ef9db75c309464df25185ba9ce8fff2/href">https://medium.com/media/2ef9db75c309464df25185ba9ce8fff2/href</a></iframe><h3>Conclusion</h3><p>Scrum’s collaborative and adaptive nature makes it a powerful framework for project management. By fostering collaboration, adaptability, and transparency, Scrum enables teams to deliver incremental value, embrace changing requirements, and enhance customer satisfaction. Embracing Scrum empowers organizations to navigate complexities, drive innovation, and achieve project success in today’s dynamic business landscape.</p><h3>Furthermore</h3><p>Wanna learn more about Scrum? Here are some dictionaries and glossaries related to Scrum:</p><ol><li><strong>Scrum Glossary (Scrum.org):</strong> A comprehensive glossary of terms related to Scrum, provided by Scrum.org, a leading authority on Scrum. It covers essential concepts, roles, events, artifacts, and practices used in Scrum. Access it at: <a href="https://www.scrum.org/resources/scrum-glossary">https://www.scrum.org/resources/scrum-glossary</a></li><li><strong>Agile Alliance Glossary:</strong> The Agile Alliance provides a glossary that covers a wide range of agile terms, including those specific to Scrum. It offers definitions and explanations of various agile concepts and practices. Explore it at: <a href="https://www.agilealliance.org/agile101/glossary/">https://www.agilealliance.org/agile101/glossary/</a></li><li><strong>Scrum Reference Card (Scrum Alliance):</strong> The Scrum Reference Card by the Scrum Alliance is a handy resource that provides an overview of key Scrum elements, including roles, events, artifacts, and basic principles. It serves as a quick reference guide for Scrum practitioners. Download it at: <a href="https://www.scrumalliance.org/get-certified/scrum-reference-card">https://www.scrumalliance.org/get-certified/scrum-reference-card</a></li><li><strong>Agile Dictionary (Agile Alliance):</strong> The Agile Dictionary by the Agile Alliance is a comprehensive resource that covers terms and definitions related to agile practices, methodologies, and principles. It includes Scrum-related terms and provides insights into various agile concepts. Visit it at: <a href="https://www.agilealliance.org/glossary/">https://www.agilealliance.org/glossary/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e053a06d89ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Add IAM User and IAM Role to AWS EKS Cluster]]></title>
            <link>https://ekypradhana.medium.com/how-to-add-iam-user-and-iam-role-to-aws-eks-cluster-749571a67bc9?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/749571a67bc9</guid>
            <category><![CDATA[aws-iam-role]]></category>
            <category><![CDATA[aws-iam]]></category>
            <category><![CDATA[aws-eks]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Mon, 16 May 2022 05:44:20 GMT</pubDate>
            <atom:updated>2022-05-16T05:48:01.650Z</atom:updated>
            <content:encoded><![CDATA[<p>Well this actually should be written in my technical private notes, but just in case someone needs it, hopefully it can help.</p><p>I followed this youtube video from Anton Putra below, and it works pretty well</p><p><a href="http://www.youtube.com/watch?v=EGdN21F2Jfw">www.youtube.com/watch?v=EGdN21F2Jfw</a></p><p>He also wrote a blog post regarding this video so we can easily copy and paste the code here : <a href="https://antonputra.com/kubernetes/add-iam-user-and-iam-role-to-eks/">https://antonputra.com/kubernetes/add-iam-user-and-iam-role-to-eks/</a></p><p>Of course I found some challenges when following his video, but fortunately it can be solved. So if you find any difficulties, on behalf of Anton, I will be very happy to discuss.</p><p>Thank you, Anton! The world can be a very beautiful place because of people like you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=749571a67bc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Objective and Key-Result]]></title>
            <link>https://ekypradhana.medium.com/objective-and-key-result-f8a8695baa88?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8a8695baa88</guid>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Mon, 04 Apr 2022 17:55:14 GMT</pubDate>
            <atom:updated>2022-04-04T17:55:29.761Z</atom:updated>
            <content:encoded><![CDATA[<p>I believe the fastest way to learn something is to document it. <a href="https://rumaysho.com/13457-beliau-pun-menyimak-dan-mencatat-ikatlah-ilmu-dengan-menulis.html">Tie up the knowledge by writing it down</a>. So let’s start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CJdIzo3FtBCG-0NxiWOONA.png" /><figcaption>credit : <a href="https://id.hrnote.asia/">https://id.hrnote.asia/</a></figcaption></figure><h3>Why OKR ?</h3><p>First principle, <a href="https://www.youtube.com/watch?v=u4ZoJKF_VuA&amp;vl=en">start with why</a>. Since the OKR stands for Objective and Key-Result, which Objective is the “what” or the “where”, and Key-Result is the “how”, so we can assume that we need OKR as a guidance or framework to get something we want, to achieve our goals. And since many big companies out there have proven that they have been succeed in adopting this goal setting methodology, so why don’t we try. Is it only FOMO thing? well, you decide.</p><h3>What is OKR ?</h3><p>Again, OKR stands for Objective and Key-Result. It’s just an ordinary goal-setting framework or methodology. Objective describes what we want to do, where we want to go. It sets our mission and set the deadline to achieve it. It contains the highest priority our team needs to accomplish in certain period of time (usually 30 to 90 days). The Key-Result on the other hand is the how we do that. It shows progress toward our objective. It helps us to know whether we are on the right path or not. In short, Key-Result provides the benchmark to measure or track our progress towards our objective. That’s it!</p><h3><strong>OKR vs KPI ?</strong></h3><p>Should not compare those two, from what I got those may complement each other. But still, what are the differences?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*puYcS8FQ8Dcjs1xbcurxsw.png" /></figure><p>Then how to make a good OKR? How to implement it well? I don’t know haha.. at least till this moment. Stay tune, I’ll try to keep documenting it from now.</p><p>Marhaban yaa Ramadhan!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8a8695baa88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The KanoFresh : Freedom of Speech]]></title>
            <link>https://ekypradhana.medium.com/the-kanofresh-freedom-of-speech-3cf32eed7ede?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/3cf32eed7ede</guid>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Sat, 26 Mar 2022 10:04:41 GMT</pubDate>
            <atom:updated>2022-03-28T03:55:44.294Z</atom:updated>
            <content:encoded><![CDATA[<h3>The KanoFresh : Freedom of Speech</h3><p>Sejak beberapa pekan yang lalu di perusahaan tempat saya bekerja (<a href="https://kanosolution.com/">Kano Solution</a>), ada inisiatif dari teman-teman untuk mengadakan satu sesi khusus dimana kami berkumpul secara online dan berbicara apapun, literally apapun, dengan tujuan sebagai waktu jeda setelah 1 pekan bekerja (refresh), mengenal sisi lain dari rekan kerja kita, bonus mengasah skill berbicara di depan umum dengan terstruktur dan efektif, serta menambah sesuatu yang baru untuk pribadi masing-masing. Tentunya dengan beberapa value yang tetap kami jaga, tidak terkesan menggurui, bukan ajang untuk show-off, no place for judgement, serta growth mindset : belajar untuk berbagi, berbagi untuk belajar.</p><p>Kesadaran akan adanya ‘sesuatu’ yang hilang sejak full WFH diberlakukan mungkin juga berperan terbentuknya sesi ini. Kami mulai dari kelompok kecil dulu pada awalnya. Bersyukur antusias dari teman-teman di kantor ternyata diatas ekspektasi, terukur dari jumlah peserta dari pekan ke pekan yang stabil dan cenderung meningkat, serta pertanyaan dan response dari peserta yang kadang lucu-lucu, membuat suasana jadi lebih bermakna. Bahkan ada yang secara blak-blakan juga menceritakan sisi lain kehidupannya yang membuat saya pribadi merasa wow, this man is in different level! Kesadaran untuk menganggap bahwa rekan kerja itu bukan hanya orang-orang yang membantu kita menyelesaikan pekerjaan di kantor, tapi mereka pun juga seutuhnya manusia sama seperti kita yang memiliki hidup, tantangan, dan perjuangan masing-masing, adalah salah satu hal positif yang saya dapatkan dari sesi-sesi ini.</p><p>Dalam satu renungan pribadi, saya semakin tersadar bahwa sebenarnya masing-masing dari kita ini adalah pahlawan, setidaknya untuk keluarga kita masing-masing. Hal itu membuat segala judgement yang terkadang muncul terhadap hasil pekerjaan pun perlahan terkikis, menjadi sebuah pemahaman akan kondisi dan usaha untuk menemukan solusi. Jika kita merasa bahwa kita terlalu berat dalam berlari, orang-orang di sekitar kita pun sebenarnya juga sedang berlari, lalu mengapa kita tidak coba saja berlari bersama?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*yDZN5031cxypoEuCLzBoKQ.jpeg" /><figcaption>run baby ruuunnn!</figcaption></figure><p>Ada yang bilang ‘collaboration is the new competition’. Susah memang pada awalnya saya memahami quote ini. Memaknai bahwa ‘kompetisi terbesar dalam hidup sebenarnya adalah mengalahkan diri sendiri’ pun juga menjadi sesuatu yang absurd dan non-sense bagi saya pada awalnya. Bersyukur dari sesi-sesi ini, celah antara ‘hah?’ dan ‘ooh’ dalam memaknai dua kalimat di atas perlahan mendekat. Terlalu sempit jika kita memaknai berlari untuk berkompetisi dengan orang lain, toh goals besar kita pun pada akhirnya masing-masing, hanya saja kebetulan (atau tidak?) jalan yang kita lalui sekarang ini adalah jalan yang sama. Kita berlari untuk saling menguatkan, mengingatkan, menyemangati. Terkadang mungkin kita juga perlu beristirahat bersama di bawah pohon menikmati awan atau hujan. Pun juga kadang kita perlu menggendong (bahkan menyeret paksa) teman berlari kita sebagai bentuk support kepada mereka agar tetap ‘menggigit’ kuat impian-impiannya.</p><p>Tidak perlu malu juga untuk meminta gendong kepada mereka saat kaki kita terkilir. Ngga usah sok kuat bestieeee, dalam berbagai hal banyak kelemahan yang harus kita akui :D</p><p>— — —</p><p><em>“Lewat endi iki bosku?”</em></p><p><em>“Koyok’e lurus luwih enak, soale aku pernah lewat dan dalanne luwih penak, akeh wit2an pisan dadi luwih sejuk, sak wayah2 kesel iso leren diluk”</em></p><p><em>“ooow siyaapp.. es teh sek a bos?”</em></p><p><em>“koen onok duit a?”</em></p><p><em>“yo iki onok tapi mung cukup gawe sakgelas, paroan ae yo”</em></p><p><em>“iyowes, ngelingi dusomu akeh koen butuh akeh sodakoh ancene”</em></p><p><em>“lambemu.. ngomong ae lek ancene ngelak”</em></p><p>— — —</p><p>Semoga dan semoga kolaborasi semacam ini akan semakin kuat terbentuk, tidak ada lagi keinginan untuk menjatuhkan, terganti dengan sebuah pencapaian mengalahkan diri yang kemarin bahkan mungkin hanya untuk sekedar memakai dan mengikat tali sepatu lari pun selalu kalah dengan penundaan.</p><p><em>Credit image : istockphoto.com</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3cf32eed7ede" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About Lean, Agile, Scrum, Kanban, Waterfall]]></title>
            <link>https://ekypradhana.medium.com/about-lean-agile-scrum-kanban-waterfall-40b660e9e41e?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/40b660e9e41e</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Tue, 05 Oct 2021 18:29:49 GMT</pubDate>
            <atom:updated>2021-10-05T18:35:13.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Wow, what a title!</p><p>In product development world bla bla bla bla there he is.. shut up! just to the point please.</p><p>With a good title comes great opening sentence. Whatever, let’s start!</p><h3>Lean (in Product Development)</h3><p>Lean is a philosophy in product development that revolve around cutting off the unnecessary works or efforts until we’re absolutely sure we need to do it for our users or customers.</p><p>One good example lately I’ve found is when my friend’s trying to build a new business. He tried to bridge the sellers in local (traditional) market with the customer, because he saw that during pandemic, many people don’t go to the traditional market so the sellers lose their profit.</p><p>What he did was, he just made an instagram account, uploaded the flyers consist of the service he offered, phone/whatsapp number, small text about the story behind why he did it, and start selling his service. He didn’t build a fancy mobile apps to acquire the customers to start this idea, although I know he is a great software developer as well. Pretty sure he will do it when the market is validated. This is the lean approach. So lean is really just about building something in an intelligent way where we’re not using the resources until we know we actually have to. And this way we safe a ton of money and time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TG3Jhl2tQdNOdFErv7AU2A.png" /><figcaption>instagram : @tumbasno.id</figcaption></figure><p>Get the point, right? at least I do :) . Let’s jump to the next thing.</p><h3>Agile</h3><p>You can find some other definitions about what is agile out there, but this is as per my understanding. So what is agile? Agile is just a way of applying the lean mindset to software development. This is sort of project management framework for software development.</p><p>Agile is an iterative method to develop software where we do it batch by batch. We split the whole big requirement and group it into small batches, then do them in order to not wasting resources. So for example, let’s say we have about 15 features we need to build for our apps that we’re sure users will use it. If we do it in agile way, in the first phase probably we will only research and develop the first until five features that we think are most important. Then we release them and waiting for user feedbacks before we go to the next phase to do the remaining features.</p><p>I also apply the agile method in writing this post. So I will split this story become some parts (maybe 2, or more?) because I want to release this post faster and hear the feedback.</p><p>No, that’s because I’m tired to arrange the words actually. It is 1:27 AM and I miss my bed.</p><p>Keep sharing small things ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40b660e9e41e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup Multi Profile AWS CLI]]></title>
            <link>https://ekypradhana.medium.com/setup-multi-profile-aws-cli-cecd51ba3450?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/cecd51ba3450</guid>
            <category><![CDATA[aws-eks]]></category>
            <category><![CDATA[aws-cli]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Tue, 28 Sep 2021 10:45:46 GMT</pubDate>
            <atom:updated>2021-09-28T10:45:46.960Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been so loooonggg time I didn’t write anything in this page. Okay to fire up the writing spirit inside, let’s document something simple, but frequently I forget how to do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lF22yPXDljP0_3SDDXbjbw.jpeg" /><figcaption>credit : google images</figcaption></figure><h3>Ok let’s make it quick!</h3><p>First, to configure the aws profile in CLI, we can use :</p><pre>aws configure</pre><p>and then we will have a prompt to input AWS access key id, AWS secret, default region name, and default output. Then the information will be stored in ~/.aws/credentials (or somewhere in Windows file system, I use Mac anw)</p><p>It will configure the [default] profile of our AWS CLI credentials. To add another profile, we can use :</p><pre>aws configure --profile our_second_profile</pre><p>Then the credentials file will look like this :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*rFFDJQJkFibrivuQ8HAQqQ.png" /></figure><p>Easy, right?</p><p>In this case I use that credentials to manage my k8s cluster in EKS using kubectl. We can simply add flag/args ‘profile’ and fill with the profile name to switch between EKS clusters.</p><pre>aws eks --region ap-southeast-1 update-kubeconfig --name ada-dev --profile ada-dev</pre><p>Then we can simply use standard kubectl command to do what we want</p><pre>kubectl get pods -n your-namespace</pre><p>Thank you and keep sharing small things!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cecd51ba3450" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Multi Stage Docker]]></title>
            <link>https://medium.com/kanoteknologi/multi-stage-docker-c216757ae66d?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/c216757ae66d</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 00:01:01 GMT</pubDate>
            <atom:updated>2018-11-13T00:01:01.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-0T-ZwNq9ByrChspxs50g.png" /></figure><p>In our <a href="https://medium.com/eaciit-engineering/dockerized-your-golang-application-37e9067ad6dd">previous post about Docker</a>, we have built an image with a simple Golang apps inside of it. We created it from golang:latest as a base image taken from the official Docker Hub. And yes, it was running perfectly. But if we see more detail, we will find that the size of the image is so big. And of course we don’t want to save an image (that only contains a simple application) with that size in our local registry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXgQwGYkfgLzk71LZP8cpQ.png" /><figcaption>781 MB — are you kidding me?</figcaption></figure><h3>The Challenge!</h3><blockquote>If I have to build and save many Docker Images with that size in my local registry, where should I save my downloaded blu-ray movies then?</blockquote><p>Well.. ummm.. that’s…. wow what a challenge!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCG4B1zFIqXv9M5YT1mj6A.png" /><figcaption>Wait, I can explain it…</figcaption></figure><h3>The Better Challenge!</h3><blockquote>How can we minimize the size of the Docker Images so there will be a lot of space in my storage so that I can use to save my ummm…. kids photos?</blockquote><p>Well, ok.. whatever.</p><p>This is why we need a <strong>Multi Stage Docker!</strong></p><p>The idea is simple, it is like we use one computer that contains everything we need to build our apps, in this case a Golang development environment. Then we build the code there to produce a binary file. Once complete, we copy that binary file (and some other needed files too) to another very basic clean computer. We don’t need any libraries or dependencies to be installed in this computer, all we need is just making the service running there. Well maybe in some cases, we still need something to be installed too, but it should be not as complex as what’s in the first computer. So we will find the size of second computer is not as big as the first computer, even way smaller. And that second computer that will be our Docker image.</p><h3>First, Knowing Our Base Image</h3><p>Since we use golang:latest as our base image, let’s get a little closer about it so we have a better understanding about what we are using on. Let’s go to the <a href="https://hub.docker.com/r/library/golang/tags/">official golang repository on Docker Hub</a> and get acquainted. We’ll see our base image’s size there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iMJlaaq-AUrMNOoS_c91UA.png" /><figcaption>Golang Repo on Docker Hub</figcaption></figure><p>Yes, it is 295 MB. But don’t be surprised now, it is only the compressed size. What about the uncompressed size? Let’s take a look again to our docker images list, because actually we pulled the golang:latest image from Docker Hub and extract it into our local registry when we built our latest container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7UYfo5Q2PiYJTA-ZMWeHeQ.png" /></figure><p>Now you may be surprised, it is 774 MB! No wonder if our dockerizedgoapp image’s size is more than that.</p><h3>Use Very Basic Base Image</h3><p>From the <strong><em>2 computers analogy</em></strong><em> </em>above, I believe we have a better perspective now. So we will use golang:latest (first base image) as a specification for the computer no 1, which will build our application and produce the executable binary file. Now what about the computer no 2 ? what will we use for that?</p><p>Let’s say thanks to : <strong>alpine. </strong><em>A minimal Docker image based on </em><a href="https://alpinelinux.org/"><em>Alpine Linux</em></a><em> with a complete package index and only 5 MB in size!</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Hv0uq9tUSvIubva5VHcdA.png" /></figure><p>We can find it in the <a href="https://hub.docker.com/explore/">Docker Hub official repositories</a>. It is lightweight and very commonly used as a base image of Docker container. And if you follow some tutorials about Docker for beginners on Google or YouTube, most of them will use this image for their first Docker container.</p><p>So let’s start modifying our Dockerfile now.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4eaa26e3634b86e6b5e0d83047e31826/href">https://medium.com/media/4eaa26e3634b86e6b5e0d83047e31826/href</a></iframe><p>It’s beautiful, isn’t it? And I’m sure you get the point at the first sight reading the changes.</p><p>One thing we should note that, the way we build our Golang source (line no 6) is also getting changed. The reason is to make sure the binary is running well on alpine, we need to adjust it because it is different environment.</p><p>Well, let’s build it and see the result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAXrEhiB44mvaAYb_Jtn8w.png" /><figcaption>Build process result</figcaption></figure><p>When you want to see the size….. better you prepare yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZu2EES3KtulucM3xAxeSA.png" /></figure><p><strong>Wohooo… It is 10.6MB only! ❤ ❤ ❤</strong></p><p>And the most important thing, it is still running well as expected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y34S5BpGmLj3Y6ifJDcHNQ.png" /></figure><h4><em>And…. IT’S DONE!</em></h4><p>It is simple, yet applicable. At least for me, the only-256GB-SSD notebook user.</p><p><a href="https://github.com/ekypradhana/eaciit-engineering">Please find the github repo for this project here.</a></p><p>— — —</p><p><em>“Thanks man! Now I am still able to enjoy my Iron Man collections anywhere directly from my local drive”</em></p><p><em>“Wait… so what about your babies photos?”</em></p><p><em>“It is safe….. on my DropBox :D”</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c216757ae66d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kanoteknologi/multi-stage-docker-c216757ae66d">Multi Stage Docker</a> was originally published in <a href="https://medium.com/kanoteknologi">KANO Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dockerized Your Golang Application]]></title>
            <link>https://medium.com/kanoteknologi/dockerized-your-golang-application-37e9067ad6dd?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/37e9067ad6dd</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Tue, 06 Nov 2018 18:30:40 GMT</pubDate>
            <atom:updated>2018-11-08T07:59:17.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXihJiQb9lFeTEBkYnXKww.png" /></figure><p>When we finally jump into the modern software development world, especially in the microservices architecture, one thing we should understand is containerized environment. It makes us so easier to deploy our application anywhere without risking other applications that are running on the same server, with minimum effort of configuration. We can say, build once, run anywhere.</p><p>And Docker, is very common and powerful platform to create and manage containerized environment. It lets us to package up the entire applications and everything else that is needed by the application to run, including the libraries, dependencies, environment configuration, etc. In other words, we can think of containers as portable, packaged bits of functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*URnhVKchJ6p7TG7viwbOoQ.png" /><figcaption>Source : <a href="https://www.docker.com/resources/what-container">Docker.com</a></figcaption></figure><p>This post will give us a ‘getting-started’ guide how to Dockerized a Golang application. I assume we have installed Docker in our machine. If not, it is better for us to follow their <a href="https://docs.docker.com/install/">official documentation about how to install Docker here</a>. Please choose your operating system on the left menu, and we’re good to go.</p><h3>Prepare The Application</h3><p>Before we start, I have prepared a simple Golang application serving on defined port (8080) and accessible through http request.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/de46bfe9557427f2987f4bec5fe0b88a/href">https://medium.com/media/de46bfe9557427f2987f4bec5fe0b88a/href</a></iframe><p>Let’s run it and access it using a browser :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEvl-GZPR8_EX9vYe8NRug.png" /><figcaption>Application is running</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4IVF2S9jVzECyhy084G9w.png" /><figcaption>Accessed via browser</figcaption></figure><h3>Dockerfile</h3><p>To create a Docker container, we will use something called Docker Image. And to build a Docker Image, we need to provide a Dockerfile, so Docker knows what to do. In general, Dockerfile is placed on the root of the project directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/38b8c123f335ff64aa33128038193b47/href">https://medium.com/media/38b8c123f335ff64aa33128038193b47/href</a></iframe><p>Seems like a bunch of instruction?</p><ol><li>FROM : it will tell Docker to specify which base image from <a href="https://hub.docker.com/explore/">Docker Hub</a> we want to build from. In this case, we use golang:latest. We can also choose some other versions we want. Why would we love to use this? because we don’t want to create golang environment from the scratch, like installing golang manually, defining the environment variable ($GOPATH, $GOROOT), creating the project folder structure, etc. By using this image, we will have the containerized environment with golang pre-installed there. So we can directly build our code, and then run it as a independent service. Don’t worry, it is official. And most importantly, it is free to use.</li><li>MAINTAINER : when you want to tell the world that you are the one who responsible of this great and cool Docker image. It is a narcissistic command I think :)</li><li>ADD : copy our whole project to specific destination of the image.</li><li>WORKDIR : will tell the Docker to move the active working directory. So after we copy the file to /go/src/DockerizedGoApp, we enter that directory. It is like when we type cd /go/src/DockerizedGoApp in the linux administration terminal.</li><li>RUN : will tell Docker to run the following command. In this case, we want to build our application to become an executable binary.</li><li>EXPOSE : exposes a port which the container will listen on.</li><li>CMD : sets the default command to execute when we start our container.</li></ol><p>Finally, let’s build our image and tag it with name <strong>‘dockerizedgoapp’</strong>.</p><pre>docker build . -t dockerizedgoapp</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QEzIy6nIRgg2VXiUtogJNg.png" /><figcaption>Docker build process</figcaption></figure><p>Well done, we have successfully built the image. We can see the list of our images with command docker images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXgQwGYkfgLzk71LZP8cpQ.png" /></figure><h3>Run It!</h3><blockquote>Sometimes you gotta run, before you can walk. -Tony Stark</blockquote><p>Nice quote, but is there any correlation with this article? <em>Man.. come on!</em></p><pre>docker run -p 8080:8080 dockerizedgoapp</pre><p>Wait, why on earth we need that -p flag? Since the docker is isolated environment, we can’t just access it outside from its network, even it is from the host machine. So we need to publish the specific port in the container and map it on the specific port in our host machine. Or we can call it as <em>port-forwarding.</em></p><p>But, we have exposed the port 8080 in our Dockerfile, right? Yes, but still it is just accessible from its internal network. When we have more than 1 Docker containers running and it is connected each other on the same network, they will be able to communicate through their exposed port. Well I think we should have another post regarding this later, please remind me then :)</p><p>So let’s give it a shot!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Oz7VMnMjjhDbsCXG_ynCQ.png" /><figcaption>Container is running</figcaption></figure><p>And access it via browser again :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F4IVF2S9jVzECyhy084G9w.png" /><figcaption>Application is serving from the Docker container and accessed from host machine’s browser</figcaption></figure><p>And we’re done. We have successfully dockerized our golang apps. So what’s next? is it only this? Of course not. Since Docker has become one of must-have skill for the software developer in this microservices era, especially for the DevOps engineer, I highly recommend that we can master it well. So let’s keep exploring my friend :)</p><p>Credit : docker.com, google.com</p><p><a href="https://github.com/ekypradhana/eaciit-engineering">Please find the github repo for this project here.</a></p><p>And don’t forget, <strong>sometimes you gotta run before you can walk!</strong></p><p><em>Man please.. not again.. -_-</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=37e9067ad6dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kanoteknologi/dockerized-your-golang-application-37e9067ad6dd">Dockerized Your Golang Application</a> was originally published in <a href="https://medium.com/kanoteknologi">KANO Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating Microservices Environment with Docker]]></title>
            <link>https://ekypradhana.medium.com/creating-microservices-environment-with-docker-2fb450725b8b?source=rss-d8bdc6760704------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fb450725b8b</guid>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[learning-microservices]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Eky Pradhana]]></dc:creator>
            <pubDate>Fri, 21 Sep 2018 13:45:51 GMT</pubDate>
            <atom:updated>2018-09-21T13:45:51.664Z</atom:updated>
            <content:encoded><![CDATA[<p>Docker is very common and powerful platform to manage container and creating microservices environment, especially in our local machine or development server. This video below explains well about what docker is and why it is good for us to create containerized application.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJprTjTViaEA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJprTjTViaEA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJprTjTViaEA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/585a5edb01d3166a4ee390fc5752b75b/href">https://medium.com/media/585a5edb01d3166a4ee390fc5752b75b/href</a></iframe><p>Still continuing my last post about <a href="https://medium.com/@ekypradhana/simple-microservices-using-golang-and-twirp-rpc-also-mongodb-part-1-4fce5dace540">simple microservices application</a>, I will use that small service for the use case in this post. But I have added 2 more services to make it more interesting. So now we have 3 customized services, which are Product Service, Transaction Service, and WebApp (for the API call / REST). And not forget to mention we also have MongoDB for the database. So actually we will have 4 services. The use case is very simple, those 4 services will be run on Docker, and only one service (WebApp Service) will be exposed so it is allowed to be accessed from outside of the network.</p><p><a href="https://github.com/ekypradhana/simple-microservices">You can find the github repo for this project here.</a></p><p>The architecture of this project will be like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g6maOPHdkekfWsA6nTj88w.png" /><figcaption>Project’s common architecture</figcaption></figure><p>From the YouTube video above, I believe we have basic understanding about Docker. To make the service runs on Docker, we have to build an image for that service. And to do that, we have to provide a Dockerfile for each service so the Docker knows what to do. For example, let’s see the Dockerfile under Product Service, we can find it on product/Dockerfile.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3d1dede036d8cafa19cdf35243979ddb/href">https://medium.com/media/3d1dede036d8cafa19cdf35243979ddb/href</a></iframe><p>If you see the script above, we try to tell docker to create image based on existing image, which is golang:1.9. We don’t have to create the image from the very start because we can find so many pre-customized images on <a href="https://hub.docker.com/explore/">Docker Hub</a>. We use golang:1.9 because we need the containerized environment with golang 1.9 pre-installed there. So we can build our code, and then run it as a independent service. On the next rows, we tell Docker to copy our apps to Docker machine, and getting some dependencies needed to build our apps. So now we have 1 Docker image with Product Service ready to run.</p><p>We also do the same thing on the other service. Kindly please explore the other service folder too.</p><p>Next, we want to make it run together on the same network so they can communicate each other. To do that, Docker has provided the feature called Docker compose. So our services will be managed with single file and we don’t have to run it one by one. Ok let’s see our docker-compose.yaml file on the root directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/762ad44e2b89f0906ae09c82befd4b47/href">https://medium.com/media/762ad44e2b89f0906ae09c82befd4b47/href</a></iframe><p>As we can see there, we create 4 services, which are mongo (for database), product, transaction, and webapp. And only 1 service (webapp) that is opened publicly so we can access it from outside the network as a REST API. I have created 3 endpoints on that service, which are Save, PopulateProduct, and Order. If we hit ‘Save’ and ‘PopulateProduct’, the webapp service will communicate to product service to do the job. And for ‘Order’, it will tell transaction service to do order mechanism. The diagram below will tell us more about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gHoG6UOp6EaLSoD6f1Vscw.png" /><figcaption>Project’s flow and endpoints</figcaption></figure><p>So let’s give it a shot!</p><p>Go to our console, and run :</p><pre>docker-compose up</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rrEMyVibYYmzIXUnYR6Sbg.png" /><figcaption>docker-compose is started</figcaption></figure><p>Next, we can use 3rdparty apps like Postman to hit the endpoints and send some parameters needed. Let’s try to hit ‘PopulateProduct’ :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hN7bMkSbi6b2Q7PxPJtgGw.png" /></figure><p>The result is still empty, because we haven’t saved any product yet. Let’s try to Save product :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n0u4IkGtZt76w9iXRtp-OQ.png" /></figure><p>Ok, the product has been saved successfully. Then let’s try to populate it again :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N7bARS5yzm-BuOSgwNby8w.png" /></figure><p>The product we’ve saved is shown there.</p><p>Now let’s try to hit ‘Order’ endpoint. It will involve all microservices, because once we hit it, the webapp service will tell transaction service to handle it, and the transaction service will then tell the product service to update the stock. Let’s give it a try :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCX4mjW6YMq7xW4Nk4XlzQ.png" /></figure><p>Well then, we’ve placed the order. Let’s wait until the package shipped to our house :)</p><p>Now if we try to populate product again, we will see that the stock is decreased:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9MMLQsqmbfulCa6RgGDlqg.png" /></figure><p>That’s it! It is just a very simple microservices application using Docker. I believe there are so many things we can do more than it, even it is not impossible that we can build Amazon-like platform. But still, so many things we need to explore and improve. Keep moving forward, my friend :)</p><p>Now the next question is, how if one or more services are crashed or shutdown by accident? Of course the data will be messing up. The order has been placed successfully, but the stock is not getting updated. On the bigger scale and case, I believe it will make very serious problem. Then the developers will get terrible headache, they will work over the weekend to address it, they will loose their family time, their children will be crying all day because the plan to go to swimming pool must be canceled, their wives will divorce them because they are getting enough living with developer, wow what a life!</p><p>Hahaha.. not that bad, buddy :)</p><p>So how to tackle it?</p><p>Welcome to Event-Driven Architecture!</p><p>To be continued…</p><p>*mbuh kapan :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fb450725b8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>