<?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 Vivek Madurai on Medium]]></title>
        <description><![CDATA[Stories by Vivek Madurai on Medium]]></description>
        <link>https://medium.com/@vivekmadurai?source=rss-deec4a332fb7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M0CBYhTXN6aW5s0PgzPQ2A.jpeg</url>
            <title>Stories by Vivek Madurai on Medium</title>
            <link>https://medium.com/@vivekmadurai?source=rss-deec4a332fb7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:01:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vivekmadurai/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[Multi-tenancy in REST API]]></title>
            <link>https://medium.com/@vivekmadurai/multi-tenancy-in-rest-api-a570d728620c?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a570d728620c</guid>
            <category><![CDATA[rest]]></category>
            <category><![CDATA[url]]></category>
            <category><![CDATA[multitenancy]]></category>
            <category><![CDATA[stateless]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Mon, 07 Oct 2019 07:34:07 GMT</pubDate>
            <atom:updated>2019-10-07T07:34:07.787Z</atom:updated>
            <content:encoded><![CDATA[<p>Multi-tenancy architecture helps us to share the resources cost-efficiently and securely in cloud environments where the single instance of the software runs on a server and serves multiple tenants. In which statelessness plays a major role in scaling for millions of concurrent users. Statelessness means that every Http request(API) happens in complete isolation. When the client makes an Http request, it includes all the information necessary for the server to fulfill that request.</p><p>In this article, I will be sharing different ways to build REST API for multi-tenant stateless application which will be consumed by different client application such as Mobile, Web browser and Integration platforms, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*l4Md3ejyIdipwiHouBLrnQ.png" /></figure><p>When it comes to multi-tenancy the only variant is the tenant Id. Since its a stateless system, the system needs to know tenant information in order to process the request and get the corresponding resources. For example, each tenant’s data either get saved in different tenant database or separated with tenant id as a namespace. The only option for the backend to access the tenant-specific is to send the tenant identifier part of every API.</p><p><strong>URL</strong>: &lt;<strong>scheme</strong>&gt;://&lt;<strong>domain</strong>&gt;/&lt;<strong>path</strong>&gt;?&lt;<strong>query</strong>-<strong>param</strong>&gt;#&lt;nose&gt;</p><p>A URL contains scheme/protocol and a domain. Every URL get differentiated from others by changing the path or query param. I have listed some of the methods in which a tenant can get identified as part of REST API,</p><p><strong>Query parameter based tenant identification</strong></p><p>In this approach, the client will send the tenant-id as part of the parameter to the server in addition to other required parameters they need to send. This is not a recommended approach to implement multitenant based API’s.</p><blockquote>example:</blockquote><blockquote>https://&lt;your-domain&gt;.com/&lt;api-context&gt;?tenantid=&lt;tenant-id&gt;&amp;&lt;other-parameters&gt;</blockquote><p><strong>URL path based tenant identification</strong></p><p>In this approach, the API is designed in a way to mandatorily accommodate tenant-id as part of the URL path. So that the server can parse the URL path to get the tenant-id. Most of the multitenant system uses this approach to identify their tenant context.</p><blockquote>example:</blockquote><blockquote>https://&lt;your-domain&gt;.com/&lt;tenant-id&gt;/&lt;api-context&gt;</blockquote><p><strong>Domain-based tenant identification</strong></p><p>In this method, your application is accessed by your client via their own subdomain. This approach the server requires an additional effort to maintain the mapping between the tenant’s domain and tenant id from your end.</p><blockquote>example:</blockquote><blockquote>https://&lt;tenant-domain&gt;.&lt;your-domain&gt;.com/&lt;api-context&gt;</blockquote><blockquote>&lt;tenant-domain&gt;:&lt;tenant-id&gt;</blockquote><p><strong>Custom Http header-based tenant identification</strong></p><p>In this method, we can pass the tenant-id as part of your own custom Http headers like <strong>X-TENANT-ID</strong>. It&#39;s not recommended to use custom headers as a way of addressing multitenancy or a resource. They should be used instead to pass ancillary information like accept types, auth tokens, etc.</p><p><strong>As part of the custom attribute in JWT token</strong></p><p>JSON Web Token is an open industry standard for representing claims securely between two parties. Click <a href="https://jwt.io/">here</a> to know more about <a href="https://jwt.io/">JWT</a>.</p><p>The JWT token’s payload will have two information logged-in user’s identification and its corresponding tenant identification. This token will be sent part of a client cookie or a custom header.</p><blockquote>example:</blockquote><blockquote>{<br> “sub”: “1234567890”,<br> “name”: “&lt;user-name&gt;”,<br> “iat”: 1516239022,<br> “userid”: “&lt;user-id&gt;”,<br> “tenantid”: “&lt;tenant-id&gt;”<br>}</blockquote><p>We have seen different ways on how a tenant id can be represented in REST API. When it comes to which is best or which one to choose? its just a question of taste, choose the one that suits you most. The one we’ve used in our API implementation is by having the tenant-id part of the URL path. I would suggest the URL path and sub-domain based tenant identification when compared to other options.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a570d728620c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservice Authorization]]></title>
            <link>https://medium.com/@vivekmadurai/microservice-authorization-af8d9efa2123?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/af8d9efa2123</guid>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[authorization]]></category>
            <category><![CDATA[service-to-service]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Wed, 18 Sep 2019 05:53:01 GMT</pubDate>
            <atom:updated>2019-09-18T05:53:01.573Z</atom:updated>
            <content:encoded><![CDATA[<p>I am sure you would have enjoyed and learned something new from my previous blog. In my previous article, I have covered how I used JSON Web Token(JWT) for<a href="https://medium.com/@vivekmadurai/microservice-authentication-70b2dde94a0"> service-based authentication</a>. Once the request is verified(<strong>authenticated</strong>) we need to make sure they have the right access to read, edit or delete the resources(<strong>authorization</strong>). In this article, I will be covering the authorization in microservice with the help of JWT which we used in our product<a href="https://kissflow.com/"> Kissflow</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/0*LnvjWPRn-YP7GCm0" /></figure><p>As we move from monoliths towards microservice we also move away from local libraries, SDK, API calls within the same network and our flexibility in Access control. More and more services getting deployed this will become a nightmare for us.</p><p>We need to separate out the authentication and authorization from every microservice. Authentication and Authorization in our system are implemented based on a sidecar pattern, a sidecar is independent of its primary application in terms of the runtime environment and programming language. The primary application container and sidecar(<strong>auth</strong> <strong>service</strong>) container are bundled together as a microservice. Because of its proximity to the primary applications, there’s no significant latency when communicating between them.</p><p>The sidecar contains two major components the <strong>Authenticator</strong> which receives the credential and performs verification and an <strong>Authorizer </strong>which makes use of the session/token returned but the Authenticator and evaluates the incoming API/HTTP request based on below-mentioned access controls and decides whether the request should be allowed or not.</p><ul><li>Role-Based Access Control(RBAC)</li><li>Metadata Based Access Control(MBAC)</li><li>Data-Based Access Control(DBAC)</li><li>Service-Based Access Control(SBAC)</li></ul><p><strong>Role-Based Access Control</strong>(RBAC): A widely used access control mechanism that restricts access to resources based on the roles of individual users. There will be API-Registry which maintain the list of API against the list of Roles like Admin, Creator, Member, User, etc. The <strong>Authenticator </strong>sets the user’s Role part of JWT and the RBAC controller which is a part of <strong>Authorizer </strong>makes use of the Role from JWT and validates the incoming API against the Roles from API-Registry and prevents the user from accessing information that doesn’t pertain to them.</p><p><strong>Metadata Based Access Control</strong>(MBAC): We can call this as Config Based Access Control. This methodology manages access rights by evaluating the user-defined config(metadata). In our product, we have an option to configure custom access controls like who can initiate the request, who can act, who can manage, etc. The <strong>Authorizer </strong>will load the respective metadata based on the URL and check against the logged-in user.</p><p><strong>Data-Based Access Control</strong>(DBAC): In this security model the creator of the application defines the rules that govern the access to specific resources. These rules are based on conditions which define SLA, Assigned to, Delegated to, etc.</p><p><strong>Service-Based Access Control</strong>(SBAC): The biggest enemies in distributed architecture are boundaries and dependencies. With microservices, each microservice is meant to operate on its own. However, some part of the system relies on cooperation and integration with other services. In concrete, one service needs to access the data managed by another service. We maintain a service dependency in the same API registry which we discussed above, which will be used by the <strong>Authorizer </strong>to validate the incoming request from a different service. SBAC will play a major role in the chain of service calls. I have explained about the role of JWT in service to service and chain of service communication in my previous<a href="https://medium.com/@vivekmadurai/microservice-authentication-70b2dde94a0"> article</a>.</p><p>When comes to authorization we can split the API into two different variations based on access controls,</p><ul><li>One needs the user context and</li><li>Other doesn’t care(Public API)</li></ul><p>Few API ‘s are marked as public which can be accessed without user context, in other words, certain API doesn’t need user login. The access controls like RBAC, MBAC, and DBAC will be performed only on the user context API’s. Practically, SBAC doesn’t need a user context. But in our use case, we don’t have a requirement for a public API being dependent on other services, so even SBAC doesn’t get involved without a user context.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af8d9efa2123" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservice Authentication]]></title>
            <link>https://medium.com/@vivekmadurai/microservice-authentication-70b2dde94a0?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/70b2dde94a0</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[service-to-service]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Fri, 23 Aug 2019 05:39:09 GMT</pubDate>
            <atom:updated>2019-08-23T05:39:09.285Z</atom:updated>
            <content:encoded><![CDATA[<p>With the recent rise in the microservice architecture, authentication has been gaining popularity in the tech community. Authentication in microservice involves two use cases</p><ul><li>User Authentication</li><li>Service-Based Authentication</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lO6iHLsUbPr1_IAu4OiRGw.jpeg" /></figure><p>I have published an article on different ways to authenticate a web application, in which I have covered how a user can register his identity into an application, <a href="https://medium.com/@vivekmadurai/different-ways-to-authenticate-a-web-application-e8f3875c254a">Click here</a> to know more about user authentication. In this article, I will primarily be covering service-based authentication.</p><p>When it comes to service-based authentication, a microservice can be accessed through various means,</p><ul><li>By a direct user</li><li>By other microservices</li><li>By external/third-party application</li></ul><p>We have open platforms like <a href="https://istio.io/"><strong>ISTIO</strong></a><strong> </strong>which is very popular in Kubernetes Community and <a href="https://spiffe.io/spiffe/"><strong>SPIFFE</strong></a><strong> </strong>which stands for Secure Production Identity Framework for Everyone with its runtime environment <a href="https://spiffe.io/spire/">SPIRE</a>, both of them are based on Sidecar pattern. These sidecars abstract the complexity away from the application and handle functionalities like service discovery, authentication, traffic management, load balancing, circuit breaking, etc.</p><p>In all these standards when it comes to securing our communication it boils down to either X.509 certificate-based authentication or Token-based authentication(JWT). The difficulty in managing the certificates makes X.509 a nonstarter for most applications. In our organization, we use JWT token-based authentication for service to service authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/336/0*cUGCVHsV4urQ0wBA.png" /></figure><p><em>JSON Web Tokens(JWT) are an open, industry-standard </em><a href="https://tools.ietf.org/html/rfc7519"><em>RFC 7519</em></a><em> method for representing claims securely between two parties. The token is composed of a header, a payload, and a signature. </em><a href="https://jwt.io/introduction/"><em>Click here</em></a><em> to know more about JWT</em></p><p>JWT solves both <strong>users</strong> accessing a microservice and a <strong>microservices </strong>accessing other microservices. Once the user successfully logs in using their credentials, a JSON Web Token will be returned. Whenever the user (consumer) wants to access any microservice (producer), the user agent will send the JWT in an authorization header. Upon receiving the token the microservice (producer) will verify the validity of the token and allow the requestor to access the protected resources.</p><p>In the same way, we can achieve service to service communication as well. In this, the consumer will be another microservice. The consumer will send the token in an authorization header to the producer, the producer will verify the token and allow the service to access protected resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HyYlyTnYhjTTmNqe.png" /></figure><p><strong>Chain of service calls</strong>: Let’s say you have Service A calling Service B which in turn calls another service called Service C and so on. Instead of sending the same JWT to all subsequent services, if needed we can create a new JWT token on every service and add additional information like the identity of the calling service, scope of the requester, etc. We can use JWT to carry the complete information and the chain of dependencies that are used for authorization. Authorization plays a major role in the Microservice based system, which I will be covering in my next blog.</p><p>External/Third-party applications can securely access our API’s in two ways,</p><ul><li>API Key</li><li>OAuth Access Token</li></ul><p><strong>API Key</strong> still remains as the most common identifier in many applications. The best thing about API key is its simplicity, you need to log in to any service, get the API token (key) from your setting page and use it in an application via authorization header, custom header, query string, etc. We use the API Key in custom header(X-API-Key) for external users.</p><p><strong>OAuth</strong>: While the API Key is always traveling with your request, OAuth provides an alternative solution. OAuth 2.0 is basically a way to separate the authentication process from the access to the resource and therefore limit the exposure of the credentials. Instead of sending the credentials, the user retrieves an access token which can be used to access the resource. The most common implementation of OAuth uses the access token (which can optionally be set to expire) and refresh token (it&#39;s optional use it to retrieve new access token on expiry).</p><p>Both these options aren’t mutually exclusive. In fact, it’s possible an API could use both API key and OAuth at once.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70b2dde94a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Squad for building Microservices]]></title>
            <link>https://medium.com/@vivekmadurai/agile-squad-for-building-microservices-54a05469ece9?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/54a05469ece9</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[squad]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 07:17:02 GMT</pubDate>
            <atom:updated>2019-08-07T07:17:02.658Z</atom:updated>
            <content:encoded><![CDATA[<p>Smaller teams are more productive, the number of people on a team has a significant impact on productivity. But when the startup grows in business, the team grows as well. <strong><em>Bigger team ≠ Better productivity</em></strong></p><p>How do we grow and remain productive? We would have seen many successful case studies like Jeff Bezos-Amazon’s Two Pizza Teams and Spotify’s Squad Model. In all these cases, we are biased with their success and tend to miss the actual process behind their success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/0*mu6z5DXeh-H0aK3Z.jpg" /></figure><p>We should be more cautious when trying to structure our team while scaling. It needs to match our organization culture or style of working. In this article, I will be sharing some of the insights on how we scaled our development team with the help of <a href="https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf">Squad Model from Spotify</a> and <a href="https://en.wikipedia.org/wiki/Agile_software_development">Agile software development</a> and how microservice architecture made it possible.</p><p>As the product grows in scope and complexity we end up in adding more people with different skill sets at various levels. As a team, we slowly start losing our inherent traits of being a small team. When the team grows the dependability among the developers grows and it ends in chaos and distraction. The first thing we need to do is to separate the concerns by splitting the modules and create various microservices in alignment with the business needs. We never tried to split the modules in order to cut the technical dependencies, we always prioritized the business needs when splitting the modules as microservices. Each microservice should have a clear boundary and business goals.</p><p>Once the microservice boundaries are defined, we started forming an individual team for every microservice. These teams will work as an independent unit and start delivering any functionality from top to bottom. We used to call those teams as Squads as Spotify does. A typical Squad will include,</p><ul><li>1 Product Manager/Owner</li><li>1 Squad Lead/Scrum Master</li><li>1 UX/UI designer</li><li>1 Frontend Developers for a thread(feature)</li><li>1 PWA/Native Mobile Developers(Optional)</li><li>1 Backend Developers for a thread(feature)</li><li>1 QA Manual/Automation</li><li>1 DevOps</li></ul><p>Based on the scope of microservice if needed we shared the QA and DevOps with other Squads. To an extent, we even shared the UX and UI designers. Every squad had a minimum of 5 to 6 members. Our delivery model is designed based on <strong>one feature at a time</strong> for a squad. I have mentioned <strong>1 for a thread</strong> for all developer role. Some of the microservice which plays a major role in business will demand more than one thread(feature) at a time. For those cases, we will increase the developers to <strong>2 threaded</strong> models like (2 Frontend, 2 Backend, and 2 Mobile developers). In our Organization, we have very few squads demands for more than 1 feature at a time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZBE-g7ve7bFdSQSHW3EPDA.png" /><figcaption>Team Structure in a Squad</figcaption></figure><p>Apart from these, we do have chapter leads for UX/UI, Frontend, Backend, Mobile, QA, and DevOps. Currently, we don’t have a Tribe model. I hope that would be part of our next scaling.</p><p><strong>Brief on our Process:</strong> The Product Manager will create the spec(Requirement) with UX and UI screens for a feature and the Squad lead will work on the technical design and documentation for the same. Once the document is signed off, the development(Sprint) starts for that feature and on completion and after testing(QA) and user evaluation(UAT) the feature finally gets deployed to production. In the meantime, the Product Manager will start the next feature spec and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/0*NhJBgIpB895KsJYm.png" /><figcaption>Requirement-Release cycle</figcaption></figure><p>In this approach, we don&#39;t follow the standard sprint cycle, our pipeline will be based on the size of the feature and every feature will get rolled out from 2 days to 2 weeks one by one. Every squad will have two pipelines one for the feature rollout and another for the bug fixes. These two pipelines will function independently.</p><p><strong>Conclusion:</strong> Form a lightweight Agile process within every Squad which includes daily standup, feature-based sprint planning, and feature-based QA and release process. The two major changes which we did in our organization improved our release process tremendously,</p><ul><li>Microservice based squad model</li><li>From 2 weeks sprint to feature-based sprint</li></ul><p>These two changes gave us the flexibility for the complete squad to focus on one thing at a time both in terms of business as well as technology. Based on our employee survey every individual supports this model and its working well in our Organization.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a05469ece9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ubiquitous Computing]]></title>
            <link>https://medium.com/@vivekmadurai/ubiquitous-computing-6dd3685f18e7?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6dd3685f18e7</guid>
            <category><![CDATA[pervasive]]></category>
            <category><![CDATA[next-generation-computing]]></category>
            <category><![CDATA[evolution-of-computing]]></category>
            <category><![CDATA[ubiquitous-computing]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Sun, 25 Mar 2018 16:31:18 GMT</pubDate>
            <atom:updated>2018-03-25T16:34:32.416Z</atom:updated>
            <content:encoded><![CDATA[<p>In the evolution of computing, in next 10 years Ubiquitous/Pervasive computing is going to rule the world. Ubiquitous computing is all about a ultra intelligent personal agent. A agent which uses the computer power to help in maximising the users productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/528/1*E76K-E-Zto8SdqgBGNR12Q.png" /></figure><p>The market is pushing lot of smart devices day on day and as consumers we are knowingly or unknowingly moving toward next evolution in computing. Below are some of the Ubiquitous computing platform which is getting evolved to next level,</p><ul><li>Garmin IQ, Android wear</li><li>Smart TV: Apple TV, Android TV</li><li>Google Chromecast, Amazon Fire</li><li>Virtual reality: Microsoft Hololens, Google Glass</li><li>Augmented reality: Tango</li><li>Google’s Machine learning API</li></ul><p>Assume someone who takes care of your health and manages all your personnel activities. Lets say you have booked a flight ticket to travel to a place in the morning. Due to some issues if the flight gets cancelled in might night, think about a personal agent who can automatically detect the flight cancellation and book a best alternate flight for you. What if it also detects the weather in arriving place based on your landing time and alerts you to pack a jerkin, hand gloves etc., Just think about it, all these are happening while you are in the sleep and how powerful if the computing becomes ubiquitous. The beauty is we have already crossed half a distance in achieving ubiquitous computing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6dd3685f18e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality, Time and Money]]></title>
            <link>https://medium.com/@vivekmadurai/quality-time-and-money-39278f990092?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/39278f990092</guid>
            <category><![CDATA[triangle-of-constraint]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[money-management]]></category>
            <category><![CDATA[quality]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Sun, 25 Mar 2018 16:08:12 GMT</pubDate>
            <atom:updated>2018-03-25T16:11:54.256Z</atom:updated>
            <content:encoded><![CDATA[<p>Quality, Time and Money are the three main factors to be considered in any project management decisions. These are usually called as triple constraint or project management triangle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/0*nG_M3Wb_5Hzm6nEr.png" /><figcaption><a href="http://smarterwebsiteowner.com/the-project-management-triangle/">http://smarterwebsiteowner.com/the-project-management-triangle/</a></figcaption></figure><p>As you can clearly see from the above image you can pick any two but you cannot have all three. A good leader will always try to priorities on these three factors for any project, it can never be ‘it depends on ….’</p><p>People in general will always ask for all the three, its the pure responsibility of that lead/manager in helping them to understand that they can have only two but not all three. But a smart leader will always focus on Quality and asks for more time and more money, the money in this case is resources needed to deliver the project.</p><p>Quality = Time x Money</p><p>You can still ask why more time and more money, as per the above triangle of constraints with more money we can still deliver in less time with good quality. But in reality this will not get applied on work which mainly focuses on creativity and innovation.</p><p>Sacrificing quality and delivering the project with low cost and less time is not the correct solution, in the long run the bad quality will suck your time and money anyway. Investing time in quality will always save money.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39278f990092" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fitness as a Culture in your Workplace]]></title>
            <link>https://medium.com/@vivekmadurai/fitness-as-a-culture-in-your-workplace-ef9e5ada4696?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef9e5ada4696</guid>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[fitness]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 09:15:28 GMT</pubDate>
            <atom:updated>2018-03-14T05:18:42.016Z</atom:updated>
            <content:encoded><![CDATA[<p>Culture inside a workplace helps people to stay on the same page and makes things easier to reach company goals and achieve a better lifestyle at work environment. Culture always evolve around people and its strongly dependent of how they react to your environment. People bonding plays a major role in building a successful culture, people bonding is always a challenge in any organization. In this article I will be sharing my experience in achieving people bonding via fitness activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*4Ry55A3S502BboBes46BHw.jpeg" /></figure><p>Have you heard about “Sport’s Spirt”, sportsman spirit is the act of accepting success with humility and accepting defeat cheerfully. This will only happen if we have strong bonding/relationship with in the team. Any sports game brings this quality as a default standard. Fitness activities also helps in building a good relationship between people, which helps to create a better workplace culture.</p><p>We all know fitness is a critical factor in every individuals overall health. Encouraging people to spend some time on their health via some fitness activities like yoga, running, cycling, playing games etc., will not only help their physical fitness but also mentally it will help them from getting rid of their stress and other mental illness. When it comes to promoting fitness in your workplace we always worry about dedicated facilities, setting up bootcamps, training classes, organized teams etc., but in reality all these are not needed we can achieve it with some simple steps likes,</p><ul><li>Offer some flexible time on work hours to accommodate psychical activity</li><li>Post some signs around elevator to take stairs instead of elevators</li><li>Start a employee fitness group like cycling, swimming, running etc.,</li><li>Provide shower/change room on-site for employees</li><li>If possible arrange some quarterly events to encourage fitness</li></ul><p>We always need some spark of energy to stay and get things done, its every companies responsibility to set a positive workplace culture that promotes the overall environment of their workplace, which actually encourages everyone in the company to take care of themselves and achieve better productivity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef9e5ada4696" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frontend in Microservice Architecture]]></title>
            <link>https://medium.com/@vivekmadurai/frontend-in-microservice-architecture-1e5bfa08e3e4?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e5bfa08e3e4</guid>
            <category><![CDATA[web-components]]></category>
            <category><![CDATA[monolithic]]></category>
            <category><![CDATA[micro-frontends]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Fri, 09 Mar 2018 09:11:44 GMT</pubDate>
            <atom:updated>2018-03-09T12:06:25.611Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a Microservice based architecture these days seems to make sense for a lot of big and distributed applications. This style of architecture enables the monolith team to get split to independent team which helps in improving things like scalability, complexity of the code, rolling out to production etc.,</p><p>We normally exclude frontend application from these microservice architecture. In this article I will be sharing my thoughts on different frontend approaches in microservice architecture.</p><ul><li>Monolith Frontend</li><li>Modular/Component based Frontend</li><li>Micro Frontend</li></ul><p><strong>Monolith Frontend</strong>, normally we will be building frontend by a separate team which grows and maintained separately from that of microservice backend which is referred as Frontend Monolith. We used to call this approach as Model View Controller(MVC) architecture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*l0sfQzUKdm8572t3Uwojwg.png" /></figure><p><strong>Micro Frontend</strong>, which will be part of the same individual team who builds microservice backend. Each team will own a unique business component and develops its end to end starting from user interface to database layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*nQcL0KLROHsefxXp5wsT9Q.png" /></figure><p>Choosing Micro frontend architecture, there are several benefits in applying micro frontend to our application like,</p><ul><li>Technology agnostic</li><li>Moving integration part of frontend</li><li>Isolated team for development and deployment</li><li>Individual testing and less regression issues.</li></ul><p>To know more about building micro frontend apps please read <a href="https://medium.com/@tomsoderlund/micro-frontends-a-microservice-approach-to-front-end-web-development-f325ebdadc16">Tom’s blog</a> on microservice approach for frontend web development.</p><p><strong>Component based Architecture(CBA)</strong>, this become popular after Facebook released React.js in 2013. In this approach we will break our large user interface into individual self sustaining components. Each components will have their own structure, own method and own API’s which intern can be reused inside other components.</p><p>We need to be aware of these options before taking a decision on your web application architecture. From the above three micro frontend and component based frontend is the latest and monolith is no more a option.</p><p><strong>When to use Micro frontend</strong>,</p><ul><li>Migrating legacy app in isolation, while they are still being used. Adding new feature in new framework without disturbing the existing one.</li><li>Helps different frontend frameworks to co-exist(like one in Angular, one in React, Vue, Ember etc.,)</li></ul><p>There a some common issues in building micro frontend application like,</p><ul><li>Assets loading(loading libraries), ends up in library conflicts</li><li>Common styling across micro apps</li><li>Upgrading or altering the base framework like (Angular or React)</li></ul><p><strong>Component based</strong> approach is best suited for application which gets build from the scratch over a single base framework like Angular or React or Vue etc., In this approach we will be building and deploying individual components separately.</p><p><strong>Conclusion</strong>, Even with clear microservice separation at backend layer its unable to separate our frontend application into multiple entirely separate application. Unlike backend service we cannot build our micro frontend to be completely independent from other micro frontend. We need to maintain a consistent look and feel across all the components and the application should behave as single application.</p><p>Although a total split of your application may not be possible, its still possible to have a multiple team working on a separate parts of your application. Instead of splitting your application as pure micro frontend we can still split our application into separate components which can be developed and maintained separately by different teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e5bfa08e3e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Evolution from 1.0 to 3.0]]></title>
            <link>https://medium.com/@vivekmadurai/web-evolution-from-1-0-to-3-0-e84f2c06739?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e84f2c06739</guid>
            <category><![CDATA[evolution]]></category>
            <category><![CDATA[web-evolution]]></category>
            <category><![CDATA[web2]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Sat, 17 Feb 2018 05:58:31 GMT</pubDate>
            <atom:updated>2018-02-21T08:47:03.998Z</atom:updated>
            <content:encoded><![CDATA[<p>World Wide Web is the primary tool used by billions of people to share, read, and write information to interact with other people via internet. World Wide Web made much progress since its advent, in this article I will be sharing a brief idea of the evolution happened in web from web 1.0 to 2.0 and to web 3.0.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r6Nyzggj0Avf2EHgLgLIgw.png" /><figcaption><a href="http://www.mdpi.com/futureinternet/futureinternet-04-00852/article_deploy/html/images/futureinternet-04-00852-g001.png">http://www.mdpi.com/futureinternet/futureinternet-04-00852/article_deploy/html/images/futureinternet-04-00852-g001.png</a></figcaption></figure><p>The first version of web <strong>Web 1.0</strong> also referred as Syntactic web or read only web is the era(1990–2000) where the role of a user is limited to reading information provided by the content producers. There is no option given for user or consumer to communicate back the information to the content producers. Example of Web 1.0 are static web sites and personal sites.</p><p>The <strong>Web 2.0</strong> also referred as Social Web or read-write web is the era(2000–2010 and continues even now) which facilitates interaction between web users and sites which intern allows users to communicate with other users. In this era every user can be a content producers and content is distributed and shared between sites. Some of the famous Web 2.0 applications are Facebook, Youtube, Flickr, Twitter etc., The web technologies like HTML5, CSS3 and Javascript frameworks like ReactJs, AngularJs, VueJs etc., enables startups to innovate new ideas which enables users to contribute more in this Social Web. Web 2.0 is build around the users, producer just need build a way to enable and engage them.</p><p>The <strong>Web 3.0</strong> also referred as Semantic Web or read-write-execute is the era(2010 and above) which refers to the future of web. In this era computers can interpret information like humans via Artificial Intelligence and Machine Learning. Which help to intelligently generate and distribute useful content tailored to a particular need of a user.</p><ul><li>What if computers can understand meaning behind information</li><li>What if they can learn “what we are interested in”</li><li>Then they can help us find what we want</li><li>It can recognise People, Place, Events, Companies, Product, Movies etc.,</li><li>It can understand the relationship between things</li></ul><p>Some of the examples of web 3.0 are <a href="https://www.apple.com/ios/siri/">Apple’s Siri</a>, <a href="https://cloud.google.com/products/machine-learning/">Googles Cloud API</a>, <a href="http://wolframalpha/">Wolfram Alpha</a>.</p><p>The <strong>Web 2.5</strong> is the concept to address the practical and real evolution which we are currently seeing in our era 2010–2020 between Web 2.0 and 3.0. On our way to Web 3.0 some of player like <a href="https://aws.amazon.com/">Amazon</a>, <a href="https://cloud.google.com/">Google</a>, <a href="https://www.salesforce.com/">Salesforce</a>, <a href="https://kissflow.com/">KiSSFLOW</a> etc., provides a service model in Cloud computing for developers to create web applications for their users to connect them on any devices, anytime and anywhere.</p><p>Web 2.5 is majorly focussing on mobile computing and evolution in mobile technologies. As we all know mobile computing plays a major role in engaging larger audience via native apps as well as mobile web apps, we can find more and more apps getting into mobile market to establish their presence by addressing mobile users. Some of the technologies which got introduced in this era where Progressive Web Apps(PWA), Accelerated Mobile Pages(AMP) etc., To make in conceptually clear we can call Web 2.5 as the convergence between Social and Semantic web.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e84f2c06739" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Progressive Web Apps]]></title>
            <link>https://culture.kissflow.com/why-how-progressive-web-apps-works-752a545ea645?source=rss-deec4a332fb7------2</link>
            <guid isPermaLink="false">https://medium.com/p/752a545ea645</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[native-app]]></category>
            <category><![CDATA[service-worker]]></category>
            <category><![CDATA[web-apps]]></category>
            <category><![CDATA[pwa]]></category>
            <dc:creator><![CDATA[Vivek Madurai]]></dc:creator>
            <pubDate>Sat, 17 Feb 2018 01:40:25 GMT</pubDate>
            <atom:updated>2018-02-21T07:23:54.129Z</atom:updated>
            <content:encoded><![CDATA[<p>This article is in continuation with my previous article on <a href="https://medium.com/@vivekmadurai/mobile-web-vs-native-app-2651b6b06f4d">Mobile Web vs Native App</a>, its very clear that mobile web get more number of new visits when comparing to installing new apps. But due to web apps reliability in slow network and low in engagement users churn out quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*i8XOLKt1YOtHl7_g26wfEQ.png" /></figure><p>In this article we will be seeing why we need PWA and how it helps web application to be Reliable, Fast and engage users like native apps.</p><p>Lets start with what wrong is native app,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*CXVLmsqje3jkMZ6RIN_4bA.png" /></figure><ul><li><em>High cost involved in building and delivering individual native apps</em></li><li><em>Difficultly in sharing the information to outside world.</em></li><li><em>Reaching to larger audience by SEO is not possible</em></li><li><em>Cost in getting a user to install your app is high(acquisition cost)</em></li></ul><p>Whats wrong with web app,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/168/1*w_rGcbRP3Mb8aCZWYoHnjQ.png" /></figure><ul><li><em>Apps reliability due to slow mobile network</em></li><li><em>User experience like smoothness, animation</em></li><li><em>Offline access</em></li><li><em>Low in engagement(no push notification)</em></li><li>No access to device hardware</li></ul><p><strong>Why PWA,</strong></p><ul><li>Combines best of the web and best of the apps</li><li>Reliable and loads quickly as native web app, but delivered through the web</li><li>They roll and animate smoothly, they can engage users via push notification</li><li>They are integrated as part of mobile home screen and can be loaded as top level full screen app</li><li>PWA helps mobile web in achieving native apps capability</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wzZNkZCNCzE12yjU." /></figure><p><strong>How PWA</strong> <strong>works, </strong>technologies used to build a full fledged progressive web applications are,</p><ul><li>App Shell architecture (Loads Instantly)</li><li>Https (Security)</li><li>Service Worker (Caching)</li><li>Web App manifest (Visibility)</li></ul><p>Application Shell or <a href="https://developers.google.com/web/fundamentals/architecture/app-shell">App Shell</a> architecture is the minimal HTML, CSS, Image and javascript needed to power your initial user interface, static assets needed to render your first paint. If you are building a modern single page application(SPA) then you would definitely have something similar to this which we are calling it as App Shell. These static assets can be cached at first visit via service workers so that they get loaded instantly on repeated visits.</p><p>A <a href="https://developers.google.com/web/fundamentals/primers/service-workers/">service worker</a> is script that runs in background, separate from that of your web page. Service worker can intercept a network request made for a page and returns a response retrieved from the server or retrieved from local cache. It helps in caching your app shell and data, so that the app can work in online as well as offline making reliable and smooth user experience. If you are interested in lifecycle of service worker click <a href="https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/557/1*DX0FQ74R_G27p2gAI87FaA.png" /></figure><p>The <a href="https://developers.google.com/web/fundamentals/app-install-banners/">Web App manifest</a> is a metadata defined as JSON file which gives ability for the developer to save a sites’s bookmark to users home screen. It has unique icon and name so that users can add a visibility of your app to their home screen like native app icon. This also includes things like splash screen, theme color, display mode, orientation etc., to make better appearance in launching your app.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=752a545ea645" width="1" height="1" alt=""><hr><p><a href="https://culture.kissflow.com/why-how-progressive-web-apps-works-752a545ea645">Why Progressive Web Apps</a> was originally published in <a href="https://culture.kissflow.com/">Kissflow Culture | Explore Our Butterfly Effect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>