<?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 Minal Athukorala on Medium]]></title>
        <description><![CDATA[Stories by Minal Athukorala on Medium]]></description>
        <link>https://medium.com/@minal.ma?source=rss-9fdbac012848------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Minal Athukorala on Medium</title>
            <link>https://medium.com/@minal.ma?source=rss-9fdbac012848------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:11:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@minal.ma/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[Market (Trade) Surveillance: Where RegTech and FinTech meets]]></title>
            <link>https://medium.com/@minal.ma/market-trade-surveillance-where-regtech-and-fintech-meets-4b26d89ce0b6?source=rss-9fdbac012848------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b26d89ce0b6</guid>
            <category><![CDATA[stock-market-surveillance]]></category>
            <category><![CDATA[trade-surveillance]]></category>
            <category><![CDATA[market-surveillance]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[regtech]]></category>
            <dc:creator><![CDATA[Minal Athukorala]]></dc:creator>
            <pubDate>Sun, 08 Jun 2025 13:46:52 GMT</pubDate>
            <atom:updated>2025-06-08T13:46:52.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*USUphzfe9kHJ00Hp" /><figcaption>Photo by <a href="https://unsplash.com/@orenlbz?utm_source=medium&amp;utm_medium=referral">Oren Elbaz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Market (Trade) Surveillance systems are where financial technology (FinTech) and regulatory technology (RegTech) come together to protect the fairness and stability of financial markets. These systems are designed to monitor and analyze trading activities either in realtime or after the trades are done, to detect unusual behavior, such as insider trading, market manipulation, or rule violations. FinTech refers to the use of new technologies to improve financial services, while RegTech focuses on using technology to help firms meet regulatory requirements more efficiently. Market surveillance systems apply advanced tools like data analytics, automation, and artificial intelligence to meet both goals: helping companies (Exchange companies, SEC’s, broker companies) follow the rules and keep markets safe and trustworthy. Those companies provide a great example of how RegTech and FinTech work together in today’s financial world.</p><p>In the early days of financial markets, trade surveilling was a manual process done by exchange staff or regulatory officials. They relied on paper records, phone calls, and daily trading reports to track suspicious activity. Human judgment played a major role like inspectors checking for unusual price movements or large trades and try to connect them to possible misconducts. Eventhough this method was giving out some results, it was slow, human error prone and limited in scope. In markets where millions of dollars traded in a single day, regulators or traders or the exchanges didn’t like the idea of market abusing going unnoticed.</p><p>The need for automated monitoring systems started to become a vital requirement in the 1980s and 1990s, as electronic trading had already begun to rise by that time. Stock exchanges and regulatory bodies started investing in basic surveillance software to scan trades and identify patterns that could indicate market abuse. One of the early examples was the “Stock Watch System” developed by the New York Stock Exchange (NYSE), which helped monitor trading across multiple firms. These early tools used rule based logic to detect predefined scenarios, such as a sudden surge in stock price or volume. Over time, the development of more advanced technologies like machine learning, natural language processing, and cloud computing transformed these early efforts into the smart, realtime surveillance systems we see today on market.</p><p>Modern financial markets operate at high speed and across global platforms, making them more complex than ever before. Trades now happen in milliseconds, and investors can buy and sell assets through various exchanges, often in different countries. This makes it much harder to detect harmful or illegal activities like market manipulation or insider trading without advanced tools. As a result, strong and smart market surveillance systems have become essential, not just to meet regulations, but to protect the fairness and stability of financial markets.</p><p>Real world examples show why this is so important. In the 2010 “Flash Crash” in the U.S., the stock market dropped nearly 1,000 points within minutes before quickly recovering. Investigators found that a trader had used a technique called “spoofing” to trick the market with fake orders. Incidents like this have pushed regulators, such as the U.S. SEC and CFTC, to demand better surveillance systems that can detect these behaviors as they happen.</p><p>To keep up with the fast growing FinTech solutions, financial firms are now using advanced technologies like artificial intelligence and machine learning for surveillance. These systems can analyze huge amounts of data such as trades, emails, and chat messages to find unusual patterns and prevent problems before they grow. Platforms like Eventus, Nasdaq SMARTS, and Aquis Technologies help companies stay compliant with rules like MiFID II in Europe and Dodd-Frank in the U.S.</p><p>Regulators around the world require financial institutions and exchanges to use market surveillance systems to ensure fair, transparent, and stable markets. Without effective monitoring, traders could easily engage in illegal activities like insider trading, market manipulation, spoofing (placing fake orders to move prices), or layering (placing multiple orders to create false demand or supply). These actions can mislead other market participants, manipulate prices, and create unfair advantages damaging both investor confidence and the reputation of the market itself.</p><p>To prevent such risks, regulators like U.S. Securities and Exchange Commission (SEC), the European Securities and Markets Authority (ESMA), and the Financial Conduct Authority (FCA) in the UK require firms and exchanges to have systems in place that can detect and report suspicious trading behaviors. For example, under regulations like MiFID II in Europe and Dodd-Frank in the U.S., firms must be able to monitor transactions in real time and store trade data for audits and investigations making surveillance systems a regulatory compliance. Failing to adhere with these compliances can result in massive fines and reputational damage. A recent example for this is, a European broker was fined €14 million in 2023 for failing to properly monitor trade data, allowing suspicious activity to go unnoticed.</p><p>Without surveillance, it would be difficult to identify unlawful behavior until it’s too late. In extreme cases, unidentified manipulation can lead to financial crashes or significant market losses. For example, if large investors manipulate stock prices and cause artificial price inflation, retail investors might suffer serious losses by the time truth is out. These kind of incidents can make public distrust of exchanges’ and trigger large scale panic selling, leading to broader financial instability.</p><p><strong>Conclusion</strong></p><p>Market surveillance systems are a major part of today’s financial infrastructure, helping to detect and prevent illegal trading activities, ensuring markets remain fair and trustworthy. They are a clear example of how technology is transforming the financial world.</p><p>As digital tools used to monitor financial transactions, they fall under FinTech, supporting innovation, growth and efficiency in the financial sector. At the same time, because they help firms meet legal and regulatory obligations, they are also part of RegTech, which is technology developed specifically to manage compliance. By serving both purposes, market surveillance systems sit at the middle of FinTech and RegTech, playing a crucial role in strengthening both market performance and integrity in the modern financial era.</p><h3>References</h3><p>1] Regtech in financial services: Technology … Available at: https://www.iif.com/portals/0/Files/content/RegTech in Financial Servies.pdf</p><p>2] Securities and Exchange Surveillance Commission 25th anniversary international conference Securities and Exchange Surveillance Commission 25th Anniversary International Conference：SESC. Available at: <a href="https://www.fsa.go.jp/sesc/english/news/others/20171206-1.html">https://www.fsa.go.jp/sesc/english/news/others/20171206-1.html</a></p><p>3] (2018) Fintech and Regtech: Impact on regulators and Banks, Journal of Economics and Business. Available at: <a href="https://www.sciencedirect.com/science/article/abs/pii/S014861951730142X">https://www.sciencedirect.com/science/article/abs/pii/S014861951730142X</a></p><p>4] ComplyLog (2024) Failure in trade surveillance costs broker €14 million, Case Study. Available at: <a href="https://info.complylog.com/compliance-failures/failure-in-trade-surveillance-costs-broker-euro14-million/">https://info.complylog.com/compliance-failures/failure-in-trade-surveillance-costs-broker-euro14-million/</a></p><p>5] Press, K. (2024) Trade surveillance best practices, Eventus. Available at: <a href="https://www.eventus.com/cat-article/why-a-shift-in-regulatory-enforcement-demands-a-new-approach-to-trade-surveillance/">https://www.eventus.com/cat-article/why-a-shift-in-regulatory-enforcement-demands-a-new-approach-to-trade-surveillance/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b26d89ce0b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking Free from Infrastructure: The Era of Serverless Computing]]></title>
            <link>https://medium.com/@minal.ma/breaking-free-from-infrastructure-the-era-of-serverless-computing-363b42de6cf6?source=rss-9fdbac012848------2</link>
            <guid isPermaLink="false">https://medium.com/p/363b42de6cf6</guid>
            <category><![CDATA[functions-as-a-service]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[serverless-computing]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Minal Athukorala]]></dc:creator>
            <pubDate>Sat, 18 Nov 2023 09:54:29 GMT</pubDate>
            <atom:updated>2023-11-18T11:01:26.423Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TzqNlDn4b4hAeQggd94YzQ.jpeg" /></figure><p><strong>No servers?</strong></p><p>The name itself is confusing right? But this doesn’t mean there are no servers attached. What serverless computing really is, this is a cloud computing application development and execution model that enables developers to build and execute applications without having to manage infrastructure. This way as a developer you don’t have to worry about the underlying infrastructure.</p><p>Cloud vendors (AWS, Microsoft Azure, Oracle Cloud) take care of the managing and maintenance of the infrastructure including OS and Patch upgrades, Security and most importantly Resource allocation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYcnycBoHd8PJ-sfcj8DYg.png" /><figcaption>Serverless computing model</figcaption></figure><p>In this model developers buy back-end services from cloud vendors on a pay-as-you-go basis. This way users have to only pay for what they use. The primary purpose of serverless computing is to make it easier for developers to write programs that will operate on cloud platforms and perform a specific role.</p><p>Serverless computing is a fundamental shift in modern application development because it minimizes costs, simplifies development, ensures scalability, promotes event-driven architecture, supports microservices, and facilitates global reach, ultimately enabling developers to focus on building better features.</p><ol><li><strong>Function as a Service (FaaS) — </strong>Serverless computing an functions as a service is usually tightly coupled. In FaaS, we can write individual functions, which are units of execution that respond to events. These functions are stateless and short-lived and triggered by specific events such as HTTP requests, changes in data, or timers.</li><li><strong>Event-driven architecture — </strong>Serverless applications are designed to be event driven. Which means Functions are triggered by events, such as changes in data (new data in a database), HTTP requests, file uploads, or scheduled events. This event-driven architecture allows for automatic scaling, as functions are invoked only when needed.</li><li><strong>Automatic scaling — </strong>One of the main advantages of serverless computing is automatic scaling. The cloud providers dynamically allocate resources to handle the number of incoming requests or events. If our function experiences a sudden spike in traffic, the cloud provider automatically scales up to meet the demand, and scales down during periods of inactivity. This eliminates the need for manual provisioning and scaling.</li><li><strong>Statelessness — </strong>Serverless functions are designed to be stateless, meaning they don’t save any state between invocations. If you want to save the state it should be stored externally, such as in a database or another persistent storage system. This design simplifies scaling and enhances reliability.</li><li><strong>Billing model — </strong>Serverless computing is usually billed on a pay-as-you-go model, where you are charged based on the actual compute resources consumed during the execution of your functions. This can be more cost-effective than traditional server-based models, where you pay for provisioned capacity even if it’s not fully used.</li><li><strong>Vendor specific implementations — </strong>Different cloud providers offer their own serverless computing solutions. For example, AWS has AWS Lambda, Microsoft Azure has Azure Functions, and Google Cloud has Google Cloud Functions. While the basic principles are similar, the specific implementation details and features may differ between providers.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kx0MunAnmkGYN-4AdXF2HQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*02Izrfm7UsBHeW-Z2XQEow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*H09QYDrDbigj7yKv4iuhsw.png" /></figure><p><strong>7.</strong> <strong>Microservices — </strong>Serverless computing is often used with the microservices architecture. Each function can represent a small, independent piece of functionality, and the application as a whole is composed of a collection of these functions.</p><p>Keep in mind that although serverless computing brings advantages like easy scalability, cost savings, and improved developer efficiency, it might not be the best solution for every situation. It’s important to identify the potential drawbacks and compromises before choosing if a serverless architecture is suitable for a specific application. Assessing the limitations and trade-offs is a key step in making an informed decision about whether to use serverless computing for your project.</p><h3>References</h3><p>[1] <em>Serverless computing for business transformation</em> (2022) <em>Hexaware</em>. Available at: <a href="https://hexaware.com/blogs/serverless-computing-the-mantra-for-business-transformation-and-efficiency/">https://hexaware.com/blogs/serverless-computing-the-mantra-for-business-transformation-and-efficiency/.</a></p><p>[2] Pujara, P. (2022) <em>Serverless Cloud Computing Business Benefits? — use cases</em>, <em>Multiqos Blog</em>. Available at: <a href="https://multiqos.com/blogs/business-benefits-of-serverless-computing/">https://multiqos.com/blogs/business-benefits-of-serverless-computing/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=363b42de6cf6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Containerization before Docker]]></title>
            <link>https://medium.com/@minal.ma/containerization-before-docker-c8bf2ff57fa8?source=rss-9fdbac012848------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8bf2ff57fa8</guid>
            <category><![CDATA[containerization-history]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[containerization]]></category>
            <dc:creator><![CDATA[Minal Athukorala]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 04:41:38 GMT</pubDate>
            <atom:updated>2023-09-18T05:02:52.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKGCmCLDI4wrIJXHUhEACg.png" /></figure><p><strong>What’s Docker and what does it actually do?</strong></p><p>Docker is an open-source containerization platform used for developing, deploying, and managing applications using lightweight environments called containers.</p><p>Docker packages application components and their dependencies into “Containers” that can run consistently across different environments, simplifying application development, deployment, and scaling. Docker ensures that application components are isolated from one another and the host system, enhancing security and resource efficiency. Docker makes it easier for developers to work with complex applications and deploy them reliably in various settings.</p><p><strong>Docker Containers</strong></p><p>When developing distributed applications, hundreds of components can be used, and these may need their own separate dependencies for the application. By using containers, we can separate these components and assign specific dependencies for each component. This way if the developers need to change (update, delete, add) a dependency in a component, they can do it without affecting the whole application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/345/1*U6vfdpnblRIoRVN-AgJ29g.jpeg" /><figcaption>Docker container example</figcaption></figure><p><strong>Containerization before Docker</strong></p><p>1) Unix chroot</p><p>Containerization was first introduced in 1979 with Unix “chroot” command. “chroot” means change root. What this basically does is it changes the root directory of a Unix system. After entering this command all the processes and its descendants will see the newly entered path as the top-level root directory of the file system hierarchy, isolating them from the rest of the file system.</p><p>After using “chroot” setting up the new environment is up to the user. User must create all the relevant folders such and “/bin”, “/lib”, “usr” manually. Setting up a “chroot” environment manually can be complex and error-prone process. This also only provides a basic form of isolation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/313/1*1r8kLy61pPi4CFdit4pK9w.png" /><figcaption>Basic chroot syntax</figcaption></figure><p>2) FreeBSD Jails</p><p>Jails is a containerization system introduced in FreeBSD Unix distro in 2000. This is an operating system level virtualization system that allows us to create isolated environments called “jails” within a FreeBSD host system. These jails act as independent FreeBSD systems with their own file systems, network configurations and process IDs nut these jails share the same Kernal as the host.</p><p>Users can’t use different OS’s in jails as it share the same FreeBSD Kernal. Jails can provide a strong process and file system isolation as well as resource management option. Users can allocate specific system resource to each jail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*AM-UVaYPp5k8XV7kZ6PxtQ.jpeg" /><figcaption>FreeBSD Jails overview</figcaption></figure><p>3) Virtuozzo</p><p>Virtuozzo is the first commercially available container technology in the world that was introduced in 2001. This is a container-based virtualization technology that allows users to share hardware using an abstraction layer.</p><p>When we virtualize an environment using an container let’s say in a server that virtualized container acts as a completely stand alone server. The container is separated from the other containers in the same physical server. The network can be configured to share between multiple containers.</p><p>An important thing to remember about Virtuozzo is that it’s not a hypervisor nor software interface for a hypervisor.</p><p>Other than these, some few examples for containerization before docker are:</p><p>· Linux VServer (2001) <a href="https://en.wikipedia.org/wiki/Linux-VServer">[Read more]</a></p><p>· Oracle Solaris container (2004) <a href="https://en.wikipedia.org/wiki/Solaris_Containers">[Read more]</a></p><p>· Open VZ (2005) <a href="https://en.wikipedia.org/wiki/OpenVZ">[Read more]</a></p><p>· Process containers by Google (2006) <a href="https://en.wikipedia.org/wiki/Cgroups">[Read more]</a></p><h4>References</h4><p>[1] M. Khanna, “What is a docker container?: Scout APM blog,” Scout, <a href="https://scoutapm.com/blog/what-is-a-docker-container.">https://scoutapm.com/blog/what-is-a-docker-container.</a></p><p>[2] “Day 14 — freebsd jails,” sysadvent, <a href="https://sysadvent.blogspot.com/2010/12/day-14-freebsd-jails.html.">https://sysadvent.blogspot.com/2010/12/day-14-freebsd-jails.html.</a></p><p>[3] A. Kovačević, “What is chroot jail and how to use it?,” Knowledge Base by phoenixNAP, <a href="https://phoenixnap.com/kb/chroot-jail.">https://phoenixnap.com/kb/chroot-jail.</a></p><p>[4] S. J. Bigelow and M. Courtemanche, “What is Docker and how does it work?,” IT Operations, <a href="https://www.techtarget.com/searchitoperations/definition/Docker.">https://www.techtarget.com/searchitoperations/definition/Docker.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8bf2ff57fa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>