User Tools

Site Tools


start

This is an old revision of the document!


Backlog

Java Magazine Read all
Write and publish all
Togaf Implement, publish a Digital Twin projects according to TOGAF. All layers up to implementation.
SAFE for Architectshttps://www.scaledagile.com/training/calendar/?course_id=SAFe+for+Architects
K8s on a PI farmhttps://falksangdata.no/wp-content/uploads/2020/11/running_kubernetes_on_your_raspberry_pi_homelab.pdf
https://aporcupine.com/2020/03/pi4-kubernetes-cluster/
Job scans * Find and do certificates

Write and publish

  1. concentrate on Application Design aspects of cloud. Less Infrastructure.
    1. example serverless application
      1. on java-native
        1. project structure for gradle
        2. deployment to multi-region
        3. routing
        4. api GW for lambdas
      2. database? DynamoDB Global?
      3. add CQRS
    2. various clouds
    3. K8s and CloudNativeFoundation
    4. Serverless
    5. Containers
    6. Business logic and Mesh
    7. Aspects like Streaming, consistency, liveness.
  2. Event-sourcing architecture on AWS
    1. Principles and Patterns, implement with services, cost and scalability
      1. Principles: how it relates to well arch framework
      2. Principle: Space Decoupling / Location Transparency: service discovery
      3. Principle: Time Decoupling: async message delivery
      4. Principle: non blocking I/O operations for efficiency. Idempotent operations. Reactor pattern. see https://stackoverflow.com/questions/9138294/what-is-the-difference-between-event-driven-model-and-reactor-pattern
  3. Compare some popular CI/CD - GitLab, CodePipeline, Fastlane, analyze flows like here: https://www.linkedin.com/pulse/fast-lane-aws-pipelines-roman-naumenko/
  1. Service isolation, for resource/limit/operational isolation (need to know)
    1. in K8s or
    2. using Accounts as units (service per account)

Architecture

  1. Archimate
  2. Vaughn Vernon - Implementing Domain-Driven Design - 2013
    1. Event Sourcing
    2. DDD
    3. Domain events
    4. “Event Storming” technique
    1. ETL - Extract-Transform-Load
    2. S.O.L.I.D principle https://en.wikipedia.org/wiki/SOLID_(object-oriented_design)
      1. enables loose coupling of modules

Experiment for Job

  1. Firewall
    1. Checkpoint
    2. WAF
  2. Azure
    1. EntraId
      1. integrate app with EntraId
    2. API-Manager
    3. Service Bus (Amazon SNS)
    4. Event Hubs (Amazon Kinesis)
    5. Data Driven services, ETL etc.
  3. Kubernetes project on the PI
  4. “Service-Mash” und K8s. With Spring-Boot.
    1. Istio and SPring Boot micro-services
    2. K8s Rancher
  5. camunda bpm
  1. Cloud native Java-stack
  2. security certifications (ISO2700x, SOC 2)
  3. security automation (SAST/DAST)
  4. DDD book
    1. Problem Domain - hello w
    2. Solution Domain - hello w

Tooling to try

Frameworks to try

  1. ВЕб Технологии, алгоритмы, Hadoop, MapReduce etc. http://habrahabr.ru/company/mailru/blog/258045/

Technologies to understand/try

Programming

UI

  1. Flutter - Google framework for native cross platform apps
  2. Интерфейсный дайджест http://habrahabr.ru/company/mailru/blog/183950/
  3. Google Frontend Developer - https://br.udacity.com/
  4. Martin Fowler's GUI Architectures - http://martinfowler.com/eaaDev/index.html

Interesting

Methodology

  1. OKRs – Object Key Results

Conferences

start.1720347780.txt.gz · Last modified: by skipidar