<?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 Sandeep Jandhyala on Medium]]></title>
        <description><![CDATA[Stories by Sandeep Jandhyala on Medium]]></description>
        <link>https://medium.com/@sandeepjandhyala?source=rss-866c0b7bb689------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Sandeep Jandhyala on Medium</title>
            <link>https://medium.com/@sandeepjandhyala?source=rss-866c0b7bb689------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:04:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sandeepjandhyala/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[When To Use GraphQL and How It Compares to REST]]></title>
            <link>https://medium.com/capital-one-tech/when-to-use-graphql-and-how-it-compares-to-rest-632afc621160?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/632afc621160</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[aws-appsync]]></category>
            <category><![CDATA[rest]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Tue, 04 May 2021 15:15:27 GMT</pubDate>
            <atom:updated>2021-05-04T15:15:27.801Z</atom:updated>
            <content:encoded><![CDATA[<h4>GraphQL as your new BFF (backend for frontend), AWS Appsync, and Apollo Server</h4><figure><img alt="GraphQL vs REST, when to use GraphQL" src="https://cdn-images-1.medium.com/max/1024/1*RPwzXfger1AEYO4EmcXouA.png" /></figure><p>The last decade has seen many organizations adopt microservices to power their websites, mobile apps, and desktop applications. Perhaps you’ve seen some of <a href="https://medium.com/capital-one-tech/search?q=microservices">Capital One’s articles on our microservices journey</a>. With all the business logic shifted to the server side in this architectural style, there have been some notable changes and trends, including the philosophy of building APIs once and then reusing them across channels.</p><h3>Limitations and challenges of directly reusing Web APIs across channels</h3><p>Reusing the same APIs across multiple channels such as web, mobile, desktop, IoT, etc. can cause some challenges.</p><p>In the scenario shown below, clients are tightly coupled with the backend microservices. A lot of the time gets wasted trying to figure out which API to call, integrating to all the backend services, and then coordinating with multiple teams. Also, this increases the complexity on the client side and increases the potential for errors and downtime.</p><figure><img alt="Direct client to microservice coupling" src="https://cdn-images-1.medium.com/max/918/0*f90G6oEXH8HfGJ_a" /><figcaption><a href="https://docs.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/direct-client-to-microservice-communication-versus-the-api-gateway-pattern"><em>“Direct Client-To-Microservice communication Architecture”</em></a><em> from Microsoft .NET Docs is licensed under </em><a href="https://creativecommons.org/licenses/by/4.0/"><em>CC BY 4.0</em></a><em>.</em></figcaption></figure><p>Moreso, for channels such as mobile, integrating APIs that were built for the web can cause network bandwidth bottlenecks and memory limitations. This problem is also called <a href="https://graphql.org/"><em>overfetching</em></a> — i.e fetching a lot more information than what is actually needed for a client.</p><p>Additionally, these clients can also experience a second problem due to the distributed nature of the microservice environment where the data that a user needs to see on a single screen can be scattered across multiple microservices. As a result, the mobile app has to integrate with multiple backends and make multiple network calls to fetch the data needed to load a screen. Making this worse, these calls need to be executed sequentially. This can impact performance and slow down screen load time.</p><p>The example below shows multiple REST calls that need to be made sequentially to load a specific user’s followers and their feed from an app.</p><figure><img alt="Multiple sequential calls with REST" src="https://cdn-images-1.medium.com/max/1024/0*SDdkNBJi38BCJ2Xo" /><figcaption><em>Sequential calls from client apps to backend Microservices from </em><a href="https://www.howtographql.com/basics/1-graphql-is-the-better-rest/"><em>GraphQL is the better REST</em></a><strong><em> </em></strong><em>Copyright Graphcool. Licensed under the </em><a href="https://github.com/howtographql/howtographql/blob/master/LICENSE.txt"><em>MIT license</em></a><em>.</em></figcaption></figure><h3>Overcoming challenges with Experience APIs and BFFs</h3><p>To overcome all of the above challenges, some design patterns like <a href="https://blogs.mulesoft.com/api-integration/strategy/experience-api-ownership/">Experience APIs</a> or <a href="https://docs.microsoft.com/en-us/azure/architecture/patterns/backends-for-frontends">Backends For Frontend (BFF)</a> were adopted.</p><p>An API experience layer sits on top of the existing APIs and allows each UI team to optimize the API experience for their specific app or device. A Backend for Frontend (BFF), as the name suggests, is a separate backend for each UI interface which gets optimized for that front end, without worrying about affecting other frontend experiences.</p><p>This looks something like the below diagram. The single customized endpoint on the BFF aggregates data from multiple microservices, filters what is needed for the mobile channel, and then returns only the necessary data. This not only reduces the network back and forth between the client and backend, but also provides abstraction.</p><figure><img alt="Multiple Backends for FrontEnd (BFFs) supporting different clients" src="https://cdn-images-1.medium.com/max/1024/0*gdZQZyb-U6yoV463" /><figcaption>Multiple Backends for FrontEnd supporting different clients</figcaption></figure><p>Now imagine multiple of these BFFs or Experience APIs supporting a single mobile app, including different variations of each that would be needed to maintain multiple apps. It’s a lot, right? A lot of maintenance goes into tweaking and optimizing these for each client, handling fallbacks, circuit breaker implementations, etc. Also, these APIs are subject to constant change if the views on the frontend are altered.</p><p>This can also lead to code duplication across the various BFFs. For example, a mobile team might not even be aware that the web team built another BFF for a similar flow. Or, let’s say there is a plan in your organization to integrate your APIs with smart devices like Alexa, or to eventually build an app for an Apple or Samsung Watch. Are you going to build new Experience APIs for them again? Hmm, I wonder if there is a better way to handle multiple clients…</p><h3>A new alternative — using GraphQL to improve architectures</h3><h4>What is GraphQL?</h4><p><a href="https://graphql.org/">GraphQL</a> is a query language for APIs and a runtime for executing those queries. It was developed at Facebook in 2012 and made public in 2015. GraphQL has been considered to be an alternative to REST as it was designed to make API development faster and more flexible to handle changing client requirements.</p><figure><img alt="GraphQL supporting various clients" src="https://cdn-images-1.medium.com/max/1024/0*RkohQAKbCAMxhH4g" /><figcaption>GraphQL supporting multiple clients</figcaption></figure><h4>What are the benefits of using GraphQL?</h4><p>GraphQL provides the following benefits:</p><p><strong>1. Flexibility to Clients</strong> — With GraphQL, clients such as mobile can exactly query for information that they need, and the server will respond with only that data. <em>I.E clients dictate what data the server needs to respond with as opposed to the server, thereby avoiding the overfetching problem with REST.</em> Imagine how useful this is for mobile, especially when there is a slow network.</p><p>With GraphQL, clients make a single API call to fetch the information they need. This reduces the integration overhead and improves network performance. No more client-side joins or error handling.</p><figure><img alt="Querying with GraphQL : Ask specifically for what you want" src="https://cdn-images-1.medium.com/max/1024/0*iPgwymibXsOzJnu4" /><figcaption><em>“GraphQL” from </em><a href="https://graphql.org/"><em>https://graphql.org/</em></a><em> is licensed under CC BY 3.0.</em></figcaption></figure><p><strong>2. Flexibility to API Developers</strong> — GraphQL saves the effort needed by API developers to build custom endpoints in orchestration layers or experience APIs for all possible query combinations since you can construct different page views on the client using the same endpoint and schema. Also, we can reuse this aggregation logic to support diverse clients that have varied querying needs instead of building separate BFFs per client. This simplifies the orchestration layer that one needs to maintain.</p><p><strong>3. Versioning</strong> — With GraphQL, it’s easier to know which fields in the API are being used by what clients and which ones are not. API developers can more confidently make changes to the existing APIs with this information. This means you don’t need to implement a new version when removing certain unused fields or adding new fields or types. The API can keep growing and clients need not worry as much about upgrading to the latest version. This is a stark difference from REST.</p><p><strong>4. Documentation &amp; Schema</strong> — GraphQL uses a strongly typed <a href="https://graphql.org/learn/schema/">schema</a> against which queries are validated. Through GraphQL <a href="https://graphql.org/learn/introspection/">introspection</a>, one can request the schema and know what queries are supported; this can then be used for automatic generation of documentation. Also, tools like <a href="https://www.gatsbyjs.com/docs/how-to/querying-data/running-queries-with-graphiql/">GraphiQL</a> can help you visually explore the graph of data and help one to author and submit a GraphQL query to the server. In REST API’s this documentation has to be explicitly created using Swagger or some other mechanism.</p><figure><img alt="GraphQL query response" src="https://cdn-images-1.medium.com/max/1024/0*5bZ4u5ktKGnNIcdy" /><figcaption><a href="https://www.howtographql.com/basics/1-graphql-is-the-better-rest/"><em>GraphQL query.</em></a></figcaption></figure><p>You can also specify which fields are nullable in the schema. <em>I.E if there is an error fetching certain fields, the other fields can still be returned in the response.</em></p><h3>GraphQL Implementation</h3><p>GraphQL has a rich language support and there are several <a href="https://graphql.org/code/">GraphQL Server</a> implementations available.</p><h4>Apollo Server and GraphQL</h4><p><a href="https://www.apollographql.com/docs/apollo-server/">Apollo</a> Server is a popular open source implementation of the GraphQL spec. Using the Apollo platform you can build, query, and manage your data graph by connecting to data sources or external APIs.</p><figure><img alt="Apollo server for GraphQL" src="https://cdn-images-1.medium.com/max/467/0*OAuyjvUi2fABuX2M" /><figcaption><a href="https://www.apollographql.com/docs/intro/platform/"><em>Apollo Server</em></a><em> from the Apollo Server documentation. Copyright Meteor Development Group, Inc. Licensed under the </em><a href="https://github.com/apollographql/apollo/blob/main/LICENSE"><em>MIT license</em></a><em>.</em></figcaption></figure><p>The platform consists of a JavaScript GraphQL server where you can define your schema and resolver functions. It also consists of a JavaScript Apollo client component that can be used with React, Angular, or Vue frameworks. There is also support for iOS and Android client components.</p><p>The Apollo client has features that can directly update the UI components when query results arrive or change and declaratively define the queries from the UI components. <a href="https://blog.bitsrc.io/should-i-use-apollo-for-graphql-936129de72fe">Here</a> is a good article on why to use Apollo.</p><h4>AWS AppSync and GraphQL</h4><p>In 2019 AWS released <a href="https://aws.amazon.com/appsync/">AWS AppSync</a> which is a fully managed service to build GraphQL APIs. It can combine data from multiple data sources, APIs, and Lambda functions, integrating with caches for faster performance. AppSync manages auto scaling the GraphQL execution engine based on the load. It also has integration with Cloudwatch.</p><figure><img alt="AWS AppSync : Managed GraphQL AWS service" src="https://cdn-images-1.medium.com/max/1024/0*AFJruo6kGeBORKAq" /><figcaption><em>AppSync</em><a href="https://aws.amazon.com/appsync/"><em> </em></a><em>Resolvers calling backend Microservices as taken from the </em><a href="https://aws.amazon.com/appsync/"><em>AWS AppSync documentation</em></a></figcaption></figure><p>You can have Lambda’s as your resolver functions and segregate ownership of these functions to the teams that best know how to fetch the data. These functions can even exist in multiple AWS accounts.</p><h3>Query Execution in GraphQL</h3><p>The execution of the client supplied query happens on the GraphQL server. The server parses the query, validates it against the schema, and finally passes the execution to resolver functions.</p><p>Let’s take a look at some of the challenges involved with query execution.</p><h4>Challenges to Query Execution in GraphQL</h4><p><strong><em>1. Safety controls to prevent expensive queries</em></strong></p><p>GraphQL simplifies things for the clients by giving them the control to query for exactly what they want. However, this means the clients can potentially ask for something that is resource intensive by making a lot of database calls on the server.</p><p>This is because GraphQL executes a resolver function for each field in the GraphQL schema. <a href="https://www.howtographql.com/advanced/4-security/">Techniques</a> such as setting timeout on queries or analyzing maximum query depth before executing the query or analyzing query complexity beforehand can be used.</p><p>Another subtle difference to note with GraphQL is that throttling based on the number of API requests is not a good factor as a single request can result in multiple queries.</p><p><strong><em>2. The resolver functions, batching and performance</em></strong></p><p>Each field in a GraphQL Schema maps to a <strong>resolver</strong> function which has the business logic for fetching the data. The resolvers can fetch the data by calling another API or from the database or cache etc.GraphQL also has something called default resolvers, so you don’t have to specify a resolver for each field. If there is no resolver for a field specified, GraphQL will look for that field name in the parent resolver.</p><p>When compared to REST, the performance costs of using GraphQL aren’t as obvious. Even though the clients fetch information using a single API call with GraphQL, API developers still need to be watchful about the possibility of <em>overfetching</em> shifting to the server side by making a lot of backend database calls.</p><p>Knowing the intricacies on how to structure your resolvers and where to fetch the data from (parent vs child) is key to performance. Here is an interesting <a href="https://medium.com/paypal-engineering/graphql-resolvers-best-practices-cd36fdbcef55">blog</a> that explains how query parsing works and few best practices around GraphQL resolvers.</p><h3>Conclusion</h3><p>There are many comparisons of GraphQL vs REST and discussions about GraphQL replacing REST. REST is well proven and GraphQL is fairly new and evolving, its adoption is rapidly growing in many organizations. There is somewhat of a learning curve with GraphQL, like with any other new technology. GraphQL brings along a lot of benefits and some challenges; the solutions to deal with those challenges are effectively being built.</p><p>In my view, GraphQL provides a ton of value in scenarios where the clients need flexibility to fetch minimal data in a single shot like Mobile, or where the client needs are changing rapidly and you want to minimize the overhead on the server side. It can also be a huge benefit for building organizational API’s on top of REST where you need to support a diverse set of clients.</p><p>However, if you don’t have such needs and have simple APIs with static, straightforward querying requirements, GraphQL can add unnecessary complexity compared to REST.</p><p><em>Geometric header photo created by </em><a href="https://www.freepik.com/rawpixel-com"><em>rawpixel.com</em></a><em> on </em><a href="http://www.freepik.com/"><em>www.freepik.com</em></a></p><p><em>DISCLOSURE STATEMENT: © 2021 Capital One. Opinions are those of the individual author. Unless noted otherwise in this post, Capital One is not affiliated with, nor endorsed by, any of the companies mentioned. All trademarks and other intellectual property used or displayed are property of their respective owners.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=632afc621160" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-one-tech/when-to-use-graphql-and-how-it-compares-to-rest-632afc621160">When To Use GraphQL and How It Compares to REST</a> was originally published in <a href="https://medium.com/capital-one-tech">Capital One Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Empowering your introverted software engineer]]></title>
            <link>https://medium.com/swlh/empowering-your-introverted-software-engineer-cbfae44adb10?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbfae44adb10</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[introvert]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Fri, 05 Feb 2021 03:29:46 GMT</pubDate>
            <atom:updated>2021-02-09T02:25:15.922Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Empowering your introverted software engineer</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/0*2mQWbEnfpggQesmT" /></figure><p>In a world where the one who is most vocal gets noticed and recognized, and the one who is quiet gets coached to learn and be someone else, talented introverts struggle to prosper . Introvert software engineers typically are not social in the corporate networking groups, not hanging out in happy hours, not making connections over lunch or coffee, not presenting their ideas in front of a large audience. So, it’s very likely that the leadership group who directly doesn’t supervise them, wouldn’t even know them or the value they bring to the table compared to the extroverts.</p><p>The common feedback provided to introvert engineers is to be more vocal, ask questions, challenge someone, go in front of a large crowd and showcase a demo, don’t have any inhibitions, communicate often loud and clear. This is like telling introverts to be someone else. Imagine if you are an extrovert and someone told you not to connect with people, practice talking less. Feels like a punishment eh? Introverts would feel the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*s4TVZa46Sz2StTnN.png" /></figure><p>So how can you empower introverts and enable them to prosper without asking them to be a different person or judging them for the wrong reasons? What should you do to identify the real talents and build diverse teams? Let’s take a look at few scenarios</p><ul><li><strong>In team meetings :</strong> It is natural in the meetings for extroverts to do all the talk, gossiping and likely also step over the introverts view points. Here are some tips on how to handle this scenario. Knowing who the quiet ones are in the meeting and explicitly asking them for their inputs by giving them space and time to talk will create a comfort zone for the introverts. You can continue to seek inputs offline by making it clear that they can send you an email with their thoughts. Also, you can ask everyone to come prepared to the meeting by entering their topics or talking points in a document before hand. That way, when you go through the document that has the list of topics during the meeting, it would naturally provide an opportunity to everyone who entered topics to speak and introverts are not left out.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fVpyXkMVCkX-ORrv" /></figure><ul><li><strong>In a group celebration or a fun event</strong> : Recognition is an excellent form of motivating and empowering someone to do great things. Very often recognitions take the shape of celebrating as a group. While extroverts love these activities and can spend hours and hours chatting and networking with strangers, these are the events that would make your introvert engineers some what uncomfortable. A close group team lunch that is for a shorter duration would make introverts feel more comfortable. Similarly, fun team activities that are quieter and that require to use ones brain power while working with smaller groups , such as escape rooms would engage your introvert engineers the best . Also, recognizing ones work individually in a personalized way is another great option.</li><li><strong>Building partnerships with other groups</strong>: Initiating conversations with strangers and building partnerships with new groups can get very uncomfortable for introverts. The upfront kickoff’s, probing and asking questions, meet and greets are better suited for extroverts. Pairing talented introverts with extroverts is a great way to engage with external groups. Also, introverts typically like to observe , digest the content and then make a point. They may even take time to do follow up’s via emails or have working sessions. So don’t judge the engagement and influence with other groups only on the basis of the upfront meeting conversations where extroverts are most visible and vocal. There is a lot of influence that would happen offline, where introverts would be playing a crucial role; pay attention to that as well.</li><li><strong>Suitable Office space</strong> : With open office spaces being a trend these days, one tends to ignore the philosophy behind creating these layouts. The idea was to create a more collaborative environment with easy access to your team mates, supervisors, ultimately increasing team productivity. But, introverts like to work in quiet places, where in they are by themselves. That way, they can focus and give their best; it will also help them recharge . They don’t want to be distracted with someone suddenly stopping by their desk or random chit chats or privacy intrusion. Creating flexibility for introverts to work from quiet little places in your office or remotely will empower your introvert engineers and boost overall productivity .</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*LMFRI2VRNG_y90GC" /></figure><ul><li><strong>Showcasing broader influence </strong>: Introverts might find it uncomfortable to go in front of a large audience and present on a topic. You can encourage your introverted engineers to seek alternate forms of influence and showcase their skills such as documenting thoughts or designs and sharing broadly, creating some training materials or writing a blog or creating lab exercises etc .</li><li><strong>Regular 1–1’s or small focus group sessions : </strong>While having regular 1–1’s with everyone on your team is important; for introverts these meetings mean much more . They open up more and tend to go deep in these settings. It will give them an opportunity to speak for their efforts which are generally not flashing visible to you.</li></ul><p>Remember, everyone on your team is different, they bring different value to the table; just like the fingers on your hand, each serve a different purpose. Identify what that value add is and encourage your introvert engineers to leverage their strengths and grow, rather than asking them to be someone else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbfae44adb10" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/empowering-your-introverted-software-engineer-cbfae44adb10">Empowering your introverted software engineer</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guardrails for AWS Event-Driven Serverless Architectures]]></title>
            <link>https://medium.com/capital-one-tech/guardrails-for-aws-event-driven-serverless-architectures-f9bc12ad689f?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9bc12ad689f</guid>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[event-driven-architecture]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 16:17:13 GMT</pubDate>
            <atom:updated>2020-11-18T16:17:13.167Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>9 best practices for efficient processing &amp; cost optimization with AWS SNS, SQS, EventBridge, &amp; Lambdas</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*feZoGC1JaZ4QanXo.png" /></figure><p>Event-driven architecture is a powerful architecture style that promotes de-coupling between systems, better fault isolation, independent scaling, and independent development and releases. Serverless architecture is an architecture style that provides the benefit of not having to worry about server provisioning or maintenance and has auto scaling, high fault tolerance, and is pay per use. AWS brings these two architecture styles together with the combination of serverless compute <a href="https://aws.amazon.com/lambda/">Lambda</a> and the messaging solutions <em>AWS Simple Queue Service (</em><a href="https://aws.amazon.com/sqs/"><em>SQS</em></a><em>), AWS Simple Notification Service (</em><a href="https://aws.amazon.com/sns/?whats-new-cards.sort-by=item.additionalFields.postDateTime&amp;whats-new-cards.sort-order=desc"><em>SNS</em></a><em>), and AWS </em><a href="https://aws.amazon.com/eventbridge/"><em>EventBridge</em></a><em>.</em></p><p>In this article we will go over some challenges engineers face when using event-driven serverless architectures at scale, and how to deal with them using some best practices for the AWS services above. Let’s jump right into what those best practices are.</p><h3>1. Reduce the Pressure on Your Event Consumers and their Dependencies</h3><p>In the event-driven serverless architecture style, one of the guardrails is to make sure there is smooth processing of the events by the consumers while keeping costs under control.</p><h4><strong>Factor in the time taken by consumers to process each event</strong></h4><p>Let’s say you have a Lambda function that is a subscriber to a SNS topic and the Lambda function takes a considerable amount of time to process every event. <strong><em>Example:</em></strong><em> It needs to make an external API call that is terribly slow in responding to requests.</em></p><p>In this scenario, if you use SNS to broadcast the messages to Lambda and there is a burst of messages this can lead to several invocations of your Lambda function running at the same time. This would be less cost efficient and can potentially hit <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-scaling.html">limits</a> on max concurrent Lambda invocations. Also, since those limits are at an account level, this could possibly cause capacity issues for other applications on the same account.</p><p>The suitable approach here is to throttle the traffic up-front. You can use SQS as a destination to SNS, wherein SQS queues can be used to hold the messages until the consumers are ready to process them as shown in the diagram below.</p><figure><img alt="diagram with green and pink icons and black arrows" src="https://cdn-images-1.medium.com/max/664/0*rIl9GN8SDk9PPlVI" /><figcaption><a href="https://event-driven-architecture.workshop.aws/4-sns/2-filtering/message-filtering.html">SNS distributes events to SQS</a></figcaption></figure><h4>Consider the scaling limitations of your event consumers as well as their dependencies</h4><p>This is a slightly different scenario than above. Let’s say you have a Lambda function that is going to consume messages from an SNS topic and perform some operations on an <a href="https://aws.amazon.com/rds/">AWS RDS</a> database or call an API that doesn’t scale well. If there is a burst of messages to the SNS topic, even though Lambda can scale up to the concurrency limits set, the downstream dependency may not be able to handle it. <strong><em>Example:</em></strong><em> RDS max connection limit could be reached or the downstream API that doesn’t scale well might crash. With Lambda retries it may self heal, or we might make it worse, resulting in the messages going to DLQ (that is, if you have configured a DLQ for your Lambda).</em></p><p>Similar to above, leverage SQS as a destination for SNS and then have your Lambda function consume it when it is ready.</p><h3>2. Use the SNS Message Filtering Feature</h3><p>This event-driven serverless best practice can be leveraged to filter the noise upfront before it hits the event consumers, thereby saving costs.</p><p>When subscribing to SNS topics, consumers can specify additional filter criteria in their subscription <a href="https://docs.aws.amazon.com/sns/latest/dg/sns-subscription-filter-policies.html">filter policy</a> to say, “<em>Only send me messages that meet certain criteria.”</em> Filter policy is a JSON object that contains the filter criteria. The messages published to the SNS topic consist of a Message Attributes element that can host additional metadata about the message. Publishers can populate this element and SNS takes care of filtering the messages per the subscription filter policy, only delivering the messages that match the right criteria to the consumers. This way, consumers don’t need to be bothered by every single message, thereby saving costs and processing.</p><p>As an example, in the diagram shown above messages are being published to the Orders SNS topic and each of the SQS queues subscribed to that topic have a filter policy listed. SNS uses this filter policy to filter and route the matching messages to the respective SQS queues.<strong> <em>Note:</em></strong><em> This is indicated using different color coding in the image above. Messages colored in Red are sent to Orders Queue and ones in Green are sent to Orders-EU Queue.</em></p><p>Here is an example of what a filter policy could look like:</p><figure><img alt="black screen with lines of orange and green code" src="https://cdn-images-1.medium.com/max/933/0*f_J9p_YwW5b68Rxp" /><figcaption><a href="https://event-driven-architecture.workshop.aws/4-sns/3-advanced-filtering/adv-message-filtering.html">Filter Policy</a></figcaption></figure><p>Use a filter policy only when it makes logical sense — i.e. the subscribers are interested in similar types of events and have similar access permission requirements to that topic. Don’t use it to push unrelated events into a single topic, that would complicate things.</p><h3>3. Consider Throttling Your Lambda Functions That Are Consuming Events</h3><p>Inline with the best practices on cost optimization and guarding your event consumer, this technique is extremely useful in an enterprise setting where there are multiple serverless components, possibly owned by different teams under the same AWS account.</p><p>Lambda concurrency limit is at an account level, that means it is shared by all the Lambda functions under that AWS account. However, you can also have a function level concurrency limit configured in advance called <a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html"><em>reserved concurrency</em></a>. It can ensure other functions don’t take up your reserved quota. It can also throttle your Lambda function invocations when there is a burst of messages that your function is subscribed to process. Keep in mind that your function’s concurrent invocations will not go beyond this setting even if there is room in the unserved concurrency.</p><p>This can help reduce load on downstream dependencies like a database or another API and can help keep your costs under control. Additional requests to your function beyond the limits assigned will fail with a throttling error. Refer to point 9 below on retries for different types of errors.</p><figure><img alt="screenshot of concurrency configuration screen" src="https://cdn-images-1.medium.com/max/1024/0*4570nMUYOBTgqJ6W" /><figcaption><a href="https://aws.amazon.com/blogs/aws/new-provisioned-concurrency-for-lambda-functions/">Reserved Concurrency</a></figcaption></figure><h3>4. Consider Using the Long Polling Feature in SQS</h3><p>With SQS, consumers can either receive messages from the queue using <a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-short-and-long-polling.html">short polling or long polling</a>. When consumers use Short polling, SQS immediately returns messages from a subset of the servers where messages are distributed. This can result in empty responses or a subset of the messages not being returned to the consumers. Consumers are forced to do more sweeps to fetch the complete messages available on SQS. Example below where SQS messages A,C,D, and B from servers grayed out and it did not return message E.</p><figure><img alt="flow chart of cylinders with multicolored dots pointing to grey squares" src="https://cdn-images-1.medium.com/max/735/0*dcetmjLkpXo8COqX" /><figcaption><a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-short-and-long-polling.html">Short Polling SQS</a></figcaption></figure><p>AWS pricing increases with the number of polls to the queue. Long polling is a mechanism to stay connected to the queue for a longer time (up to 20 seconds) and as soon as a message arrives, start processing. This can reduce your costs as it will reduce the number of polls resulting in less empty reads and getting a complete set of messages from all servers. You can configure this per queue, it is called <em>Receive Message Wait Time.</em></p><figure><img alt="screenshot of queue attributes menu" src="https://cdn-images-1.medium.com/max/1024/0*-OwnXonPlo4eT7g9" /></figure><p>In the case of AWS Lambda using a SQS trigger, Lambda polls the queue (using long polling) and invokes the function synchronously with an event that contains messages.</p><h3>5. Consider Using Batch Size with Lambda and SQS</h3><p>Let’s say you have SQS as an event source for Lambda — i.e you have configured a SQS trigger for your Lambda function. In this case Lambda reads messages from the SQS queue and calls your function synchronously.</p><p>If your Lambda function code does some common initialization — like enriching data for every message that it processes, or it doesn’t have slow processing issues with downstream dependencies, etc. — it might be better to do a batch pull of messages at once. This can help save some processing time and costs. You can configure batchSize (up to 10) when you setup a SQS trigger as an event source for Lambda. Your function timeout should factor in time taken to process all messages.</p><p>When your function successfully processes a batch, Lambda deletes those messages from the queue. However, be careful about error handling here. If one of the messages that you pulled in the batch fails to process, the entire batch of messages in the SQS queue will become visible to the other consumers. Your options here would be to either be prepared to re-process the same batch again or to safely handle that exception in your code and return a success to the Lambda service that pulls from SQS (you can then leverage DLQs and explicitly send failed messages there or take care of explicitly deleting messages yourself in your function code).</p><p>Also, using <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html">batch</a> operations with SQS FIFO queues gives you more <a href="https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html">throughput</a> than without batching, so you can read more number of messages per second.</p><h3>6. Set the Right Visibility Timeout in SQS</h3><p>Visibility timeout for an SQS queue defines the period for which a message, once picked up by a consumer, remains hidden from the other consumers. Before the visibility timeout expires, the consumer that picked up the message needs to explicitly delete it from the queue, so that it does not become visible to other consumers.</p><p>Define a visibility timeout (shown in the image above) that is a little higher than the maximum processing time your application would need to process messages from the queue. Setting this too <em>low</em> compared to your application processing time would result in other consumers receiving the same message again, even if your application was successful in processing the message. Setting this too <em>high</em> would result in other consumers not getting the failed messages in a timely manner.</p><h3>7. Set the Right Retry Count When Lambdas are the Consumers of SQS</h3><p>When Lambda reads a batch from a SQS queue, the entire batch of messages is hidden until the queue’s visibility timeout. As messages appear in the SQS queue, Lambda initially opens five parallel long polling connections to the queue to perform the reads. If there are messages still available in the queue, it will <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html#events-sqs-queueconfig">increase</a> the number of processes that are reading messages to 60 more instances per minute, with a maximum of 1000 batches, that can be processed in parallel.</p><p>All the Lambda processes doing the reads of the batches synchronously will attempt to invoke the Lambda functions. But, what happens if the Lambda function invocations are throttled? The messages that can’t be processed as a result would become available after the visibility timeout.</p><p>AWS <a href="https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html">recommends</a> that you set the maxReceiveCount to at least five in your redrive policy for the queue so that messages can be retried before sending them to DLQ. Also, AWS recommends setting the visibility timeout of the source queue to at least six times your function’s timeout to allow for retries due to throttling, Lambda cold start times, etc.</p><h3>8. Get to Know Lambda’s Error Handling &amp; Where to Attach Your Dead Letter Queues to Capture All Errors</h3><p>Lambdas process SQS messages synchronously and SNS messages asynchronously. If you have a DLQ for the SNS topic and Lambda is a subscriber to this topic, that DLQ will only consist of messages that were unable to be delivered to the Lambda service (due to permissions or service unavailability) after all the retries. It will not contain messages that were successfully delivered to Lambda, picked up by your function, but unsuccessfully processed due to some other code or runtime issue. It will also not contain the throttling errors due to which your Lambda function could not be invoked.</p><p>The retries for such scenarios are handled by the Lambda service using its internal queues. You can configure the number of retries, max age of the event, and where to send failed messages to SQS, SNS, EventBridge, Lambda, etc.</p><p>Take a look at asynchronous invocation for Lambda’s <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html">here</a>.</p><figure><img alt="diagram of destinations for asynchronous invocation" src="https://cdn-images-1.medium.com/max/641/0*08FREZpmV5UXd2t_" /><figcaption><a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html">Lambda Asynchronous: Send failed messages to a new destination</a></figcaption></figure><p>Learn more about the different types of <a href="https://docs.aws.amazon.com/lambda/latest/dg/invocation-retries.html">errors</a> for Lambda’s.</p><h3>9. Know When to Use AWS EventBridge</h3><p>So far we have been talking about best practices when using SQS and SNS. However, there are scenarios when they are not the best tools for the job. Recently, AWS rolled out <a href="https://aws.amazon.com/eventbridge/">Amazon EventBridge</a> as another event bus with unique features that differentiate it from SQS or SNS. EventBridge was previously called CloudWatch Events, which was mainly used as the event bus for AWS resource state change events <em>(example: EC2 instance terminated)</em> or scheduled events <em>(example: Using a cron expression to trigger a Lambda)</em>.</p><p>AWS EventBridge supports a lot more clients as an event source and more destinations compared to SNS. It can deliver events to other AWS accounts which is an extremely useful feature in an organization where different teams each owning different accounts may want to subscribe to events in other’s accounts. One more awesome feature that it provides is that it can ingest events from third party SaaS applications and trigger its destinations. <strong><em>Example:</em></strong><em> You can configure EventBridge to get incidents that are created or updated in PagerDuty delivered to a Lambda function which can create a log of it.</em></p><p>There are a lot more useful features that EventBridge provides such as event routing using rules where you can filter messages based on the content of the event (unlike SNS where you have to rely on MessageAttributes with some limitations). Also, you can <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eventbridge-input-transformer-tutorial.html">transform</a> the event before sending it to the target.</p><p>However, compared to SNS there are currently <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/cloudwatch-limits-eventbridge.html">limitations</a> in the number of targets per rule, its permitted throughput, and latencies. This might change in the years to come as this is still a fairly new AWS service.</p><p><strong>***</strong></p><p>In this post we covered best practices for event-driven serverless architectures using the AWS solutions SNS, SQS, EventBridge, and Lambdas. I hope that this gave you some ideas on opportunities for cost optimization, gaining efficiencies in processing, and minimizing errors when using AWS solutions on event-driven serverless architectures.</p><p><em>DISCLOSURE STATEMENT: © 2020 Capital One. Opinions are those of the individual author. Unless noted otherwise in this post, Capital One is not affiliated with, nor endorsed by, any of the companies mentioned. All trademarks and other intellectual property used or displayed are property of their respective owners.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9bc12ad689f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-one-tech/guardrails-for-aws-event-driven-serverless-architectures-f9bc12ad689f">Guardrails for AWS Event-Driven Serverless Architectures</a> was originally published in <a href="https://medium.com/capital-one-tech">Capital One Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Popular Myths About Relational & No-SQL Databases Explained]]></title>
            <link>https://medium.com/capital-one-tech/popular-myths-about-relational-no-sql-databases-explained-60c0e1c3c87a?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/60c0e1c3c87a</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[cloud]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Tue, 14 Jul 2020 15:01:02 GMT</pubDate>
            <atom:updated>2020-07-14T15:25:17.932Z</atom:updated>
            <content:encoded><![CDATA[<h4>What’s no longer true about relational and No-SQL databases in 2020?</h4><figure><img alt="multiple characters surrounding multicolored cylinder containers" src="https://cdn-images-1.medium.com/max/1023/0*63E0P9sUnOlKFr-a.jpg" /></figure><p>There are plenty of articles on the web comparing the traditional characteristics of relational and No-SQL databases. So I won’t repeat them again here. This article is intended to shed light on the catchup game that relational and No-SQL databases are in; learning and implementing some best practices from one another.</p><p>When relational databases were originally designed in the 1970’s, storage was very expensive. So relational databases were built keeping a single machine in mind and were meant to be used for properly structured data that needed<a href="https://mariadb.com/resources/blog/acid-compliance-what-it-means-and-why-you-should-care/"> ACID</a> compliance enforced. Again, as storage was expensive, the data was normalized into several tables without any room for redundancy.</p><p>As more and more companies went digital in the 2000’s — growing data collection and storage needs — it became clear that relational databases don’t give the necessary flexibility for unstructured or semi-structured data. They don’t scale well under growing demand and were a single point of failure which impacted the availability. In addition, they had slow performance due to data normalization and the added overhead of object to relational data transformation.</p><p>To address these shortcomings, at a time when storage was becoming cheaper, No-SQL databases started coming to the forefront. They provided the flexibility needed for semi-structured or unstructured data by relaxing ACID compliance and following something called<a href="https://neo4j.com/blog/acid-vs-base-consistency-models-explained/"> BASE compliance</a>. They also provided tremendous scalability for massive data storage needs by distributing the data on several machines. To enable high availability, they followed “eventual consistency” where availability, even with stale data, is favored over consistency with the most up-to-date data.</p><p>However, it took a while for No-SQL databases to gain wide adoption. With their relaxed policies around data structure and eventual consistency, a lot of applications that needed structure and strong consistency did not lend themselves to No-SQL databases. It wasn’t easy for someone with a legacy application, built using relational databases, to port them over to No-SQL. Also, added complexity came with the distributed nature of these databases. The learning curve associated with the wide variety of No-SQL databases meant less tech savvy users weren’t able to explore the breadth of this category and the benefits offered.</p><p>In the last few years, the momentum behind open source databases has really paved the way for the developer community to think about the best practices offered in each database type and put efforts into overcoming some of the shortcomings. In addition, managed cloud solutions have invested a lot in building services to achieve optimal results for scalability, availability, performance, and security; these have made database maintenance and administration easier.</p><p>As a result, some of the criteria that were used to decide when to use relational or a No-SQL database have changed and should be re-verified to see if they still hold true.</p><p>Below, I will try to clarify some of the myths associated with relational and No-SQL databases.</p><h3>Myths About Relational Databases</h3><h4>1. Relational databases don’t offer fast read performance or scale</h4><p>If you have a read-heavy application, modern relational databases let you set up read replicas with configurations around how the replication would take place (synchronous vs asynchronous). This enables the application’s growing read traffic to get distributed across multiple read replicas through load balancing. The number of read replicas that can be configured varies by the database. Also, scaling compute, memory, and storage have become much easier with managed solutions such as<a href="https://aws.amazon.com/rds/"> AWS RDS</a> and there is no downtime associated to achieve the scaling.</p><p>The message here is to evaluate your specific use case and determine how many read replicas are needed for your application’s growing demand and what size will be sufficient. Don’t blindly rule out relational databases assuming they don’t scale at all, because they do for reads.</p><p><em>Note: With asynchronous replication to read replicas, one gets a fast write performance but has to deal with the trade offs associated with eventual read consistency. Synchronous replication would result in immediate consistency but slow down the write performance.</em></p><h4>2. Relational databases are not highly available</h4><p>Availability refers to the data being always made available to applications, whenever needed, despite failure conditions or infrastructure disruptions, etc. Availability is often measured by <em>uptime</em>. You have probably heard of the term RTO (Recovery Time Objective) — i.e how long does it take to restore something in case of a disruption. The lesser the RTO, the higher the availability.</p><p>With managed solutions such as<a href="https://aws.amazon.com/rds/"> AWS RDS</a>, the availability of a relational database has become super high with multi A-Z deployments. In case the primary database goes down, or connectivity to primary fails or the servers/data centers crash, AWS RDS can auto failover to the standby in a different A-Z without the need for applications to make any changes. This process of failover can take up to a couple of minutes (or even less if<a href="https://aws.amazon.com/rds/aurora/"> AWS Aurora</a> is used).</p><p>For non-cloud solutions, this might involve setting up a primary replica architecture and using solutions to detect the primary failure and failover to the standby (making it the new primary). This failover process could take a few hours.</p><p>The message here is to evaluate if that amount of downtime is acceptable for your use case and to not rule out relational databases without that analysis.</p><h4>3. Relational databases don’t offer support for a variety of data types and structures</h4><p>Traditional relational databases only offered support for certain standard data types such as Integer, String, Boolean, Long, etc. However, databases like<a href="https://www.compose.com/articles/what-postgresql-has-over-other-open-source-sql-databases/"> PostgreSQL</a> are object relational in nature and give you the ability to represent an object like structure in a database. Data need not be normalized in a traditional relational database style, requiring multiple tables with joins to represent that structure. They also support several data types suited for storing geometric, network address, text search, money, and array type data. You can also define your own custom data type as well. With the support for storing data in JSONB format, PostgreSQL provides flexibility for unstructured data and enables faster data retrieval.</p><h3>Myths About No-SQL Databases</h3><h4>1. No-SQL databases or non-relational databases cannot be used for storing relationships between entities</h4><p>When someone says No-SQL or non-relational databases, it does not mean they don’t or can’t represent relationships between entities. They definitely do, but it doesn’t need to be in a normalized table/column format. In the below example you can see the contrast on how relationships are expressed in a document hierarchical structure.</p><p><em>Ex: Normalized structure in relational vs hierarchical structure in No-SQL</em></p><figure><img alt="flow chart of many files outlined in blue" src="https://cdn-images-1.medium.com/proxy/0*dKtOoXT-EUJ6isl0" /></figure><h4>2. No-SQL databases are not reliable for critical application use cases because they are eventual consistent</h4><p>Originally, No-SQL databases practiced eventual consistency to offer high availability and to have fast write performance. The tradeoffs involved applications accepting the risk of reading stale data for a while and eventually getting caught up or having data loss.</p><p>However, No-SQL databases these days allow you to choose between eventual consistency and strong consistency. You can also configure how many replicas need to acknowledge a transaction before it is committed (commonly called quorum).</p><p><em>Ex: Eventual Consistency in No-SQL databases</em></p><figure><img alt="flow chart of 2 data centers showing nodes and green squares depicting computers" src="https://cdn-images-1.medium.com/max/625/1*JrtNsBpXMmqp2gJLMq8r4A.png" /><figcaption><em>“Conceptual Depiction of Replication with Eventual Consistency” (https://cloud.google.com/datastore/docs/articles/balancing-strong-and-eventual-consistency-with-google-cloud-datastore) by Google Cloud (https://cloud.google.com/) is licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)</em></figcaption></figure><h4>3. No-SQL databases offer far better performance for all scenarios</h4><p>It is generally true that No-SQL databases offer superior read performance because they come custom fit for the structure of your data (key-value, graph, documents, etc).</p><p>However, there are a couple of nuances.</p><p><strong>a. Database Design</strong>: Extracting the best performance is heavily dependent on understanding the commonly used applications data access patterns and then designing the database based on those patterns. A bad database design, despite the right choice of No-SQL database, will not yield good results. Also, if you issue ad hoc queries outside of those standard application access patterns to the No-SQL databases, the performance won’t be ideal.</p><p><strong>b. Sharding</strong>: One of the main benefits of using a No-SQL database is how efficiently it can scale to high traffic loads using a distributed architecture technique called <a href="https://medium.com/@jeeyoungk/how-sharding-works-b4dec46b3f6"><strong>sharding</strong></a>, which is also known as a <strong>horizontal scaling</strong> mechanism. Instead of the traditional approach of increasing CPU/RAM/Disk space for a server (vertical scaling), sharding stores the data in a distributed fashion across several machines. When the traffic goes up, by increasing the number of shards (the number of machines in the cluster), the database adjusts itself to the load automatically. However, one needs to be aware of possible hotspots that can arise by choosing a wrong shard key. Data can get unevenly distributed among the shards and all the load can heavily concentrate on certain shards, not yielding the best performance.</p><p>The message here is using the wrong No-SQL database for your use case or using it incorrectly will not get you positive results. There are specific scenarios for which No-SQL databases offer far better performance, but not for everything.</p><h4>4. No SQL databases are only to be used for massive data needs</h4><p>While it is true that NO SQL databases are a great choice when your data is getting continuously generated and you have massive storage needs, one should not rule out No-SQL databases when they have smaller data storage needs. With “pay what you use” pricing models in the cloud, you won’t lose anything by picking No-SQL databases for small data footprints.</p><h4>5. No SQL means no schema</h4><p>No SQL databases give you the flexibility to store unstructured or semi-structured data. However, you can still enforce a schema, if you want to, where it is needed. Databases such as<a href="https://docs.mongodb.com/manual/core/schema-validation/"> MongoDB</a>, which stores data in a JSON format, let you perform validations using JSON Schema. You can configure if you want those validations to result in accepting or rejecting the documents during inserts or updates, and how they apply to existing documents.</p><p>As you can see, relational and No-SQL databases have come a long way in overcoming some of their shortcomings and have started to learn from each other. While they are still very different and solve different problems, a lot has changed over time. This convergence across database families should force us to rethink our database choices. Let’s not rule out certain databases based on market popularity or historical comparison of traditional traits. Because that information might not be as relevant in 2020 as it once was.</p><p><em>Originally published at </em><a href="https://www.capitalone.com/tech/software-engineering/relational-and-nosql-database-myths/"><em>https://www.capitalone.com</em></a><em>.</em></p><p><em>DISCLOSURE STATEMENT: © 2020 Capital One. Opinions are those of the individual author. Unless noted otherwise in this post, Capital One is not affiliated with, nor endorsed by, any of the companies mentioned. All trademarks and other intellectual property used or displayed are property of their respective owners.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60c0e1c3c87a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-one-tech/popular-myths-about-relational-no-sql-databases-explained-60c0e1c3c87a">Popular Myths About Relational &amp; No-SQL Databases Explained</a> was originally published in <a href="https://medium.com/capital-one-tech">Capital One Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Microservices Best Practices for the Optimal Architecture Design]]></title>
            <link>https://medium.com/capital-one-tech/10-microservices-best-practices-for-the-optimal-architecture-design-capital-one-de16abf2a232?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/de16abf2a232</guid>
            <category><![CDATA[microservice-architecture]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Tue, 26 May 2020 16:41:44 GMT</pubDate>
            <atom:updated>2020-07-28T15:54:00.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="3 figurines of male construction workers wearing yellow hats, standing on a black computer keyboard" src="https://cdn-images-1.medium.com/max/767/0*svLsTyjPqory4r2A.png" /></figure><p>Microservices have fundamentally changed the way server side engines are architected. Rather than a single giant monolithic codebase hosting all the business logic of your application, microservices reflect the distributed systems model, where a group of application components work together to deliver the business needs. By following ten basic microservices best practices, you can achieve an efficient microservices ecosystem devoid of unnecessary architectural complexities.</p><h3>Benefits of a Microservices Architecture</h3><p>When the migration from monolithic application to microservices architecture is done right, the following benefits should be realized:</p><ol><li>You should be able to develop a microservice in a language of your choice, release it independently at your own pace, and scale it independently.</li><li>Since different teams in an organization can independently own certain microservices, time to market should be faster as there is parallel development with more reuse.</li><li>You get better fault isolation, as errors in one particular microservice can be contained, so the rest of the ecosystem would not be impacted.</li></ol><p>However, if proper principles are not followed when building microservices, you can end up with an entangled spaghetti like this.</p><figure><img alt="web of grey rectangles with black text in it pointing to grey cylinder with black text in it" src="https://cdn-images-1.medium.com/max/974/0*GzZNFWj4QiOJnS2f.png" /></figure><p>This becomes very difficult to maintain, as it requires a lot of coordination with multiple teams to make changes, release or achieve fault tolerance.</p><p>Making the most of microservices is a science and involves some discipline. The microservices best practices and design principles below will help you build microservices that are loosely coupled, distributed, and optimized to deliver best value.</p><h3>10 Microservices Best Practices</h3><h4>1. The Single Responsibility Principle</h4><p>Just like with code, where a class should have only a single reason to change, microservices should be modeled in a similar fashion. Building bloated services which are subject to change for more than one business context is a bad practice.</p><p><em>Example: Let’s say you are building microservices for ordering a pizza. You can consider building the following components based on the functionality each supports like InventoryService, OrderService, PaymentsService, UserProfileService, DeliveryNotificationService, etc. InventoryService would only have APIs that fetch or update the inventory of pizza types or toppings, and likewise others would carry the APIs for their functionality.</em></p><h4>2. Have a separate data store(s) for your microservice</h4><p>It defeats the purpose of having microservices if you are using a monolithic database that all your microservices share. Any change or downtime to that database would then impact all the microservices that use the database. Choose the right database for your microservice needs, customize the infrastructure and storage to the data that it maintains, and let it be exclusive to your microservice. Ideally, any other microservice that needs access to that data would only access it through the APIs that the microservice with write access has exposed.</p><h4>3. Use asynchronous communication to achieve loose coupling</h4><p>To avoid building a mesh of tightly coupled components, consider using asynchronous communication between microservices.</p><p><strong>a.</strong> Make calls to your dependencies asynchronously, example below.</p><p><em>Example: Let’s say you have a Service A that calls Service B. Once Service B returns a response, Service A returns success to the caller. If the caller is not interested in Service B’s output, then Service A can asynchronously invoke Service B and instantly respond with a success to the caller.</em></p><p><strong>b.</strong> An even better option is to use events for communicating between microservices. Your microservice would publish an event to a message bus either indicating a state change or a failure and whichever microservice is interested in that event, would pick it up and process it.</p><p><em>Example: In the pizza order system above, sending a notification to the customer once their order is captured, or status messages as the order gets fulfilled and delivered, can happen using asynchronous communication. A notification service can listen to an event that an order has been submitted and process the notification to the customer.</em></p><h4>4. Fail fast by using a circuit breaker to achieve fault tolerance</h4><p>If your microservice is dependent on another system to provide a response, and that system takes forever to respond, your overall response SLAs will be impacted. To avoid this scenario and quickly respond, one simple microservices best practice you can follow is to use a circuit breaker to timeout the external call and return a default response or an error. The Circuit Breaker pattern is explained in the references below. This will isolate the failing services that your service is dependent on without causing cascade failures, keeping your microservice in good health. You can choose to use popular products like <a href="https://github.com/Netflix/Hystrix">Hystrix</a> that Netflix developed. This is better than using the HTTP CONNECT_TIMEOUT and READ_TIMEOUT settings as it does not spin up additional threads beyond what’s been configured.</p><h4>5. Proxy your microservice requests through an API Gateway</h4><p>Instead of every microservice in the system performing the functions of API authentication, request / response logging, and throttling, having an API gateway doing these for you upfront will add a lot of value. Clients calling your microservices will connect to the API Gateway instead of directly calling your service. This way you will avoid making all those additional calls from your microservice and the internal URLs of your service would be hidden, giving you the flexibility to redirect the traffic from the API Gateway to a newer version of your service. This is even more necessary when a third party is accessing your service, as you can throttle the incoming traffic and reject unauthorized requests from the API gateway before they reach your microservice. You can also choose to have a separate API gateway that accepts traffic from external networks.</p><h4>6. Ensure your API changes are backwards compatible</h4><p>You can safely introduce changes to your API and release them fast as long as they don’t break existing callers. One possible option is to notify your callers , have them provide a sign off for your changes by doing integration testing. However, this is expensive, as all the dependencies need to line up in an environment and it will slow you down with a lot of coordination . A better option is to adopt contract testing for your APIs. The consumers of your APIs provide contracts on their expected response from your API. You as a provider would integrate those contract tests as part of your builds and these will safeguard against breaking changes. The consumer can test against the stubs that you publish as part of the consumer builds. This way you can go to production faster with independently testing your contract changes.</p><h4>7. Version your microservices for breaking changes</h4><p>It’s not always possible to make backwards compatible changes. When you are making a breaking change, expose a new version of your endpoint while continuing to support older versions. Consumers can choose to use the new version at their convenience. However, having too many versions of your API can create a nightmare for those maintaining the code. Hence, have a disciplined approach to deprecate older versions by working with your clients or internally rerouting the traffic to the newer versions.</p><h4>8. Have dedicated infrastructure hosting your microservice</h4><p>You can have the best designed microservice meeting all the checks, but with a bad design of the hosting platform it would still behave poorly. Isolate your microservice infrastructure from other components to get fault isolation and best performance. It is also important to isolate the infrastructure of the components that your microservice depends on.</p><p><em>Example: In the pizza order example above, let’s say the inventory microservice uses an inventory database. It is not only important for the Inventory Service to have dedicated host machines, but also the inventory database needs to have dedicated host machines.</em></p><h4>9. Create a separate release train</h4><p>Your microservice needs to have its own separate release vehicle which is not tied to other components within your organization. This way you are not stepping on each other’s toes and wasting time coordinating with multiple teams.</p><h4>10. Create Organizational Efficiencies</h4><p>While microservices give you the freedom to develop and release independently, certain standards need to be followed for cross cutting concerns so that every team doesn’t spend time creating unique solutions for these. This is very important in a distributed architecture such as microservices, where you need to be able to connect all the pieces of the puzzle to see a holistic picture. Hence, enterprise solutions are necessary for API security, log aggregation, monitoring, API documentation, secrets management, config management, distributed tracing, etc.</p><h3>***</h3><p>By following these microservices best practices, you should end up with a loosely coupled, distributed, and independent microservice system, wherein you can achieve the true benefits of a microservices architecture as listed at the beginning of this article.</p><h3>References</h3><p><strong>API Gateway Pattern</strong><br><a href="https://microservices.io/patterns/apigateway.html">Microservices Pattern: API gateway pattern</a><br><a href="https://microservices.io/patterns/apigateway.html"><em>Let’s imagine you are building an online store that uses the Microservice architecture pattern and that you are…</em>microservices.io</a></p><p><strong>Circuit Breaker</strong><br><a href="https://martinfowler.com/bliki/CircuitBreaker.html">bliki: CircuitBreaker</a><br><a href="https://martinfowler.com/bliki/CircuitBreaker.html"><em>It’s common for software systems to make remote calls to software running in different processes, probably on different…</em>martinfowler.com</a></p><p><em>Originally published at </em><a href="https://www.capitalone.com/tech/software-engineering/10-design-principles-optimize-microservices-potential/"><em>https://www.capitalone.com</em></a><em>.</em></p><h3>Related:</h3><figure><a href="https://medium.com/capital-one-tech/popular-myths-about-relational-no-sql-databases-explained-60c0e1c3c87a"><img alt="" src="https://cdn-images-1.medium.com/max/704/1*TH90aOKf1yi97ecC4mEw-w.png" /></a></figure><p><em>DISCLOSURE STATEMENT: © 2020 Capital One. Opinions are those of the individual author. Unless noted otherwise in this post, Capital One is not affiliated with, nor endorsed by, any of the companies mentioned. All trademarks and other intellectual property used or displayed are property of their respective owners.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de16abf2a232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-one-tech/10-microservices-best-practices-for-the-optimal-architecture-design-capital-one-de16abf2a232">10 Microservices Best Practices for the Optimal Architecture Design</a> was originally published in <a href="https://medium.com/capital-one-tech">Capital One Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t give feedback to someone without these 3 things]]></title>
            <link>https://medium.com/swlh/dont-give-feedback-to-someone-without-these-3-things-3ad8dd83bf03?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ad8dd83bf03</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Fri, 15 May 2020 00:39:17 GMT</pubDate>
            <atom:updated>2020-05-15T00:39:17.027Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*7WHdPZD-ElJhufu-7E0_Cg@2x.jpeg" /></figure><p>Whether you are a manager or an employee , there are times when providing feedback to someone is necessary. May be its your job to regularly provide feedback or maybe someone is not behaving appropriately with you or someone explicitly asked you to provide feedback .</p><p>But how do you provide feedback when you are new to the process or not good at it ? If it makes you feel uncomfortable or makes you sweat , this article is for you . We will go through the tips on the content of the feedback first , then talk about how to deliver the message and the most important of all , how to ensure the feedback is actionable.</p><p><strong>1. Content of the feedback</strong></p><p>Whether it is a direct observation from you or feedback collected from someone else , there are 2 critical pieces of information that are necessary in the content of the feedback.</p><p>a. <strong>Specific observation points in a context , within a bounded time frame: </strong>This could be behavior exhibited in a particular situation , skills demonstrated in a particular project assignment or lack of skills during a particular time period of observation. This needs to be very specific and not vague .</p><p><em>For example : It doesn’t help to say , you are weak in your communication ; instead more meaningful message would be , “when you gave a presentation in our team meeting last month , half of the room had to repeatedly ask you questions to get to your intent. You need to improve your communication to get to the point that you are trying to say precisely </em>“ .</p><p>b. <strong>What kind of impact it had</strong>: Another mandatory information in the feedback is the impact certain behaviors or skills had on the project , fellow team members, stakeholders , business or customers . This could be a positive or negative impact.</p><p><em>In the example above , this would look like , “ the team meeting was unproductive as a lot of time was wasted for those in the room “</em>.</p><p><em>Another example would be “When you released faulty code to production, it resulted in the customers seeing a misleading message , making them call our call centers and causing impacts to agent productivity and customer experience “.</em></p><p><strong>2. Delivering the feedback</strong></p><p>As important is the content of the feedback , delivering the feedback right is equally important. This is where the even the experienced , can strike the chord negatively.</p><p>a. <strong>Deliver a rounded message</strong> : Remember , you are not just there to talk about areas of improvement or it make someone look bad . Dont forget to call out positive observations.</p><p><strong>b. Dont beat around the bush or sugar coat the message: </strong>So as to not waste anyone’s time and to make sure the feedback is registered , come to the point soon. Sugar coating a message can have the effects of missing the emphasis on the actual feedback.</p><p><strong>c. Be empathetic but keep your other emotions out of it : </strong>We are all human at the end of the day , and humans have emotions ,let’s not forget that. So listen, spend time and genuinely care about the other person’s emotions. Also, while delivering feedback, watch out for unprofessional behavior in your expressions or body language or tone.</p><p><strong>d. Timing is important : </strong>Feedback needs to be timely to have the best effect. It needs to be ongoing . Don’t save the feedback for year end , a lot of damage could have happened by then.</p><p><strong>e. Own your feedback : </strong>Your feedback is yours, not your managers, not your colleagues, its yours. Dont put the blame on someone else just to get by the situation.</p><p><strong>3. Make the feedback actionable</strong></p><p>Ask yourself a question when you are about to give feedback to someone , What is the purpose of it ? If the answer is that, you want the recipient of the feedback to course correct their behavior or skills and show improvement, then make the feedback actionable as well .</p><p>a. Suggest relevant training or courses to take or a coach who can help</p><p>b. Give them opportunities to demonstrate progress</p><p>c. Make the action items time bound</p><p>d. Regularly measure progress</p><p>Hopefully this article has provided some guidance around what and how of delivering feedback to someone. If you are the one receiving feedback and don’t have clarity on the feedback that was handed to you , ask for the above details .</p><p>Remember, feedback is extremely valuable for ones personal growth and emotional wellbeing . Preparing , Delivering and measuring it right can really transform individuals . Don’t do it half baked , without clarity or just for the sake of checking the box .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad8dd83bf03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/dont-give-feedback-to-someone-without-these-3-things-3ad8dd83bf03">Don’t give feedback to someone without these 3 things</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Tips to let  go of your comfort zone]]></title>
            <link>https://sandeepjandhyala.medium.com/5-tips-to-let-go-of-your-comfort-zone-f8beea8a0bc9?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8beea8a0bc9</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Thu, 05 Mar 2020 03:52:06 GMT</pubDate>
            <atom:updated>2020-03-05T03:52:06.178Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>5 Tips to let go of your comfort zone</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*mMDl_j7fITYnLSnxLJVjiw.jpeg" /></figure><p>As human beings , all of us are subject to emotions, those of compassion or anger or envy or joy or sadness and a lot of them at various phases in our life’s and careers . In this article we will talk about a major inhibitor in our careers, holding us back from taking a next step ; fear . So , what causes it , why does it cripple us and how to overcome it in order to achieve growth ?</p><p>When you have worked on certain standard types of projects , got familiar with the work environment and have built a good network around you , you are in something called a comfort zone . This is similar to you relaxing on a couch in front of your tv and watching your favorite show while working on a laptop . You think you are being productive , but that’s not being quite effective and definitely you are not challenging yourself . If you’re not challenging yourself , you are stagnant and not growing .</p><p>Most people would agree that operating in their comfort zone for an extended period is going to make them complacent and stale . Yet, a very few of them venture to step out of it and do something different. The vast majority either get a late wake up call at which point they struggle to come up to speed or they succumb to the cozyness.</p><p>So , Why does it take this group of people, who know that they have been in a comfort zone for a while , so long to step out of it and do something different ? It’s the fear of unknowns that holds them down . Let’s examine a few top types of worries .</p><ul><li>Fear of not being able to learn the new skills needed for the new job or project</li><li>Fear of not being able to perform at the level and speed of your new team.</li><li>Fear of having to start building connections from the scratch ; new team means having to work with strangers and establish trust .</li><li>Fear of a new work place environment , which may have a different culture with lesser flexbility or transparency.</li><li>Fear of not getting as much financial recognition or suitable designation or other perks that the comfort zone is giving you.</li><li>Fear of losing work flexibility or having to work overtime .</li></ul><p>If you have some of these worries , here are a few ways in which you can overcome these fears and get into something called a growth zone</p><ul><li><strong>Be Curious</strong> : First off, be open to the idea of getting to know whats out there . Put on your curious George hat and look around to see what kind of work other teams are doing . When you meet your friends or colleagues at lunch or coffee , ask about what they working on. Attend some lunch and learn sessions or tech showcases or demos . There is no harm in being curious. You do this and you win half the battle just by being ready to keep your eyes and ears open . Why ? Because , you will start learning and growing.</li><li><strong>Practice new skills</strong>: Read up on areas that interest you to know more about a topic. There are plenty of articles on the internet . Watch youtube videos on a beginners guide to something. Do a small project to practice what you have learnt. Until you do this , you wont feel comfortable. It might not be easy at first , but investing some time to sit through this exercise will help you get confident.</li><li><strong>Market Awareness </strong>: Most people who are settled in their comfort zone are likely with the same company for a while. Being market aware , requires you to extend your curiosity beyond your company. Attend tech or leadership conferences that other companies host , where you can register . This will not only give you a view into what others in the market are doing , but it’s also an opportunity to establish some connections and get some material to research. You can also read blogs of some famous companies or watch recordings of conferences like Google I/O or AWS ReInvent online.</li><li><strong>Do some presentations</strong>: Possibly the best way to build your self confidence is to prepare on a topic and give a presentation in front of a small group . This is a mechanism to share your knowledge and interact with the audience. Once you feel comfortable, do it in front of a larger crowd .</li><li><strong>Find a Mentor</strong>: There is no better resource to help you step out of your comfort zone than a good mentor. Find someone who you feel is practicing all the above mentioned tips and can be good coach as well . They will continue to challenge you , until you establish the discipline yourself. This person need not be your manager, it can be your friend or a peer in your team or some other group. You want to feel challenged , similar to how a personal trainer at a gym would put you through pressure tests.</li></ul><p>Hopefully after following these tips , you will let go of some of your fears. You can always minimize your exposure to a subset of fears at once . For example: You can opt to work on a different project with a manager who you worked with in the past , as he/she can give you that comfort feeling and help you build the network around. Another option is you can internally look for a new challenge and try it out for sometime .</p><p>The goal is to not stay in your comfort zone for too long . What is too long is subjective , you are the best judge , but just don’t become outdated. There are no rewards for loyalty alone at workplaces .</p><p>So , own your career paths and start getting into growth zones frequently.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8beea8a0bc9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 resources to identify your strengths]]></title>
            <link>https://sandeepjandhyala.medium.com/10-resources-to-identify-your-strengths-3b3c5bbf5f86?source=rss-866c0b7bb689------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b3c5bbf5f86</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[strength]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Sandeep Jandhyala]]></dc:creator>
            <pubDate>Mon, 24 Feb 2020 15:39:48 GMT</pubDate>
            <atom:updated>2020-03-05T18:22:10.259Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>10 resources to help identify your strengths</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/209/1*s4hJ9omKmMvWQc2GpThHEg@2x.jpeg" /></figure><p>Most often we tend to focus on getting better at ones weaknesses rather than our strengths. If you ask someone what their strengths are, they might not be ready with the answers , but most certainly , they will be able to list their weaknesses .</p><p>Why is that ? Well, how much time do we actually spend understanding what made us successful in doing something and give ourselves a pat on the back ?We are quick to investigate what caused a failure , perform a thorough root cause analysis , and take preventative measures to avoid those mistakes again.</p><p>I bet some of you are even hesitant to write your own performance reviews at work because your nature isn’t one of self boasting or may be you are too lazy . And some of you shy away when your receive praise or flattery for something ; may be you think thats your job anyways or may be it makes you feel awkward.</p><p>Let me tell you why is it important to know your strengths. First and foremost, it will give you a lot of self confidence to take on the world. You will be able to suit yourself in the fields of work which demand your strengths . You will be able to look for partners who have complementary strengths to effectively tackle a problem . And finally, when someone tells you, “you are not good at xyz” , you will have an answer and examples to share about your strengths.</p><p>Playing on your strengths requires you to know yourself deeper . Here are some resources that can help you identify your strengths</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/180/1*Ssd4OoV3Z-wklD9PsGhqHQ@2x.jpeg" /></figure><p><strong>Ways to Identify</strong> <strong>your</strong> <strong>strengths</strong></p><ul><li>Ask yourself , what are the characteristics that you inherently possess which make you energized or characteristics that are natural to you , where you don’t have to exert yourself and drain energy.</li><li>Introspect on projects that you were a part of , and note down what value you brought to the table ; how did you approach the problem ; how did you overcome any obstacles that you ran into.</li><li>Reflect on the moments where you thought you accomplished something awesome in your current role or in the past and think about what did you do to reach that state.</li><li>Think about the times when someone recognized you for your contributions and why.</li><li>Think about times when someone approached you to solve a particular problem or provide advice . What characteristics in you made people to come to you.</li><li>Learn about the strengths relevant to the job family that you are in , by reading the job description or qualities that the best in that field possess and see if you are able to notice some of the strengths applicable to you.</li><li>Ask your friends and family on what they see you good at .</li><li>Ask your manager at work or previous managers whom you worked for or your colleagues that you work with .</li><li>Take some personality tests such as Myers Briggs or any of the popular ones on the internet .</li><li>Read books such as the strengths finder which gives elaborately gives examples of several characteristics.</li></ul><p>By now you should have had a decent idea of what your strengths are , what motivates you the most and what are you passionate about . Once you identify what your strengths are , work on how to maximize those instead of spinning wheels on your weaknesses.</p><p>You will be much more successful and happy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b3c5bbf5f86" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>