<?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 Champika Mendis on Medium]]></title>
        <description><![CDATA[Stories by Champika Mendis on Medium]]></description>
        <link>https://medium.com/@champikamendis-cm?source=rss-bd3b26b2e8da------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VBwHvfgpuVelfd8rNj6YYQ.jpeg</url>
            <title>Stories by Champika Mendis on Medium</title>
            <link>https://medium.com/@champikamendis-cm?source=rss-bd3b26b2e8da------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:13:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@champikamendis-cm/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[Future of User Interface Design]]></title>
            <link>https://champikamendis-cm.medium.com/future-of-user-interface-design-664f59ec54ec?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/664f59ec54ec</guid>
            <category><![CDATA[future]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[human-computer-interface]]></category>
            <category><![CDATA[user-interface]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Tue, 05 Apr 2022 17:10:06 GMT</pubDate>
            <atom:updated>2022-04-05T17:10:06.123Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*UvCh590PD43iqvjM2IYaMg.jpeg" /></figure><p>The face of a computing system is the User Interface (UI), which is how we engage with our technologies. It’s changed a lot in the previous few years. As a result, it’s clear that user interfaces are crucial in determining the future of computing. When GUI operating systems like Macintosh and Microsoft first hit the market, the concept of UI design was born. But there’s still a long way to go, and future interface ideas could go in a variety of directions.</p><h3>Different user interface designs in future</h3><ol><li><strong><em>Brain-Computer Interface</em></strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*kO-K-QAPUbaJbVIeBnPP5A.jpeg" /></figure><p>Mysteries of the Brain: Brain-Computer Interface A brain-computer interface (BCI), also known as a direct neural interface or a brain-machine interface, is a tool that allows a person (their brain) to connect with a system in a simple way (an external technology).</p><p>Neurons in our brain communicate with other nerve cells by sending and receiving messages. The system in the brain-computer interface is controlled by these neurons, which produce brain waves. The BCI records brain waves and sends them to a computer to finish the task at hand.<br>In reaction to our thoughts, the brain generates electric impulses, and each thought has its own brain wave pattern. The wave signal is used to communicate a concept and operate an object.</p><p>For example, electrocorticography (ECoG) has emerged as a promising signal platform for the study and development of brain-computer interfaces. Electrical brain signals are monitored with electrodes placed directly on the exposed brain surface in electroencephalography (ECoG).</p><p><strong><em>2. Gesture Recognition</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*rfuKcBwXa1MdciKyrVNAtQ.jpeg" /></figure><p>Interfaces controlled by hand gestures or touch, such as scrolling, touching, pinching, tilting, shaking, and so on, are known as gesture interfaces. Gesture-based UI has come a long way in today’s tech world and is gaining popularity in the future of user interface design.</p><p>Gesture recognition interface technology uses sensors or a camera to detect body movement and communicates the data to a computer, which recognizes gestures as commands for devices or programs.</p><p>Movement input from a hand-held controller, a camera that captures movement, or another input device such as gloves is required for gesture recognition. This type of interface is often used to communicate or control video games, entertainment, and mobile devices.</p><p>The combination of gesture-capable movements and touch screens that enable better game control, mostly for 3D gaming, is the future of gestural user interfaces in gaming.</p><p><strong><em>3. Voice User Interface</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EDdw-NMoLWeDIXS14nFO9g.png" /></figure><p>VUIs (Voice User Interfaces) are auditory, visual, and tactile interfaces that allow individuals to interact with gadgets by speaking to them. A VUI does not require the presence of a visual interface.</p><p>Voice The user interface has achieved revolutionary success with smart assistants like Siri, Alexa, Google, and Cortana, with speech being the primary way of human contact. The future of user interface design is now, and it’s becoming better all the time as machine learning skills improve as more people engage with it.</p><p>People prefer voice interfaces since it allows them to work faster and save time. Voice interfaces require less intellect and more intuitive responses, making it simple for users to complete tasks or simplify their work.</p><p>For example:<em> </em>With Google Assistant, one can type messages through a voice command.</p><p>Voice technology is only the beginning; there is much more to this future of user interface that tech specialists have yet to discover.</p><p><strong><em>4. Augmented Reality</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*ED0wxTm7CFoNFWy94n1rIQ.jpeg" /></figure><p>The concept of augmented reality is no longer cutting-edge. Despite the fact that acceptance levels are still low, companies have been using the AR experience in a variety of apps, games, glasses, and systems. However, it has yet to realize its full potential.</p><p>AR transforms the objects around us into an interactive digital experience by using computer-generated input to enrich the real-world environment and add perceptual simulated or virtual material. Healthcare, retail, gambling, entertainment, hospitality, tourism, education, and design are just a few of the industries where it has made inroads. In several industries, the application of augmented reality has improved the user experience.</p><p>In the case of users’ interests, AR aids decision-making and the selection of the best possible product or alternative. The impact IKEA made when it debuted its augmented reality app, which allows customers to choose and arrange furniture in their homes and rooms, as well as decide on the appearance and feel based on their input, is well known.</p><p>Because AR’s promise for a wide range of applications has been proved, the market has been saturated and influenced by this technology. The future of UI design with AR will almost certainly have a major impact on the market.</p><p><strong><em>5. Virtual Reality</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kRBHKTWJAwhsKJI9K8qH9A.jpeg" /></figure><p>Virtual reality, or VR, is a seasoned technical player, but with the introduction of VR gear in recent years, it has reached new heights.</p><p>Virtual Reality (VR) generates a three-dimensional artificial environment that can be explored and interacted with, giving users a one-of-a-kind experience. The virtual environment is created to make the user feel as though they are in a real area.</p><p>The potential for virtual reality to create engaging and fascinating experiences is propelling it into new areas like health, architecture, gaming, entertainment, hospitality, and the arts. Only further study and technology advancements are required before a high-potential interface may have a big impact on our daily lives.</p><p><strong><em>6. Holographic User Interfaces</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aRVK6xWF7KMd4U1LoaZMeg.jpeg" /></figure><p>A holographic display is a type of display that uses light diffraction to produce a virtual three-dimensional depiction of an item. Holograms, unlike other types of 3D imaging, do not require the use of special glasses or other external equipment to view the image. Through science fiction, people have been able to express their ideas and fantasies.</p><h3>Next-generation UI design tools</h3><p>Since the earliest version of Adobe Photoshop, which was designed for altering photographs rather than designing dynamic user interfaces, UI design tools have gone a long way. Adobe XD, Figma, and Sketch are among the latest tools that have made our tasks easier and faster.</p><h3>Integrating Design and Code</h3><p>Future user interface technologies will mix design and coding to make the transition easier for designers and developers. Our current technologies let us create abstract representations of web user interfaces rather than actual web user interfaces. The mock-ups in Figma and Sketch are separate from the source code.</p><h3>Parallel Creation Will Replace Designer/Developer Handoffs</h3><p>During the handoff process, there is an inordinate amount of back-and-forth between designers and developers. Because handoff is so time-consuming and demanding, the quality of the task may deteriorate as a result. Thanks to next-generation design tools that connect with source code, developers will no longer be solely responsible for UI design. Instead, they’ll be able to focus on developing the logical architecture that connects a product’s user interface to its back end and allows it to work properly.</p><h3>Design UI Tools and Developer Software Will Align</h3><p>Designers and developers will be able to collaborate on the same deliverable: the source code, thanks to next-generation design tools that directly interface with the source code. This eliminates throwaway deliverables and allows designers and developers to work on the same deliverable: the source code.</p><h3>UI’s impact on everyday life</h3><p>When it comes to technological breakthroughs, the future is unquestionably exciting, and it has already been here in many ways! We’ll look at some examples of how future user interface design will impact our everyday lives. It’s a wonderful time to consider what technology will bring next. So, what do you think the future holds? What will our future position as designers be like? What strategies will we use to adapt to new technologies? Although many questions remain at this moment, one thing is certain: we will no longer be working as UI/UX designers in the traditional sense.</p><p>Hope you enjoyed reading this article on the Future of User Interface Design. See you soon in the next article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=664f59ec54ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Messaging for your mobile application]]></title>
            <link>https://champikamendis-cm.medium.com/aws-messaging-for-your-mobile-application-ec5f6ff9fb31?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec5f6ff9fb31</guid>
            <category><![CDATA[services]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Fri, 07 May 2021 13:28:07 GMT</pubDate>
            <atom:updated>2021-05-09T08:44:31.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ndTGEhibQeKQ8Ajv6GkWwg.jpeg" /></figure><p>By reading this article carefully, You can get a sound idea about AWS Messaging. And I recommend viewing this article if you are going to use or integrate AWS Messages for your application.</p><h3>Introduction</h3><p>AWS messaging services enable different software systems and end devices–often using different programming languages, and on different platforms–to communicate and exchange information. You can use AWS messaging services to send and receive data in your cloud applications.</p><h3>Match Messaging to your Use-Case</h3><ul><li><a href="https://aws.amazon.com/amazon-mq/?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">Amazon MQ</a></li><li><a href="https://aws.amazon.com/sqs/?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">Amazon SQS</a></li><li><a href="https://aws.amazon.com/sns/?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">Amazon SNS</a></li><li><a href="https://aws.amazon.com/pinpoint/?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">Amazon Pinpoint</a></li><li><a href="https://aws.amazon.com/kinesis/?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">Amazon Kinesis Streams</a></li><li><a href="https://docs.aws.amazon.com/iot/latest/developerguide/iot-message-broker.html?sc_channel=ta&amp;sc_campaign=modernmessagingapplicationintegration&amp;sc_geo=namer&amp;sc_country=us&amp;sc_outcome=aware">AWS IoT Message Broker</a></li></ul><h3>Amazon MQ</h3><p>Amazon MQ is a managed message broker service for <a href="http://activemq.apache.org/components/classic/">Apache ActiveMQ</a> and <a href="https://www.rabbitmq.com/">RabbitMQ</a> that makes it easy to set up and operate message brokers on AWS. Amazon MQ reduces your operational responsibilities by managing the provisioning, setup, and maintenance of message brokers for you. Because Amazon MQ connects to your current applications with industry-standard APIs and protocols, you can easily migrate to AWS without having to rewrite code.</p><h4>Pricing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XTL0OjuWyq2f38Qp" /></figure><h4>Benefits</h4><p><em>Migrate quickly</em></p><p>Connecting your current applications to Amazon MQ is easy because it uses industry-standard APIs and protocols for messaging, including JMS, NMS, AMQP 1.0 and 0–9–1, STOMP, MQTT, and WebSocket. This enables you to move from any message broker that uses these standards to Amazon MQ by simply updating the endpoints of your applications to connect to Amazon MQ.</p><p><em>Offload operational responsibilities</em></p><p>Amazon MQ manages the administration and maintenance of message brokers and automatically provisions infrastructure for high availability. There is no need to provision hardware or install and maintain software and Amazon MQ automatically manages tasks such as software upgrades, security updates, and failure detection and recovery.</p><p>Durable messaging made easy.</p><p>Amazon MQ is automatically provisioned for high availability and message durability when you connect your message brokers. Amazon MQ stores messages redundantly across multiple Availability Zones (AZ) within an AWS region and will continue to be available if a component or AZ fails.</p><h3>Amazon SQS</h3><p>Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS eliminates the complexity and overhead associated with managing and operating message-oriented middleware and empowers developers to focus on differentiating work. Using SQS, you can send, store, and receive messages between software components at any volume, without losing messages or requiring other services to be available. Get started with SQS in minutes using the AWS console, Command Line Interface or SDK of your choice, and three simple commands.</p><p>SQS offers two types of message queues. Standard queues offer maximum throughput, best-effort ordering, and at least one delivery. SQS FIFO queues are designed to guarantee that messages are processed exactly once, in the exact order that they are sent.</p><h4>Pricing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JuXVDqwj4VeNWMIc" /></figure><h4>Benefits</h4><p><em>Eliminate administrative overhead</em></p><p>AWS manages all ongoing operations and underlying infrastructure needed to provide a highly available and scalable message queuing service. With SQS, there is no upfront cost, no need to acquire, install, and configure messaging software, and no time-consuming build-out and maintenance of supporting infrastructure. SQS queues are dynamically created and scale automatically so you can build and grow applications quickly and efficiently.</p><p><em>Reliably deliver messages</em></p><p>Use Amazon SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be available. SQS lets you decouple application components so that they run and fail independently, increasing the overall fault tolerance of the system. Multiple copies of every message are stored redundantly across multiple availability zones so that they are available whenever needed.</p><p><em>Keep sensitive data secure</em></p><p>You can use Amazon SQS to exchange sensitive data between applications using server-side encryption (SSE) to encrypt each message body. Amazon SQS SSE integration with AWS Key Management Service (KMS) allows you to centrally manage the keys that protect SQS messages along with keys that protect your other AWS resources. AWS KMS logs every use of your encryption keys to AWS CloudTrail to help meet your regulatory and compliance needs.</p><p><em>Scale elastically and cost-effectively</em></p><p>Amazon SQS leverages the AWS cloud to dynamically scale based on demand. SQS scales elastically with your application so you don’t have to worry about capacity planning and pre-provisioning. There is no limit to the number of messages per queue, and standard queues provide nearly unlimited throughput. Costs are based on usage which provides significant cost saving versus the “always-on” model of self-managed messaging middleware.</p><h3>Amazon SNS</h3><p>Amazon Simple Notification Service (Amazon SNS) is a fully managed messaging service for both application-to-application (A2A) and application-to-person (A2P) communication.</p><p>The A2A pub/sub functionality provides topics for high-throughput, push-based, many-to-many messaging between distributed systems, microservices, and event-driven serverless applications. Using Amazon SNS topics, your publisher systems can fan-out messages to a large number of subscriber systems including Amazon SQS queues, AWS Lambda functions, and HTTPS endpoints, for parallel processing, and Amazon Kinesis Data Firehose. The A2P functionality enables you to send messages to users at scale via SMS, mobile push, and email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jIChvgkXg2ZLjBig" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7szpUYr3EMvKLTFs" /></figure><h4>Benefits</h4><p><em>Modernize and decouple your applications</em></p><p>Amazon SNS enables you to modernize your applications and decouple them into smaller, independent components that are easier to develop, deploy and maintain. Leveraging a pub/sub-event-driven architecture for your application improves performance, reliability, and allows each component to scale independently.</p><p><em>Send messages directly to millions of users</em></p><p>Amazon SNS enables you to send messages or notifications directly to users with SMS text messages to over 200 countries, mobile push on Apple, Android, and other platforms or email (SMTP). Amazon SNS provides redundancy across multiple SMS providers and allows you to push mobile notifications using a single endpoint for all platforms.</p><p><em>Reliably deliver messages</em></p><p>Amazon SNS uses a number of strategies that work together to provide message durability. To start, published messages are stored across multiple, geographically separated servers and data centers. If a subscribed endpoint isn’t available, Amazon SNS executes a <a href="https://docs.aws.amazon.com/sns/latest/dg/sns-message-delivery-retries.html">message delivery retry policy</a>. To preserve any messages that aren’t delivered before the delivery retry policy ends, you can create a <a href="https://docs.aws.amazon.com/sns/latest/dg/sns-dead-letter-queues.html">dead-letter queue</a>. You can also subscribe to <a href="https://docs.aws.amazon.com/sns/latest/dg/sns-kinesis-subscriber.html">Amazon Kinesis Data Firehose delivery streams to SNS topics</a>, which allows messages to be sent to durable endpoints such as Amazon S3 buckets or Amazon Redshift tables.</p><p><em>Automatically scale your workload</em></p><p>Amazon SNS leverages the proven AWS cloud to dynamically scale with your application. Amazon SNS is a fully managed service, taking care of the heavy lifting related to capacity planning, provisioning, monitoring, and patching. The service is designed to handle high-throughput, bursty traffic patterns and enables you to send millions of messages per second.</p><p><em>Ensure accuracy with message ordering and deduplication</em></p><p><a href="https://aws.amazon.com/sns/features/#Topic_types">Amazon SNS FIFO topics</a> work with <a href="https://aws.amazon.com/sns/features/#Topic_types">Amazon SQS FIFO queues</a> to ensure messages are delivered in a strictly ordered manner and are only processed once (deduplicated). This enables you to maintain consistency when processing transactions across a single or multiple independent services where it’s critical that messages are in the correct order. It also allows you to offload the effort of writing custom code for ordering and message deduplication.</p><p><em>Simplify your architecture with Message Filtering</em></p><p>Amazon SNS helps you simplify your pub/sub messaging architecture by offloading the message filtering logic from your subscriber systems, and message routing logic from your publisher systems. With Amazon SNS message filtering, subscribing endpoints receive only the messages of interest, instead of all messages published to the topic. Amazon CloudWatch gives visibility into your filtering activity, and AWS CloudFormation allows you to deploy subscription filter policies in an automated and secure manner.</p><h3>Amazon Pinpoint</h3><p>Amazon Pinpoint is a flexible and scalable outbound and inbound marketing communications service. You can connect with customers over channels like email, SMS, push, or voice. Amazon Pinpoint is easy to set up, easy to use and is flexible for all marketing communication scenarios. Segment your campaign audience for the right customer and personalize your messages with the right content. Delivery and campaign metrics in Amazon Pinpoint measure the success of your communications. Amazon Pinpoint can grow with you and scales globally to billions of messages per day across channels.</p><h4>Pricing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3WOp_J3F33F8QdfR" /></figure><h4>Benefits</h4><p><em>Get started quickly</em></p><p>Whether you are a marketer or a developer, Amazon Pinpoint is flexible for marketing, bulk, or transactional communications use cases. Marketers can design, orchestrate, and run campaigns visually through the console. Developers can leverage the Amazon Pinpoint APIs for message sending, scheduling campaigns, or tracking web and mobile activities. Send across channels like email, SMS, or push notifications.</p><p><em>Segment and personalize for impact</em></p><p>Segment your audience for the right group of customers based on existing customer lists, attributes or use Amazon Pinpoint to create segments from mobile and web application data. Personalize the right message content to engage and delight your customers using both static and dynamic attributes. Marketers can also visually create a customer journey that automates multi-step campaigns.</p><p><em>Measure your efficiency</em></p><p>From message delivery results to campaign data like opens and clicks, use metrics to understand the success of your communications. Amazon Pinpoint updates your customer lists with results to reflect learnings for the next campaign. View the campaign metrics natively in the Amazon Pinpoint reports or stream data to nearly any destination.</p><p><em>Scale securely with the experts</em></p><p>Based on the scale and security of AWS, Amazon Pinpoint provides a reliable customer experience that can grow with you. Amazon has relationships with the top email providers, telecoms, and spam advisories to ensure the highest customer delivery rates.</p><h4>Use-cases</h4><p><em>Marketing messages</em></p><p>Promote your products and services with basic templates or highly personalized messages, including special offers, newsletters, and other engaging content. You can use Amazon Pinpoint to create targeted groups of customers, and then send them campaign-based messages. You can also design multi-step journeys for a complete customer experience with custom channels, email, SMS, or push notifications.</p><p><em>Transactional messages</em></p><p>Send immediate, trigger-based customer communications across channels directly from your application, such as purchase confirmations, one-time passwords, or shipping notifications. With SMS, you can receive messages back from your customers.</p><p><em>Bulk communications</em></p><p>Send messages to communities of millions, including notifications and announcements. After you send your messages, use the built-in analytics of Amazon Pinpoint to understand how your outreach impacted your business goals.</p><h3>Amazon Kinesis Streams</h3><p>Amazon Kinesis makes it easy to collect, process, and analyze real-time, streaming data so you can get timely insights and react quickly to new information. Amazon Kinesis offers key capabilities to cost-effectively process streaming data at any scale, along with the flexibility to choose the tools that best suit the requirements of your application. With Amazon Kinesis, you can ingest real-time data such as video, audio, application logs, website clickstreams, and IoT telemetry data for machine learning, analytics, and other applications. Amazon Kinesis enables you to process and analyze data as it arrives and respond instantly instead of having to wait until all your data is collected before the processing can begin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2lhTagdzB74pvtjV" /></figure><h4>Benefits</h4><p><em>Real-time</em></p><p>Amazon Kinesis enables you to ingest, buffer, and process streaming data in real-time, so you can derive insights in seconds or minutes instead of hours or days.</p><p><em>Fully managed</em></p><p>Amazon Kinesis is fully managed and runs your streaming applications without requiring you to manage any infrastructure.</p><p><em>Scalable</em></p><p>Amazon Kinesis can handle any amount of streaming data and process data from hundreds of thousands of sources with very low latencies.</p><h4>Amazon Kinesis capabilities</h4><p><a href="https://aws.amazon.com/kinesis/video-streams/">Kinesis Video Streams</a></p><p>Amazon Kinesis Video Streams makes it easy to securely stream video from connected devices to AWS for analytics, machine learning (ML), and other processing.</p><p><a href="https://aws.amazon.com/kinesis/data-streams/">Kinesis Data Streams</a></p><p>Amazon Kinesis Data Streams is a scalable and durable real-time data streaming service that can continuously capture gigabytes of data per second from hundreds of thousands of sources.</p><p><a href="https://aws.amazon.com/kinesis/data-firehose/">Kinesis Data Firehose</a></p><p>Amazon Kinesis Data Firehose is the easiest way to capture, transform, and load data streams into AWS data stores for near real-time analytics with existing business intelligence tools.</p><p><a href="https://aws.amazon.com/kinesis/data-analytics/">Kinesis Data Analytics</a></p><p>Amazon Kinesis Data Analytics is the easiest way to process data streams in real-time with SQL or Apache Flink without having to learn new programming languages or processing frameworks.</p><h3>AWS IoT Message Broker</h3><p>AWS IoT Core supports devices and clients that use the MQTT and the MQTT over WebSocket Secure (WSS) protocols to publish and subscribe to messages and devices and clients that use the HTTPS protocol to publish messages. All protocols support IPv4 and IPv6. This section describes the different connection options for devices and clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bXNQ01PMaWBv1cVV" /></figure><p><strong>By referring to all this stuff you can decide what service matches your purpose. Then you can integrate it into your app.</strong></p><p>Reference: <a href="https://aws.amazon.com/messaging/">https://aws.amazon.com/messaging/</a></p><p>Thank you, everyone. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec5f6ff9fb31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Firebase Cloud Messaging (FCM) and its Push Notification Service]]></title>
            <link>https://champikamendis-cm.medium.com/firebase-cloud-messaging-fcm-and-its-push-notification-service-a710275da43?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/a710275da43</guid>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[firebase]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 03:42:04 GMT</pubDate>
            <atom:updated>2021-03-11T03:42:04.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Mk7mwwIHqjxs3JsFWrw0g.jpeg" /><figcaption>Cloud Messaging</figcaption></figure><p><strong><em>I mainly focus here to discuss Firebase Cloud Messaging(FCM). And give you some more idea about its push notification service.</em></strong></p><h3>Introduction</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*_j7Cbtzpqneraf_YyLyEJg.png" /></figure><p>Firebase Cloud Messaging, formerly known as Google Cloud Messaging, is a cross-platform cloud solution for messages and notifications for Android, iOS, and web applications, which currently can be used at no cost.</p><h3>Common capabilities and limitations</h3><h4>Types of messages that can be sent</h4><p>1. Notification Message: Notification messages are handled by firebase SDK itself. Typically, the notification message contains a title, message, icon, etc., These messages can be sent from the <a href="https://console.firebase.google.com/">firebase console</a> UI. By sending this kind of message, you won’t get much control over the notification. The notification will be shown automatically when the app is in the background.</p><p>2. Data Message: Data messages have to be handled by the Android app. You can add this kind of message if you want to send some additional data along with the notification. But sending these messages through the Firebase console is not possible. You need to have a server-side logic to send the notification using Firebase API. You need to use a data key when sending this message.</p><p><strong>The maximum payload for both message types is 4KB.</strong></p><p>3. Messages with both notification and data payload:</p><p>· A message can also contain both notification and data payload. When these kinds of messages are sent, they will be handled in two scenarios depending upon the app state (background/foreground). For these messages, we can use both notification and data keys.</p><p>· When in the background — Apps receive the notification payload in the notification tray and only handle the data payload when the user taps on the notification.</p><p>· When in the foreground — App receives a message object with both payloads available.</p><h4>Pricing</h4><p>· Cloud messaging and In-App Messaging are Free of charge.</p><p>· But If we are using firebase functions to send messages, we have to pay for firebase functions as follows.</p><p><strong>Cloud Functions</strong></p><p><strong>* Invocations — Free up to 2M/month. Then $0.40/million</strong></p><p><strong>*GB-seconds — Free up to 400K/month. Then </strong><a href="https://cloud.google.com/functions/pricing"><strong>Google Cloud pricing</strong></a></p><p><strong>*CPU-seconds — Free up to 200K/month. Then </strong><a href="https://cloud.google.com/functions/pricing"><strong>Google Cloud pricing</strong></a></p><p><strong>*Outbound networking — Free up to 5GB/month. Then $0.12/GB</strong></p><p><strong>*Cloud Build minutes — Free up to 120min/day. Then $0.003/min</strong></p><p><strong>*Container storage — No free usage. $0.026/GB</strong></p><h4>Message Latency</h4><p>· The official <a href="https://www.youtube.com/watch?v=sioEY4tWmLI&amp;ab_channel=Firebase">video</a> of Firebase Cloud Messaging says that 95% of your messages will deliver with an average time of 250ms</p><h4>Messaging Delivery &amp; Lifetime</h4><p>· Can send messages by setting priorities.</p><p>· Receiving messages from multiple senders — FCM allows multiple parties to send messages to the same client app. For example, suppose the client app is an article aggregator with multiple contributors, and each of them should be able to send a message when they publish a new article. This message might contain a URL so that the client app can download the article. Instead of having to centralize all sending activity in one location, FCM gives you the ability to let each of these contributors send its own messages. Note that there is a limit of 100 multiple senders.</p><h4>· Maximum message rate to a single device — You can send up to 240 messages/minute and 5,000 messages/hour to a single device. This high threshold is meant to allow for short-term bursts of traffic, such as when users are interacting rapidly over chat. This limit prevents errors in sending logic from inadvertently draining the battery on a device.</h4><h4>· Upstream message limit — We limit <a href="https://firebase.google.com/docs/cloud-messaging/android/upstream">upstream messages</a> at 1,500,000/minute per project to avoid overloading upstream destination servers. We limit upstream messages per device at 1,000/minute to protect against battery drain from bad app behaviors.</h4><h4>· Topic message limit — The topic subscription add/remove rate is limited to 3,000 QPS per project. For message sending rates, see <a href="https://firebase.google.com/docs/cloud-messaging/concept-options#fanout_throttling">Fanout Throttling</a>.</h4><p>· Then, you can configure Firebase to store and resend every message <a href="https://firebase.google.com/docs/cloud-messaging/concept-options?hl=ru#ttl">up to 28 days</a>. Of course, losing a network connection for some time does not prevent a message to arrive.</p><p>· There is another limitation though: <a href="https://firebase.google.com/docs/cloud-messaging/concept-options?hl=ru#collapsible_and_non-collapsible_messages">up to 100 messages can be stored</a> per client. So, if there are more than a hundred, it’s better to re-request the diff.</p><h4>Termination of message service</h4><p>· The best approach it’s to use <a href="https://firebase.google.com/docs/analytics/android/start/">Firebase Analytics for Android</a> with <a href="https://firebase.google.com/docs/analytics/android/events">event logging</a> which automatically log app uninstall using the app_remove event. You can find a complete list of automatically logged events for both Android and iOS <a href="https://support.google.com/firebase/answer/6317485">here</a>. So, you can find who uninstalled the application and who uses it. Then you can select what message and for whom to send that.</p><h3>Multiple Notification feasibilities</h3><p>· Fanout Throttling — Message fanout is the process of sending a message to multiple devices, such as when you target topics and groups, or when you use the <a href="https://console.firebase.google.com/project/_/notification">Notifications composer</a> to target audiences or user segments. Message fanout is not instantaneous and so occasionally you have multiple fanouts in progress concurrently. We limit the number of concurrent message fanouts per project to 1,000. After that, we may reject additional fanout requests or defer the fanout of the requests until some of them already in-progress fanouts complete. The actual achievable fanout rate is influenced by the number of projects requesting fanouts at the same time. A fanout rate of 10,000 QPS for an individual project is not uncommon, but that number is not a guarantee and is a result of the total load on the system. It is important to note that the available fanout capacity is divided among projects and not across fanout requests. So, if your project has two fanouts in progress, then each fanout will only see half of the available fanout rate. The recommended way to maximize your fanout speed is to only have one active fanout in progress at a time.</p><p>· Device Group Messaging — With device group messaging, app servers can send a single message to multiple instances of an app running on devices belonging to a group. Typically, “group” refers to a set of different devices that belong to a single user. All devices in a group share a common notification key, which is the token that FCM uses to fan-out messages to all devices in the group. Device group messaging makes it possible for every app instance in a group to reflect the latest messaging state. In addition to sending messages downstream to a notification key, you can enable devices to send upstream messages to a device group. You can use device group messaging with either the XMPP or HTTP connection server. The limit on data payload is 2KB when sending to iOS devices, and 4KB for other platforms. The maximum number of members allowed for a notification_key is 20.</p><p>· Multiple services that want to send notifications — If We want to make it as easy as possible for any service to be able to send a notification, without worrying about the multiple devices and providers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*bpcS1qBz7c8_eBiBApEbtw.png" /></figure><p>· Can we use Rabbit MQ? — We can use RabbitMQ as an exchange for our job queues. We have a queue for each application ID and provider type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d0oSpqEBC_0_1HN2FSd9YA.png" /></figure><p>This is important because we want to isolate failures for each application and provider type.</p><p>Reference: <a href="https://blog.gojekengineering.com/how-we-manage-a-million-push-notifications-an-hour-549a1e3ca2c2">https://blog.gojekengineering.com/how-we-manage-a-million-push-notifications-an-hour-549a1e3ca2c2</a></p><h3>Security of the communication</h3><h4>· Credentials</h4><p>Project ID</p><p>A unique identifier for your Firebase project, used in requests to the FCM v1 HTTP endpoint. This value is available in the <a href="https://console.firebase.google.com/project/_/settings/general">Firebase console Settings</a> pane.</p><p>Registration token</p><p>A unique token string that identifies each client app instance. The registration token is required for single device and device group messaging. Note that registration tokens must be kept secret.</p><p>Sender ID</p><p>A unique numerical value created when you create your Firebase project, available in the <a href="https://console.firebase.google.com/project/_/settings/cloudmessaging/">Cloud Messaging</a> tab of the Firebase console Settings pane. The sender ID is used to identify each sender that can send messages to the client app.</p><p>Access token</p><p>A short-lived OAuth 2.0 token that authorizes requests to the HTTP v1 API. This token is associated with a service account that belongs to your Firebase project. To create and rotate access tokens, follow the steps described in <a href="https://firebase.google.com/docs/cloud-messaging/auth-server">Authorize Send Requests</a>.</p><p>Server key (for legacy protocols)</p><p>A server key that authorizes your app server for access to Google services, including sending messages via the Firebase Cloud Messaging legacy protocols. You obtain the server key when you create your Firebase project. You can view it in the <a href="https://console.firebase.google.com/project/_/settings/cloudmessaging/">Cloud Messaging</a> tab of the Firebase console Settings pane.</p><p><strong>Important: Do not include the server key anywhere in your client code. Also, make sure to use only server keys to authorize your app server. Android, iOS, and browser keys are rejected by FCM.</strong></p><p>· Network Address Translation and/or Stateful Packet Inspection firewalls</p><p>If your network implements Network Address Translation (NAT) or Stateful Packet Inspection (SPI), implement a 30 minute or larger timeout for our connections over ports 5228–5230. This enables us to provide reliable connectivity while reducing the battery consumption of your users’ mobile devices.</p><p>· Communication Security</p><p>Developers already use HTTPS to communicate with Firebase Cloud Messaging (FCM). The channel between FCM server endpoint and the device is encrypted with SSL over TCP. However, messages are not encrypted end-to-end (E2E) between the developer server and the user device unless developers take special measures.</p><h4>· FMC Protocols</h4><p>Currently, FCM provides these raw server protocols:</p><p>· <a href="https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages">FCM HTTP v1 API</a></p><p>· Legacy <a href="https://firebase.google.com/docs/cloud-messaging/http-server-ref">HTTP protocol</a></p><p>· Legacy <a href="https://firebase.google.com/docs/cloud-messaging/xmpp-server-ref">XMPP Protocol</a></p><p>Your app server can use these protocols separately or in tandem. Because it is the most up-to-date and most flexible for sending messages to multiple platforms, the FCM HTTP v1 API is recommended wherever feasible. If your requirements include upstream messaging from devices to the server, you’ll need to implement the XMPP protocol.</p><p>XMPP messaging differs from HTTP messaging in the following ways:</p><p>· Upstream/Downstream messages</p><p>o HTTP: Downstream only, cloud-to-device.</p><p>o XMPP: Upstream and downstream (device-to-cloud, cloud-to-device).</p><p>· Messaging (synchronous or asynchronous)</p><p>o HTTP: Synchronous. App servers send messages as HTTP POST requests and wait for a response. This mechanism is synchronous and blocks the sender from sending another message until the response is received.</p><p>o XMPP: Asynchronous. App servers send/receive messages to/from all their devices at full line speed over persistent XMPP connections. The XMPP connection server sends acknowledgment or failure notifications (in the form of special ACK and NACK JSON-encoded XMPP messages) asynchronously.</p><p>· JSON</p><p>o HTTP: JSON messages sent as an HTTP POST.</p><p>o XMPP: JSON messages encapsulated in XMPP messages.</p><p>· Plain Text</p><p>o HTTP: Plain Text messages sent as an HTTP POST.</p><p>o XMPP: Not supported.</p><p>· Multicast downstream sends multiple registration tokens.</p><p>o HTTP: Supported in JSON message format.</p><p>o XMPP: Not supported.</p><p>· Authorize Send Requests</p><p>Requests sent to FCM from your app server or trusted environment must be authorized. Note these important differences between legacy HTTP and HTTP v1 API authorization:</p><p>· The FCM HTTP v1 API authorizes requests with a short-lived OAuth 2.0 access token. To mint this token, you can use Google Application Default Credentials (in Google server environments) and/or manually obtain the required credentials from a JSON private key file generated for a service account. If you are using the Firebase Admin SDK to send messages, the library handles the token for you.</p><p>· The legacy protocols can use only long-lived API keys obtained from the Firebase console.</p><p>You can get a better idea of the security background by tapping <a href="https://firebase.google.com/support/privacy">here.</a></p><p>Thank you, everyone. Hope you gain something from my story. Nave a nice day!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a710275da43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Differences Between Monolithic and Micro-Service Architectures]]></title>
            <link>https://champikamendis-cm.medium.com/differences-between-monolithic-and-micro-service-architectures-520697b5794a?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/520697b5794a</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[services]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[monolithic]]></category>
            <category><![CDATA[monolith]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Sun, 21 Feb 2021 10:37:57 GMT</pubDate>
            <atom:updated>2021-02-21T10:37:57.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*kAs0M76LQGWwRjTfBRlCuw.png" /></figure><p>This is an article that describes Micro-Service and Monolith one over the other. And then you can easily find the best architecture which fits your requirement.</p><p>To start with, how about we characterize what we mean by “Monolith” and “Microservice”. The monolith in the sense A solid design is worked as one enormous framework and is normally one code-base. It is regularly sent at the same time, both front and end code together, paying little heed to what was changed. Microservices engineering anyway is the place where an application is worked as a set-up of little services, each with its own code-base. These services are built around specific capabilities and are usually independently deployable.</p><h3>When To Start With A Monolith</h3><p>Here are a few situations that show that you should begin your next task utilizing <strong>Monolithic Architecture:</strong></p><ul><li><strong>Your Team Is At Founding Stage:</strong> Your team is small, between 2–5 members, and is thus unable to tackle a broader and high-overhead microservices architecture.</li><li><strong>You’re Building An Unproven Product or Proof of Concept:</strong> Are you building an unproven product in the market? If it’s a new idea, it’s likely going to pivot and evolve, so a monolith is ideal to allow for rapid product iteration. The same applies to a proof of concept where your goal is just to learn as much as possible as quickly as possible, even if you end up throwing it away.</li><li><strong>You Have No Microservices Experience:</strong> If your team has no prior experience with microservices unless you can justify taking the risk of learning “on the fly” at such an early stage, it’s likely another sign you should stick to a monolith to start.</li></ul><h3>When To Start With Microservices</h3><p>Here are a few situations that show that you should begin your next task utilizing <strong>Micro-Service Architecture:</strong></p><ul><li><strong>You Need Quick, Independent Service Delivery:</strong> Microservices allow for fast, independent delivery of individual parts within a larger, integrated system. Note, depending on your team size, it can take time to see service delivery gains versus starting with the monolith.</li><li><strong>A Piece of Your Platform Needs to Be Extremely Efficient:</strong> If your business is doing intensive processing of petabytes of log volume, you’ll likely want to build that service out in a very efficient language (i.e. C++) while your user dashboard may be built in Ruby on Rails.</li><li><strong>You Plan To Grow Your Team:</strong> Starting with microservices gets your team used to developing in separate small services from the beginning, and having teams separated by service boundaries makes it much easier to scale up your team when you need to without introducing exponential complexity.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=520697b5794a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Authentication Vs Authorization]]></title>
            <link>https://champikamendis-cm.medium.com/authentication-vs-authorization-ec640c3ae347?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec640c3ae347</guid>
            <category><![CDATA[authorization]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Wed, 02 Dec 2020 17:32:26 GMT</pubDate>
            <atom:updated>2020-12-02T17:32:26.520Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In simple terms, authentication is the process of verifying who a user is, while authorization is the process of verifying what they have access to.</strong></p><h3>More about Authentication</h3><p>Authentication is the process of identifying users and validating who they claim to be. One of the most common and obvious factors to authenticate identity is a password. If the user name matches the password credential, it means the identity is valid, and the system grants access to the user.</p><p>Interestingly, with enterprises going passwordless, many use modern authentication techniques like one-time passcodes (OTP) via SMS, or email, single sign-<em>on </em>(SSO), multi-factor authentication (MFA) and biometrics, etc. to authenticate users and deploy security beyond what passwords usually provide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*mftigyDG1yOaJHfpDjmPQQ.jpeg" /><figcaption>Authentication</figcaption></figure><h3>Popular authentication techniques</h3><ul><li><strong>Password-based authentication</strong> is a simple method of authentication that requires a password to verify the user’s identity.</li><li><strong>Passwordless authentication </strong>is where a user is verified through OTP or a magic link delivered to the registered email or phone number.</li><li><strong>2FA/MFA </strong>requires more than one security level, like an additional PIN or security question, to identify a user and grant access to a system.</li><li><strong>Single sign-on</strong> (SSO) allows users to access multiple applications with a single set of credentials.</li><li><strong>Social authentication </strong>verifies and authenticates users with existing credentials from social networking platforms.</li></ul><h3>More about Authorization</h3><p>Authorization happens after a user’s identity has been successfully authenticated. It is about offering full or partial access rights to resources like databases, funds, and other critical information to get the job done.</p><p>In an organization, for example, after an employee is verified and confirmed via ID and password authentication, the next step would be defining what resources the employee would have access to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*KyzSr9YASAyaf3Cm9uPPLQ.jpeg" /><figcaption>Authorization</figcaption></figure><h3>Popular authorization techniques</h3><ul><li><strong>Role-based access controls</strong> (RBAC) can be implemented for system-to-system and user-to-system privilege management.</li><li><strong>JSON web token</strong> (JWT) is an open standard for securely transmitting data between parties, and users are authorized using a public/private key pair.</li><li><strong>SAML </strong>is a standard Single Sign-On format (SSO) where authentication information is exchanged through XML documents that are digitally signed.</li><li><strong>OpenID authorization</strong> verifies user identity based on an authorization server’s authentication.</li><li><strong>OAuth </strong>allows the API to authenticate and access the requested system or resource. Not for user authorization but for clients with resource servers.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec640c3ae347" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Micro-Service Architecture]]></title>
            <link>https://champikamendis-cm.medium.com/micro-service-architecture-821e3c6c7826?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/821e3c6c7826</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[services]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Sun, 01 Nov 2020 04:37:50 GMT</pubDate>
            <atom:updated>2020-11-01T04:37:50.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/409/0*AdDvYEKWvsKV1V5J" /><figcaption>Micro-Service architecture</figcaption></figure><p>Microservices architecture is an architectural development style that allows building an application as a collection of small autonomous services developed for a business domain that communicate with lightweight mechanisms, often an HTTP resource API. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. The microservice architecture enables the rapid, frequent, and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack.</p><h3>The Characteristics Of Microservices</h3><p>We cannot say there is a formal definition of the microservices architectural style, but we can attempt to describe what we see as common characteristics for architectures that fit the label. As with any definition that outlines common characteristics, not all microservice architectures have all the characteristics, but we do expect that most microservice architectures exhibit most characteristics. While we authors have been active members of this rather loose community, we intend to attempt a description of what we see in our own work and in similar efforts by teams we know of. In particular, we are not laying down some definitions to conform to.</p><p><strong>1) Multiple Components</strong></p><p>Software built as microservices can, by definition, be broken down into multiple component services. Why? So that each of these services can be deployed, tweaked, and then redeployed independently without compromising the integrity of an application. As a result, you might only need to change one or more distinct services instead of having to redeploy entire applications. But this approach does have its downsides, including expensive remote calls (instead of in-process calls), coarser-grained remote APIs, and increased complexity when redistributing responsibilities between components.</p><p><strong>2) Built For Business</strong></p><p>The microservices style is usually organized around business capabilities and priorities. Unlike a traditional monolithic development approach — where different teams each have a specific focus on, say, UIs, databases, technology layers, or server-side logic — microservice architecture utilizes cross-functional teams. The responsibilities of each team are to make specific products based on one or more individual services communicating via message bus. In microservices, a team owns the product for its lifetime, as in Amazon’s oft-quoted maxim “<a href="http://www.strehle.de/tim/weblog/archives/2010/11/09/1320">You build it, you run it</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*ObkgHdD9_yEIrgXY" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/0*PlgyTpbk_UHGQko2" /></figure><p><strong>3) Simple Routing</strong></p><p>Microservices act somewhat like the classical UNIX system: they receive requests, process them, and generate a response accordingly. This is the opposite of how many other products such as ESBs (Enterprise Service Buses) work, where high-tech systems for message routing, choreography, and applying business rules are utilized. You could say that microservices have smart endpoints that process info and apply logic, and dumb pipes through which the info flows.</p><p><strong>4) Decentralized</strong></p><p>Since microservices involve a variety of technologies and platforms, old-school methods of centralized governance aren’t optimal. Decentralized governance is favored by the microservices community because its developers strive to produce useful tools that can then be used by others to solve the same problems. Just like decentralized governance, microservice architecture also favors decentralized data management. Monolithic systems use a single logical database across different applications. In a microservice application, each service usually manages its unique database.</p><p><strong>5) Failure Resistant</strong></p><p>Like a well-rounded child, microservices are designed to cope with failure. Since several unique and diverse services are communicating together, it’s quite possible that a service could fail, for one reason or another (e.g., when the supplier isn’t available). In these instances, the client should allow its neighboring services to function while it bows out in as graceful a manner as possible. However, <a href="https://smartbear.com/en-us/learn/performance-monitoring/monitoring-microservices/">monitoring microservices</a> can help prevent the risk of failure. For obvious reasons, this requirement adds more complexity to microservices as compared to monolithic systems architecture.</p><p><strong>6) Evolutionary</strong></p><p>Microservices architecture is an evolutionary design and, again, is ideal for evolutionary systems where you can’t fully anticipate the types of devices that may one day be accessing your application. Many applications start based on monolithic architecture, but as several unforeseen requirements surfaced, can be slowly revamped to microservices that interact over an older monolithic architecture through APIs.</p><p>Microservices are not a silver bullet, and by implementing them you will expose communication, teamwork, and other problems that may have been previously implicit but are now forced out into the open. But <a href="https://smartbear.com/learn/api-design/api-gateways-in-microservices/">API Gateways in Microservices</a> can greatly reduce build and QA time and effort.</p><p>One common issue involves sharing schema/validation logic across services. What A requires to consider some data valid doesn’t always apply to B if B has different needs. The best recommendation is to apply to version and distribute schema in shared libraries. Changes to libraries then become discussions between teams. Also, with strong versioning comes dependencies, which can cause more overhead. The best practice to overcome this is planning around backward compatibility, and accepting <a href="https://smartbear.com/learn/automated-testing/what-is-regression-testing/">regression tests</a> from external services/teams. These prompt you to have a conversation before you disrupt someone else’s business process, not after.</p><p>As with anything else, whether or not microservice architecture is right for you depends on your requirements, because they all have their pros and cons. Here’s a quick rundown of some of the good and bad:</p><p><strong>Props of using Micro-Services</strong></p><ul><li>Microservice architecture gives developers the freedom to independently develop and deploy services</li><li>A microservice can be developed by a fairly small team</li><li>Code for different services can be written in different languages (though many practitioners discourage it)</li><li>Easy integration and automatic deployment (using open-source continuous integration tools such as Jenkins, Hudson, etc.)</li><li>Easy to understand and modify for developers, thus can help a new team member become productive quickly</li><li>The developers can make use of the latest technologies</li><li>The code is organized around business capabilities</li><li>Starts the web container more quickly, so the deployment is also faster</li><li>When change is required in a certain part of the application, only the related service can be modified and redeployed — no need to modify and redeploy the entire application</li><li>Better fault isolation: if one microservice fails, the other will continue to work (although one problematic area of a monolith application can jeopardize the entire system)</li><li>Easy to scale and integrate with third-party services</li><li>No long-term commitment to the technology stack</li></ul><p><strong>Cons of using Micro-Services</strong></p><ul><li>Due to distributed deployment, testing can become complicated and tedious</li><li>An increasing number of services can result in information barriers</li><li>The architecture brings additional complexity as the developers have to mitigate fault tolerance, network latency, and deal with a variety of message formats as well as load balancing</li><li>Being a distributed system, it can result in duplication of effort</li><li>When the number of services increases, integration and managing whole products can become complicated</li><li>In addition to several complexities of monolithic architecture, the developers have to deal with the additional complexity of a distributed system</li><li>Developers have to put additional effort into implementing the mechanism of communication between the services</li><li>Handling use cases that span more than one service without using distributed transactions is not only tough but also requires communication and cooperation between different teams</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=821e3c6c7826" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monolithic Software Architecture]]></title>
            <link>https://champikamendis-cm.medium.com/monolithic-software-architecture-6b805d26c69d?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b805d26c69d</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[patterns]]></category>
            <category><![CDATA[monolithic-architecture]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Wed, 28 Oct 2020 16:11:37 GMT</pubDate>
            <atom:updated>2020-10-28T16:11:37.990Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Software Architecture?</h3><p>According to Wikipedia, it says that “<strong>Software architecture</strong> refers to the fundamental structures of a <strong>software</strong> system and the discipline of creating such structures and systems. Each <strong>structure</strong> comprises <strong>software</strong> elements, relations among them, and properties of both elements and relations.”</p><p>There are many Software Architectural patterns. Of them now I am going to make a description of <strong>Monolithic Software Architecture.</strong></p><h3>Monolithic Architecture Pattern</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/388/0*lAS0DWRfFA5QLPcV" /><figcaption>Monolithic Architectural Pattern</figcaption></figure><p><strong>Monolithic Architecture pattern</strong>, which is the traditional architectural style that is still a good choice for many applications. A monolithic application describes a<strong> single-tiered</strong> software application in which the user interface and data access code are combined into a single program from a single platform. A monolithic application is self-contained and independent from other computing applications.</p><p>Such a monolithic server is a natural way to approach building such a system. All your logic for handling a request runs in a single process, allowing you to use the basic features of your language to divide up the application into classes, functions, and namespaces. With some care, you can run and test the application on a developer’s laptop, and use a deployment pipeline to ensure that changes are properly tested and deployed into production. You can <strong>horizontally scale the monolith</strong> by running many instances behind a load-balancer.</p><p>Monolithic applications can be successful, but increasingly people are feeling frustrations with them — especially as more applications are being deployed to the cloud . Change cycles are tied together — a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it’s often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resources.</p><p><strong>Pros of using Monolithic Architecture:</strong></p><ul><li>Simple to develop.</li><li>Simple to test. For example you can implement end-to-end testing by simply launching the application and testing the UI with Selenium.</li><li>Simple to deploy. You just have to copy the packaged application to a server.</li><li>Simple to scale horizontally by running multiple copies behind a load balancer.</li></ul><p><strong>Cons of using Monolithic Architecture:</strong></p><ul><li>This simple approach has a limitation in size and complexity.</li><li>Application is too large and complex to fully understand and made changes fast and correctly.</li><li>The size of the application can slow down the start-up time.</li><li>You must redeploy the entire application on each update.</li><li>Impact of a change is usually not very well understood which leads to extensive manual testing.</li><li>Continuous deployment is difficult.</li><li>Monolithic applications can also be difficult to scale when different modules have conflicting resource requirements.</li><li>Another problem with monolithic applications is reliability. Bug in any module (e.g. memory leak) can potentially bring down the entire process. Moreover, since all instances of the application are identical, that bug will impact the availability of the entire application.</li><li>Monolithic applications has a barrier to adopting new technologies. Since changes in frameworks or languages will affect an entire application it is extremely expensive in both time and cost.</li></ul><p><em>Thank you everyone for visiting my article and hope you got some idea of Monolithic Architecture by reading this.</em></p><p>I will write more articles on Micro Services and hope to compare Monolithic Architecture with Micro Services architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b805d26c69d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Licenses]]></title>
            <link>https://champikamendis-cm.medium.com/software-licenses-f309af30a876?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/f309af30a876</guid>
            <category><![CDATA[software-licensing]]></category>
            <category><![CDATA[end-user-agreements]]></category>
            <category><![CDATA[software-license]]></category>
            <category><![CDATA[copyright-law]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Tue, 08 Sep 2020 16:29:17 GMT</pubDate>
            <atom:updated>2020-09-08T16:30:04.472Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a Software License?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IeVIyBNGzUfBDY2jSORd5g.jpeg" /></figure><p>A software license is a legal instrument (usually by way of contract law, with or without printed material) governing the use or redistribution of software. Under United States copyright law, all software is copyright protected, in both source code and object code forms, unless that software was developed by the United States Government, in which case it cannot be copyrighted. Authors of copyrighted software can donate their software to the public domain, in which case it is also not covered by copyright and, as a result, cannot be licensed.</p><h3>Why Software Licensing is important?</h3><p>Businesses must be savvy in the licenses they purchase to ensure firstly they are using software legally and secondly, they aren’t paying for licenses that aren’t being used. By acquiring too many software licenses you’re wasting company resources, without enough you leave yourself liable to a potential lawsuit (which is quite costly). Finding the right license agreement can also make it easier to manage software in your company.</p><p>A typical software license grants the licensee, typically an end-user, permission to use one or more copies of the software in ways where such a use would otherwise potentially constitute copyright infringement of the software owner’s exclusive rights under copyright.</p><h3>Ownership vs. licensing</h3><p>Many proprietary or open-source software houses sell the SW copy with a license to use it. There isn’t any transferring of ownership of the good to the user, which hasn’t the warranty of a for live availability of the software, nor isn’t entitled to sell, rent, give it to someone, copy or redistribute it on the Web. License terms and conditions may specify further legal clauses that users can’t negotiate individually or by way of a consumer organization, and can uniquely accept or refuse, returning the product back to the vendor. This right can be effectively applied where the jurisdiction provides a mandatory time for the good decline right after the purchase (as in the European Union law), or a mandatory public advertisement of the license terms, so as to be made readable by users before their purchasing.</p><h3>What are the different types of software licenses?</h3><p>Here are five types of common software license models you should know about. Four are examples of open source licenses (which allow you to reuse code to some extent), and one disallows any reuse whatsoever.</p><p><strong>Public domain</strong>- This is the most permissive type of software license. When software is in the public domain, anyone can modify and use the software without any restrictions. But you should always make sure it’s secure before adding it to your own codebase. Warning: Code that doesn’t have an explicit license is NOT automatically in the public domain. This includes code snippets you find on the internet.</p><p><strong>Permissive-</strong> Permissive licenses are also known as “Apache-style” or “BSD style.” They contain minimal requirements about how the software can be modified or redistributed. This type of software license is perhaps the most popular license used with free and open-source software. Aside from the <a href="https://www.apache.org/licenses/LICENSE-2.0">Apache License</a> and the <a href="https://opensource.org/licenses/BSD-2-Clause">BSD License</a>, another common variant is the MIT License.</p><p><strong>LGPL- </strong>The <a href="https://www.gnu.org/licenses/lgpl-3.0.en.html">GNU Lesser General Public License</a> allows you to link to open source libraries in your software. If you simply compile or link an LGPL-licensed library with your own code, you can release your application under any license you want, even a proprietary license. But if you modify the library or copy parts of it into your code, you’ll have to release your application under similar terms as the LGPL.</p><p><strong>Copyleft-</strong> Copyleft licenses are also known as reciprocal licenses or restrictive licenses. The most well-known example of copyleft or reciprocal license is the GPL. These licenses allow you to modify the licensed code and distribute new works based on it, <em>as long as</em> you distribute any new works or adaptations under the same software license. For example, a component’s license might say the work is free to use and distribute for personal use only. So any derivative you create would also be limited to personal use only. (A derivative is any new software you develop that contains the component.)</p><p>The catch here is that the users of your software would also have the right to modify the code. Therefore, you’d have to make your own source code available. But of course, exposing your source code may not be in your best interests.</p><p><strong>Proprietary-</strong> Of all types of software licenses, this is the most restrictive. The idea behind it is that all rights are reserved. It’s generally used for proprietary software where the work may not be modified or redistributed.</p><h3>How do I know what licenses apply to the code in my codebase?</h3><p>Before you can determine which licenses govern any reused code in your codebase, you need to create a software bill of materials or a list of all the components in your code. And the fastest way to generate that list is with a software composition analysis tool. A good SCA tool will be able to find full components as well as code snippets, and it’ll tell you which licenses apply to each piece of code and whether you might be using licenses that have conflicts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f309af30a876" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ethical Whistle-Blowing]]></title>
            <link>https://champikamendis-cm.medium.com/ethical-whistle-blowing-b79fc4c2479c?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/b79fc4c2479c</guid>
            <category><![CDATA[industry]]></category>
            <category><![CDATA[whistleblowing]]></category>
            <category><![CDATA[ethics]]></category>
            <category><![CDATA[whistleblower]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Sat, 25 Jul 2020 18:16:51 GMT</pubDate>
            <atom:updated>2020-07-25T18:16:51.109Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*ZRQimD5yekVved-9p0j1dg.png" /></figure><p><strong>Ethical</strong> means, legally available. A <strong>whistleblower</strong> is a person, who could be an employee of a company, or a government agency, disclosing information to the public or some higher authority about any wrongdoing, which could be in the form of fraud, corruption, etc. So, <strong>Ethical Whistle Blowing</strong> is someone who makes a sound against an illegal or unethical thing.</p><h3>Reasons For Whistle Blowing</h3><ul><li>Sometimes reasons could be idealistic as an example, Honesty, Efficiency, and Correctness support for the victim of fraud.</li><li>Sometimes reasons could be defensive and it says that he or she is not willing to take a part of that illegal act</li><li>And there are <em>negative minded</em> whistleblowing too. such as due to Disliking the supervisor, Paranoia (Paranoia is thinking and feeling like you are being threatened in some way, even if there is no evidence or very little evidence, that you are.), Loudmouth, To avoid censure — to criticize someone officially.</li></ul><h3>Retribution</h3><p>Whistleblowing generates considerable hostility from the people targeted by the whistleblower and by the organization generally.</p><p>Reasons For Hostility:</p><ul><li>A belief that the whistleblower is disloyal.</li><li>Acting against basic instincts of solidarity and mutual protection (“tribal” instincts).</li><li>Destroying security (jobs &amp; income) of colleagues.</li><li>“Stealing “ information (unfortunately necessary to prove accusations).</li></ul><h3>Whistleblower legislation</h3><ul><li>UNITED STATES: False Claims Act:</li><li>GREAT BRITAIN: The Public Interest Disclosure Act, July 1999.</li><li>NEW ZEALAND: Protected Disclosure Act, Jan 2001.</li><li>NSW: Protected Disclosures Act, 1994.</li><li>VICTORIA: Whistleblowers Protection Act, 2001.</li><li>QUEENSLAND &amp; SO. AUSTRALIA</li><li>AUSTRALIA: Democrats proposal before the Senate.</li><li>CANADA: Common Law: wrongful dismissal only.</li></ul><h3>You should be aware of followings Before you blow the whistle:</h3><ul><li>Seek legal advice, other advice,</li><li>Make sure you have all facts and if possible, proof,</li><li>Try to mobilize an appropriate organization to take up the cause — eg Professional Body.</li><li>Plan the method of disclosure — for max effort with minimum potential damage.</li><li>Whistleblow anonymously if possible.</li><li>Be prepared to be ignored, even victimized.</li><li>Remember — you are the one behaving ethically.</li></ul><h3>What does whistleblowing have to do with ethics?</h3><p>A whistleblower once testified in a California court about how his boss had regularly ordered him to discard some of the company’s toxic waste into a local storm drain rather than dispose of it properly. Why, the judge wanted to know, had the man finally decided to step forward after having participated in this illegal dumping for years. “Well,” the man explained, “I was fishing with my grandson, and it suddenly occurred to me that the waste I was dumping was going to pollute the water so that he might never be able to go fishing with his grandson.”</p><p>Whistleblowing has to do with ethics because it represents a person’s understanding, at a deep level, that an action his or her organization is taking is harmful — that it interferes with people’s rights or is unfair or detracts from the common good. Whistleblowing also calls upon the virtues, especially courage, as standing up for principles can be a punishing experience. Even though laws are supposed to protect whistleblowers from retaliation, people who feel threatened by the revelations can ostracize the whistleblower, marginalizing or even forcing him or her out of public office. On the other hand, there have been occasions when the role of the whistleblower has actually catapulted people into higher office and has earned the respect of constituents.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b79fc4c2479c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sleeping Operating System]]></title>
            <link>https://champikamendis-cm.medium.com/sleeping-operating-system-dcf81b0fdf5?source=rss-bd3b26b2e8da------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcf81b0fdf5</guid>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Champika Mendis]]></dc:creator>
            <pubDate>Sun, 16 Jun 2019 17:07:43 GMT</pubDate>
            <atom:updated>2019-06-16T17:07:43.987Z</atom:updated>
            <content:encoded><![CDATA[<p>Build Your Own Operating System Today</p><p><strong>Introduction</strong><br>This is a operating system which can read your machine’s hardware information display on the Screen.</p><p><strong>Technology</strong><br>The SleepingOS kernel is written in 16-bit x86 real mode assembly language. I used Kali Linux to implement my OS. I think Linux is better to do this job without many problems. And I used NASM and QEMU applications for this purpose.</p><p><strong>Requirements</strong><br>Open terminal and should be install following are essential for creating os.<br><strong>Install NASM</strong> — to converts assembly language into raw machine code executable files.<br><em>sudo bash apt-get install nasm</em><br><strong>Install QEMU</strong> — This is an emulator and this is to run .flp/.iso file that we needed.<br><em>sudo bash apt-get install qemu-system-x86</em></p><p><strong>Install mkisofs </strong>— This is to generate a CD_ROM ISO image of SleepingOS<br><em>sudo bash apt-get install cdda2wav cdrecord mkisofs</em></p><h3>OR</h3><p>Get all the tools you need to follow this guide by entering this in a terminal window:<br><em>sudo apt-get install build-essential qemu nasm</em></p><h3>Structure of the OS</h3><p><strong>source/</strong>.. -contains the entire OS source code</p><p><strong>source/bootload/..</strong> — source to generate bootload.bin, which is added to the disk image when building</p><p><strong>source/kernel.asm </strong>— The core kernel source file, which pulls in other source files and it includes source code which needs to display the hardware information.</p><p><strong>programs/..</strong> — Source code for programs added to the disk image</p><h3>BOOTING METHODOLOGY</h3><p><strong>Disk images</strong></p><p><strong>SleepingOS.flp</strong> — Floppy disk image containing SleepingOS and programs</p><p><strong>SleepingOS.iso </strong>— CD ISO image built using the floppy disk image</p><p>So, these files are virtual disk images that you can write to real floppy disks or CD-Rs, or run in a PC emulator as described in a moment.In Linux, you can <em>run build-linux.sh </em>to make cd iso image.</p><p><strong>build-linux.sh</strong></p><p>This script assembles the SleepingOS bootloader, kernel and programs<br> with NASM, and then creates floppy and CD images (on Linux).Only the root user can mount the floppy disk image as a virtual drive (loopback mounting), in order to copy across the files.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcf81b0fdf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>