<?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 André Farias on Medium]]></title>
        <description><![CDATA[Stories by André Farias on Medium]]></description>
        <link>https://medium.com/@andrerfarias?source=rss-b82eaa80e4b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*L2f_OI7V5YUhBJ9KfbKc3Q.png</url>
            <title>Stories by André Farias on Medium</title>
            <link>https://medium.com/@andrerfarias?source=rss-b82eaa80e4b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:05:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrerfarias/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building a multi-cloud notification service— Part 1: Concepts and Architecture]]></title>
            <link>https://medium.com/reactivehub/building-a-multi-cloud-notification-service-part-1-concepts-and-architecture-71c59c03af94?source=rss-b82eaa80e4b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/71c59c03af94</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[event-driven-systems]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[André Farias]]></dc:creator>
            <pubDate>Fri, 07 Sep 2018 14:39:13 GMT</pubDate>
            <atom:updated>2018-09-07T14:39:13.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zc8CA7BfPHHZdGLc" /></figure><p>Engaging your customer is a must have if you wish your product to succeed, and notifications services can help you with that. In this two-part series, we are going to design and implement a multi-cloud notification service. However, you should be familiar with the <a href="https://medium.com/reactivehub/event-driven-microservices-a-path-to-a-multi-cloud-environment-7ba6744dd84b">event-driven microservices pattern.</a></p><h3>Concepts</h3><p>Before start building any software architecture we must understand the real problem that we wish to solve and what is our primary objective; otherwise, we are at a high risk to build unnecessary features and waste a considerable amount of time.</p><p>Our primary objective in this project is keeping a relationship with the customer. We need to send messages asking him to execute an action within our platform and keep track of the notification status.</p><p>The actions executed when we send a notification are:</p><ol><li>Save the data in a NoSQL real-time database for in-app notifications</li><li>Save the data in a SQL database for analytics</li><li>Send an e-mail to the customer</li></ol><h3>Multi-cloud architecture</h3><p>Adopting a multi-cloud environment means being ready to make use of the best available technologies. For example, Google has an excellent <strong>real-time database</strong> product called <a href="https://cloud.google.com/firestore/">Firestore</a>; <strong>Amazon </strong>did an excellent job with the <a href="https://aws.amazon.com/pt/rds/">AWS RDS database</a>; then why would we choose just one cloud service provider?</p><p>That said, to achieve our objectives we are implementing the following technologies:</p><ol><li><a href="https://cloud.google.com/firestore/"><strong>Google Cloud Firestore</strong></a> — Real-time database so we can listen and show notifications as soon as they’re available.</li><li><a href="https://aws.amazon.com/pt/rds/"><strong>Amazon RDS </strong></a>— Relational database for data analytics.</li><li><a href="https://cloud.google.com/bigquery/"><strong>Google BigQuery (Optional)</strong></a> — Google’s analytics database, you can skip this step if you please.</li><li><a href="https://mailchimp.com/"><strong>MailChimp </strong></a>— Mailing service delivery, you can create a<a href="https://login.mailchimp.com/signup/"> <strong>free account here</strong></a><strong>. </strong>If you don’t want to, deploy your mailing service and connect it through an HTTP API (in the next article we are providing you with the code so that you can publish it with<strong> </strong><a href="https://cloud.google.com/functions/"><strong>Google Cloud Functions</strong></a>, A<a href="https://aws.amazon.com/pt/lambda/"><strong>WS Lambda</strong></a> or any other hosting service).</li><li><strong>HTTP API </strong>for integrating all of these services in a single call.</li></ol><h3>Next Steps</h3><p>In the next article, we are going to implement our notification service and connect all of these cloud providers in a single API call. In the meantime take a break to learn more about each one of the services we are going to use.</p><h3>Bonus</h3><p>If you wish to finish it before the next article launches on Medium, <a href="http://reactivehub.io/tech-insights">subscribe to our tech insights newsletter</a><strong>,</strong> get access to our articles before it goes public, and receive a $10 referral bonus on <a href="https://www.digitalocean.com/"><strong>Digital Ocean</strong> </a>services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71c59c03af94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reactivehub/building-a-multi-cloud-notification-service-part-1-concepts-and-architecture-71c59c03af94">Building a multi-cloud notification service— Part 1: Concepts and Architecture</a> was originally published in <a href="https://medium.com/reactivehub">reactivehub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Event-driven microservices: a path to a multi-cloud environment]]></title>
            <link>https://medium.com/reactivehub/event-driven-microservices-a-path-to-a-multi-cloud-environment-7ba6744dd84b?source=rss-b82eaa80e4b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ba6744dd84b</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[event-driven-architecture]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[André Farias]]></dc:creator>
            <pubDate>Fri, 24 Aug 2018 00:56:32 GMT</pubDate>
            <atom:updated>2018-08-30T00:54:30.512Z</atom:updated>
            <content:encoded><![CDATA[<p>Modern web applications architecture relies on building APIs and microservices in <a href="https://aws.amazon.com/pt/what-is-cloud-computing/">cloud infrastructures</a>. This architecture is the primary standard adopted by the majority of software developers and architects, it also defines the behavior of an application and its entire data flow, but in spite of being effective they end up by bumping into some of the most significant needs of successful apps, <strong>scalability</strong>.</p><h4>The Synchronous Gap</h4><p>Most applications that use microservices and APIs as their primary data flow run the execution of their processes synchronously.</p><p>The main issue with synchronous applications is the increase of response time which causes a negative impact in user experience and an increase in the costs with cloud infrastructure, mainly if you’ve adopted a <a href="https://aws.amazon.com/lambda/serverless-architectures-learn-more/">serverless architecture</a>.</p><p>Here is an example of a synchronous API receiving a request for adding a new customer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*sSTb17YzL2WyTs6rXjydzw.png" /><figcaption>Synchronous service example.</figcaption></figure><p>In this example, upon receiving a request for adding a new customer, the service executes the following actions in sequence:</p><ol><li>Validate the payload data;</li><li>Insert the client in the application core database;</li><li>Insert the client into the analytics database;</li><li>Send a welcome email;</li></ol><p>This strategy works, but in the long run with increasing application popularity, you have to deal with the following issues:</p><ol><li>Negative impact on user experience with increased execution time due to a large number of requests.</li><li>Increase in the cloud infrastructure costs due to the allocation of more processing resources.</li><li>The high complexity of code development and maintenance as the development team grows.</li></ol><p>To create high-performance applications we can adopt the asynchronous development pattern.</p><h4>Event-driven microservices to the rescue</h4><p>Event-driven microservices are asynchronous by definition when adopting an event-oriented architecture, the developer should think about which triggers should perform actions.</p><p>A trigger can be a page view; an insert into a database or even an API call.</p><p>Actions are asynchronous and started with a trigger that can be anything from saving information in a database entity to calling another API. They could also run new triggers, this way event-driven microservices allows the creation of a <a href="https://en.wikipedia.org/wiki/Reactive_programming">reactive application</a>.</p><p>In the previous example, we had an API request to create a new customer, consider this as an event trigger.</p><p>Upon receiving the <strong>“New Customer”</strong> trigger, the service executes the following actions:</p><ol><li>Validate the payload data;</li><li>Insert the customer into the application’s core database;</li><li>Emit a new asynchronous event called <strong>“user-created”</strong> then return a response to the client;</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*R9Mfvhc7J9iu_gZtUwGNMg.png" /></figure><p>In this model, we isolate the minimum necessary operations for creating a new customer; any other actions are processed asynchronously in a new event.</p><p>By taking these actions, we improved the application response time and optimized the customer experience.</p><p>The infrastructure costs can also be controlled by manually setting the scale of the <strong>“user-created” </strong>event with cloud services like <a href="https://cloud.google.com/pubsub/docs/overview"><strong>Google Cloud Pub/Sub</strong></a> or <a href="https://aws.amazon.com/pt/sqs/"><strong>Amazon SQS</strong></a><strong>.</strong></p><h4>Multi-cloud environment</h4><p>If you want to keep your analytics database on <a href="https://cloud.google.com/">Google Cloud Platform</a> your application database in <a href="https://aws.amazon.com/pt/rds/">Amazon RDS</a> and your APIs on <a href="http://digitalocean.com/">Digital Ocean</a> servers, an <a href="https://reactivehub.io/event-microservices">event-driven architecture</a> is the best way to <a href="https://reactivehub.io/integrations">integrate </a>all of these platforms.</p><p>Adopting a <a href="https://www.forbes.com/sites/forbestechcouncil/2017/12/21/a-closer-look-at-the-multi-cloud-trend/#6bd2c819547b">multi-cloud environment</a> means being ready to make use of the best available technologies, but you should be aware of the following:</p><ol><li><em>Disparate tools, consoles, and Technologies: </em>Keeping track of all your services statuses may be painful.</li><li><em>Expertise requirements:</em> Each cloud platform has its technology and patterns, studying each one of these technologies thoroughly before implementing is mandatory.</li><li><em>Operational Costs:</em> The charging method of each cloud platform can also vary, you should get a deep dive in understanding all the possibilities of charging.</li></ol><p>Auditing, controlling and ensuring the delivery of all events between different platforms can be a painful process and consume a considerable amount of development time. To gain speed and security in this development process, take a look at the <a href="https://reactivehub.io/">Reactivehub</a> development tools.</p><h4>Conclusion</h4><p>Event-driven microservices bring a new way of thinking about application architecture; they are incredibly configurable; fits in any product that should be scalable from the beginning and are ready for the new multi-cloud demands of modern high-performance applications.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ba6744dd84b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/reactivehub/event-driven-microservices-a-path-to-a-multi-cloud-environment-7ba6744dd84b">Event-driven microservices: a path to a multi-cloud environment</a> was originally published in <a href="https://medium.com/reactivehub">reactivehub</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>