<?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 Wida Sari on Medium]]></title>
        <description><![CDATA[Stories by Wida Sari on Medium]]></description>
        <link>https://medium.com/@widasari?source=rss-5f01202a749------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6KSqCwIuSrM66Z5k.</url>
            <title>Stories by Wida Sari on Medium</title>
            <link>https://medium.com/@widasari?source=rss-5f01202a749------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:55:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@widasari/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[Mocking Microservice Databases in Monolithic Database]]></title>
            <link>https://widasari.medium.com/mocking-microservice-databases-in-monolithic-database-ce319191493e?source=rss-5f01202a749------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce319191493e</guid>
            <dc:creator><![CDATA[Wida Sari]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 06:28:20 GMT</pubDate>
            <atom:updated>2023-04-03T06:28:20.066Z</atom:updated>
            <content:encoded><![CDATA[<p>So today, we still haven’t got that message bus and DBMS installed. But another project is about to start, so my time is running out. I have to set up the database, at least in my local machine, so that when the development servers are ready, this DDL could be directly executed.</p><p>Problem is, we’re going to implement this app as microservices, but the database is a single-server, monolithic one. And yet, at the same time we have to properly prepare for it to be used in microservice environment. It is good that we’re using PostgreSQL, it can be monolithic and segmented at the same time, by using schemas.</p><p>Schemas allow us to design a data model that is focused on a certain business process, and this is exactly what we want to achieve with microservice. So, ok, one microservice is going to use one schema.</p><p>But, what about reference and master tables, that are actually belong to another business process? The microservice app, is not assigned to do changes in these reference and master tables, just a read process. In a microservice setting, the app supposed to tap into the message bus, and listen if there’s an ‘order’ to add, update or delete data needed by the microservice. It could have less rows or less columns or both, than the ‘main’ table.</p><p>Read only, and no-write is the exact definition of a view. With the right definition and filters, we could have the same effect of a duplicated table in a microservice. And when that message bus is ready, we can easily replace the view with an actual table, fill it with the data in the view, and add the necessary relationships, without changing table names in the codebase.</p><p>win-win.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce319191493e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Database Design in Microservice]]></title>
            <link>https://widasari.medium.com/database-design-in-microservice-c2718e4e58a4?source=rss-5f01202a749------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2718e4e58a4</guid>
            <dc:creator><![CDATA[Wida Sari]]></dc:creator>
            <pubDate>Sun, 02 Apr 2023 05:08:28 GMT</pubDate>
            <atom:updated>2023-04-02T05:08:28.986Z</atom:updated>
            <content:encoded><![CDATA[<p>So, the project consist of 30 something microservice, 70 something business process and using 3 external app. Those apps are Keycloak for identity and access rights, Odoo for finance and human resource, and Amazon S3 for filing system.</p><p>When I jump in, POs already create swim lane diagrams and mockups, but without enough descriptions. So, first thing I do, is studied those workflows and mockups, and</p><p>Step 1: list all that can be listed.</p><ul><li>existing application name</li><li>table names used in existing application</li><li>mockup group as microservice name</li><li>business process as feature name</li><li>lane names as user roles name</li><li>nouns as table name</li></ul><p>Step 2: map everything that can be mapped:</p><ul><li>map existing app to business process</li><li>map existing table name to existing app</li><li>map business process to mockup group</li><li>map business process to roles</li><li>map business process to nouns</li></ul><p>Step 3: create diagrams to depict conceptual model</p><ul><li>decide which are business process and which are general process</li><li>draw relationships between business processes</li><li>draw relationships between generic objects</li><li>draw relationships between generic and business process</li><li>design conceptual ER, on table level for each of the business process</li><li>revisit mockup and use input names as column names on the right table</li></ul><p>Now, you have a design for a centralized database. This is also the stage where you already have a working monolithic app with monolithic database.</p><p>Next, you break those down into pieces. But, how?</p><p>I am clueless now, I’ll get back to writing when I figure it out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2718e4e58a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Challenge]]></title>
            <link>https://widasari.medium.com/new-challenge-33988a87f292?source=rss-5f01202a749------2</link>
            <guid isPermaLink="false">https://medium.com/p/33988a87f292</guid>
            <dc:creator><![CDATA[Wida Sari]]></dc:creator>
            <pubDate>Sun, 02 Apr 2023 04:12:27 GMT</pubDate>
            <atom:updated>2023-04-02T04:12:27.454Z</atom:updated>
            <content:encoded><![CDATA[<p>So I got a new project challenge. It’s just only beginning, and the beginning is always exciting. Got a role as a System / Data Analyst. System Analyst (and DBA) when the PO team is developing, Data Analyst when data warehouse is brewing.</p><p>The challenge is the tech-stack. I got involved in a similar tech-stack, but it was a POC and a smaller dev team. And the conclusion was we’re just not ready to use that tech stack. Lack of human resources.</p><p>And this time, the team is large, there are more then 10 POs and more then 30 people involved. Super large. Super exciting.</p><p>But, (one of) the down side, is always on the client. As usual, the business process is not clear, the talk is lengthy, procurement is slow, existing system quite confusing. The usual stuff. But I’m not involved in the requirement stage, just accepting results from PO.</p><p>The challenge is the making the design that works. Somehow, someone, dunno who, decide the tech stack is microservice with Kafka and all.</p><p>So, I will (try to) write a series of article, describing the development process, divided into smaller chunks, like database design, workflow engine, API communication, microservice communication, etc.</p><p>Currently brewing, is the database design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33988a87f292" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Post Pertama]]></title>
            <link>https://widasari.medium.com/post-pertama-eff833ae835f?source=rss-5f01202a749------2</link>
            <guid isPermaLink="false">https://medium.com/p/eff833ae835f</guid>
            <category><![CDATA[analisis-sistem]]></category>
            <category><![CDATA[studi-kasus]]></category>
            <category><![CDATA[sistem-informasi]]></category>
            <category><![CDATA[pengembangan-sistem]]></category>
            <dc:creator><![CDATA[Wida Sari]]></dc:creator>
            <pubDate>Tue, 16 Mar 2021 07:37:11 GMT</pubDate>
            <atom:updated>2021-03-16T07:42:13.238Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ZDFVp_qRU1cZ3q5Jc5i9gg.jpeg" /></figure><p>Jadi ini post pertama saya. Saya berencana menulis studi-studi kasus pengembangan sistem, just for fun, tapi mudah-mudahan bisa jadi inspirasi juga. Range sistem mulai dari yang proses bisnis sederhana, sampai rumit, mungkin juga beberapa teori atau tips. Beberapa materi yang terpikir adalah:</p><ul><li>Studi kasus: analisis proses administrasi warga</li><li>Studi kasus: analisis proses lost and found</li><li>Studi kasus: analisis proses barter</li><li>Studi kasus: analisis proses belajar harian</li><li>Studi kasus: analisis pelaporan keuangan</li><li>Tips dan teori: desain basis data relasional</li><li>Tips dan teori: data warehouse</li><li>Tips dan teori: ETL vs ELT</li><li>Tips dan teori: analisis proses bisnis</li><li>Tips dan teori: diagramming</li></ul><p>Ada usulan lain?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eff833ae835f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>