Book Image

Building Serverless Architectures

By : Cagatay Gurturk
Book Image

Building Serverless Architectures

By: Cagatay Gurturk

Overview of this book

Over the past years, all kind of companies from start-ups to giant enterprises started their move to public cloud providers in order to save their costs and reduce the operation effort needed to keep their shops open. Now it is even possible to craft a complex software system consisting of many independent micro-functions that will run only when they are needed without needing to maintain individual servers. The focus of this book is to design serverless architectures, and weigh the advantages and disadvantages of this approach, along with decision factors to consider. You will learn how to design a serverless application, get to know that key points of services that serverless applications are based on, and known issues and solutions. The book addresses key challenges such as how to slice out the core functionality of the software to be distributed in different cloud services and cloud functions. It covers basic and advanced usage of these services, testing and securing the serverless software, automating deployment, and more. By the end of the book, you will be equipped with knowledge of new tools and techniques to keep up with this evolution in the IT industry.
Table of Contents (10 chapters)

Adding logging

We should also log when there is an authentication issue. Let's add a Logger to our Handler class:

private static final Logger LOGGER = 
Logger.getLogger(Handler.class);

Then, let's modify the block where we catch the exception:

... 
  } catch (UserNotFoundException userNotFoundException) { 
    policyEffect = PolicyStatement.Effect.DENY; 
    LOGGER.info("User authentication failed for token " +  
      authenticationToken); 
  } 
.... 

Maybe at this point, we can create another test to check whether our Handler class is returning the denial policy. We need mocking for that because we will create a mock AuthenticationInput object, and easymock and powermock are good libraries for that. Let's add it to our main build.gradle file to test dependencies:

allprojects { 
  dependencies { 
    ... 
    testCompile group: 'org.easymock...