Domain Driven Design helps to solve mircoservices bounded context and allows you to find out the domain of each service and how they connect to each other while Hexagonal architecture is a framework and pattern for software design that we used to implement the service. The idea behind it is to put inputs and outputs at the edges of your service implementation. In doing so, you isolate the business domain of each service from outside concerns. Having inputs and outputs at the edge means you can swap out its persistence layer or integration layer without impacting to the core business domain.

Public Speaker and IT Advisory of Enterprise Architecture and Solutions to executive levels with 15 years of experience from MNC.
A passionate advocate on empowering agile culture and promoting revolutionary architecture to Enterprise Cloud Adoption Strategy, Cloud Migration & Modernisation, Enterprise DevOps Transformation, Cloud Data Lake Solutions and Cloud Native Transformation.
A strong technical lead and successfully delivered multiple digital transformation projects across APAC market.
LinkedIn Link: https://www.linkedin.com/in/jun-ni-thoughtworks/

I have had been working closely with the customers to deliver the Digital Transformation projects that make a significant impact on their business in banking, Insurance, telecom, and retail industries.
Worked with different customers across multiple Geographies and Cultures – USA, Singapore, Dubai, India, EU, Australia, Indonesia, Thailand, Taiwan, China, and Kenya.

Area of expertise:
API Centric Integration, Distributed Integration, Container Adoption, Enterprise Architecture, Microservices, Cloud Native App Development, Istio, Kafka, Message Oriented Middleware, CloudEvents, Streaming, SSO/federation - different data sources, PaaS, SaaS, TIBCO Stack, SOA governance

Wondering how to scale and increase reliability for your system with event-driven architecture?
In this session, we provide an overview of event-driven architecture and the advantages it can bring you and your business.
We also cover architectural patterns, and we provide a demo that showcases event-driven architecture on AWS in action.

Donnie Prakoso is a software engineer, self-proclaimed barista, café racer enthusiast, and Senior Developer Advocate at AWS. With more than 16 years of experience in the technology industry, from telecommunications, banking to startups. He is now focusing on helping the developers to understand varieties of technology to transform their ideas into execution. He loves coffee and any discussion of any topics from microservices to AI/ML.

Exploratory testing is the pinnacle of the test pyramid for a reason. It is perahps the most important form of testing before the release of a system under test. However, it is also perhaps the type of testing that provides the least ROI for a team. Why? Because it is hard to define, track and execute in a team. My talk will walk through ways to tame Exploratory Testing through visual tools and methods - bringing back its value to the test cycle.

One of the important tenets of Continuous Delivery is test automation which helps in getting the quick feedback on product quality especially from regression standpoint.

Though nobody disagrees with the important of test automation, a huge percentage of teams and orgs don't do any test automation. As and when it happens there, it's always in reactive mode. People automate tests when it's already too late.

If you investigate further, you see people not doing it because of following reasons:

* The test code sometimes is twice or thrice the size of base code.
* The team doesn't know how much test coverage is enough. That's the reason they target 100% code coverage.
* Even after doing good amount of test automation, many teams are still not sure if they really trust automation suite

This session helps in understanding why exactly above issues happen and what can we do about them.

A research from Google says, client side processing takes more time than the server side. With increasing JS speed by the browser, performance is still an issue.

Factors affecting performance may range anywhere from system cache, file types and size, bandwidth restrictions, website speed on local computers and many more. These could be measured by Initial page load performance in terms of functional elements on the page, basic text and layout or the download time.

Considering these factors, Client side performance testing in any application has become predominant in recent times.

Reducing the front end loading time of the application by 40% can increase the performance of the application. This helps us in finding ways to conclude - Is the issue occurring from Client-side or Server-side?

Metrics to be analysed
Full page load time
First reaction when loaded
HTML resources,CSS files, Images load time - DOM content ready
Javascript file load time
HTTP response time and HTTP response status.

Locust is an open source load-testing tool written in Python, which mimics the application’s user behaviour, and then run the tests at scale to help find bottlenecks or other performance issues

In this interactive 45 minute session, get ready to learn exciting ways to set up an initial test suite to measure performance of your mimicked user journeys.

Takeaway:
Why is client side performance testing the need of the hour
Metrics to be analysed
Locust to measure performance

Loges R is currently a QA consultant at ThoughtWorks, India. His focus is mostly on delivering the products with utmost quality. He is always interested in leveraging automation solutions to build a robust wall around the defect leakage.

He has predominantly worked in UI and API automation frameworks using different tools. Now he is venturing into non functional testing to unleash more value in the projects that he is working on.

Akilaa S is currently a Consultant and a Quality Analyst at ThoughtWorks,India. She has been part of End to End Customer journeys catering Quality as a mindset throughout the lifecycle. She is also inclined towards Open Source Contribution and exploring Test Automation tools.

She is now interested in working on non-functional testing and exploring multiple opportunities being an enthusiastic learner. She is from Coimbatore, India.

Overview of AWS Developer Tools like AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy and AWS CodePipeline.

Implementation of CI CD workflow with a 3 stage CodePipeline;

1. Pull the source code from two different repositories for WebApplication & Infrastructure Code

2. Compile the code, generate artifact and upload to S3

3. Spin up the infrastructure using Cloud Formation Template followed WebApplication Deployment using the Artifact stored in S3.

Walkthrough of buildspec and appspec files, Debugging Build & Deployment, Rollback of deployment and how to gauge the metrics to DevOps.

Welcome to this No brainer CI CD talk where I am going to talk about what is the ideal setup for a CI CD and what all one needs to do to implement the same. I’ll also talk about branching strategy as well as about trunk-based development.

In recent years, one term that has gained significance in the field of Quality Assurance is “Penetration Testing”. Many new tools have been developed to unearth security loopholes within the system.

In this session, I will walk through the different stages of any successful automation testing and a few open source tools used at each stage. I will also shed some light on open source automation scripts and frameworks followed by a pen testing demo.

Rajas Save is an expert security analyst and a penetration testing enthusiast. His extensive experience in the computer and network security industry includes work in the fields of malware analysis and research, sandboxing and incident response. Rajas has been involved in complex vulnerability scans and penetration tests. He is also an TedX speaker and has authored multiple publications concerning malware analysis and threat detection

An introduction to serverless architecture aimed at a wide target audience. The talk covers the strategic impact such as financial and security considerations which will be interesting to executives and managers, right through to some of the more technical aspects such as DevOps and design patterns which will be interesting to tech leads and developers interested in upskilling to serverless.

Thomas Smart is an innovation consultant that has been active in technology for 17 years, 10 of which in Asia. He holds multiple AWS certificates and in 2019 was invited to their exclusive Partner Ambassador program. He works with startups and enterprises on their innovation and cloud projects, and enjoys writing. His Latest book "Serverless - Beyond the Buzzword" will be out later this year.

Load Tests Plans and Practices
Agile Methodology and Load Tests
Load Test Tools
Load Test Environment Set up
Planning Load Tests
Identify Test Data to simulate Production
Results analysis and Extrapolation.
Load Tests in Cloud

State Machines
Global Variable
Overall flow of the framework.
Answer any questions on the framework

An experience RPA developer with a Masters degree in Business Information Systems from Monash University and a passion for creating bots.

Since its release to the public in 2015, an increasing number of developers are building new APIs with GraphQL instead of more traditional REST approaches. In this talk, I’ll give you a short history of GraphQL, explain it’s design philosophy and benefits, and show a quick demo of how to easily create and deploy GraphQL APIs on AWS.