About Website

I am using pekkakorpi-tassi.fi website as an opportunity to experiment, explore and present different approaches to technical challenges. Technical implementation of the site should not be in all cases viewed as a best practice exemplar from a solution architecture perspective. Instead, the website and the content therein serve as powerful example to illustrate the differences between what is possible, what constitutes best practices, the compromises involved, and the tangible outcomes of developing and deploying contemporary ICT solutions to be run in the Public Cloud. You can check the rough architecture of pekkakorpi-tassi.fi website below:

To develop and deploy pekkakorpi-tassi.fi website and the content therein I am using tools, technologies and practices such as:

DevOps, Kanban
Visual Studio Code
Domain, DNS Server, SSL/TLS Certificates (HTTPS)
- AWS managed certificates with CertificateManager
- Self-managed certificates with Cerbot
Git, Trunk Based Development, Pull Requests
Conventional Commits, Semantic Versioning, Change Log
- commitlint
Everything as Code, TypeScript
- Infrastructure, Automation, User Interface, Application, Documentation
Node.js and TypeScript, Markdown
- typescript-eslint, markdownlint
AWS Infrastructure Automation
- AWS CDK 2.0, CloudFormation, CodeCommit, CodePipeline, CodeBuild, ECR
Various AWS IaaS, PaaS and SaaS services
- AWS Organizations
- IAM
- Billing and Cost Management, Budgets, SNS
- Route 53, Certificate Manager
- CloudFront, API Gateway, CloudWatch
- S3
- VPC, Internet Gateway, NAT Gateway, Subnet, NACL, NSG, Route Table, ENI, ElasticIP
- EC2
Docker Containers, Docker Swarm Orchestration
Jekyll website generator, Just the Docs Jekyll theme
Jupyter Notebook, Python, Pandas (toolkit for data engineering)
Swagger (API documentation)
S3, Google Drive and GitHub for content delivery