Skip navigation

Hello Everyone,

 

These are few nice articles and references which i've come across while learning about serverless architecture, trend what made it evolves and the patterns where it is mostly suitable. It's evolution of cloud-computing coupled with event-driven architecture style.

 

Needless to say that you've to refer and keep the principles outlined in https://12factor.net/ always handly in implemented these use cases

 

https://martinfowler.com/articles/serverless.html - it's an amazing article and points to good referencesc (source: martin fowler website)

https://www.slideshare.net/jedi4ever/from-serverless-to-service-full-how-the-role-of-devops-is-evolving

https://developer.ibm.com/opentech/2016/09/06/what-makes-serverless-attractive/ - provides an explanation of how various current things abstracted for developer and helps in focusing on value-driven business development

https://www.slideshare.net/DanielKrook/openwhisk-a-platform-for-cloud-native-serverless-event-driven-apps

 

Operational aspects of serverless architecture implementation

https://charity.wtf/2016/05/31/wtf-is-operations-serverless/

https://charity.wtf/2016/05/31/operational-best-practices-serverless/

 

For Youtuber's

https://www.youtube.com/watch?v=sYRiTZ47Cao

 

Apache OpenWhisk as servlerss cloud computing infrastructure.

https://openwhisk.apache.org/

 

Serverless Framework for building serverless architecture using AWS Lambda, Azure / Google cloud functions or IBM OpenWhisk

https://serverless.com/

https://github.com/serverless/serverless

https://github.com/serverless/guide - open-source guide to understand about serverless architecture and how to use framework to build one to be serverless organization

 

For event-driven implementation reference go to http://eventuate.io/usingeventuate.html

If you're confused between SSO and centralized authentication mechanism go through these articles to get basic understanding. They help you to understand the difference between two and when to use what. This will also provide you insights on when you've to opt for which kind of approach and solution.

 

SSO as such doesn't maintain its own user repository and relies on the application for user management services. Centralized authentication services maintain user data repository which can be shared across applications (ex: LDAP, AD). SSO technique issues and validate taken, its mainly performing assertions based on protocols like SAML, JWT or OpenID connect.

 

Article 1 : https://blogs.forgerock.org/petermajor/2013/02/single-sign-on-the-basic-concepts/ very concise and simple explanation on basic building blocks of SSO infrastructure and flow of request and response

Article 2 : https://stormpath.com/blog/sso-vs-centralized-auth explains that centralized authentication is the first-step towards SSO implementation.

Article 3 : https://auth0.com/blog/what-is-and-how-does-single-sign-on-work/ provides a very simple explanation of SSO and various alternatives. You can also download the e-book at the end of article.

Article 4 : https://www.codeproject.com/Articles/429166/Basics-of-Single-Sign-on-SSO  and https://blogs.forgerock.org/petermajor/2013/02/single-sign-on-the-basic-concepts/  provide basic understanding of SSO working in simple manner

Article 5 : https://blogs.forgerock.org/petermajor/2014/05/cross-domain-single-sign-on/ provides explanation of achieving cross-domain SSO (typically called, CDSSO).

 

Additional info on implementing 'Remember Me' feature can be found here