Jacek pracuje z chmurą obliczeniową AWS od 2008 roku, na początku jako niezależny ekspert/administrator AWS, obecnie architekt AWS/właściciel firmy, która jest pierwszym AWS Partnerem w Polsce.
Wykorzystując swoje wieloletnie doświadczenie, pomaga klientom w różnej wielkości projektach, od start-ups po rozwiązania typu Enterprise, we wdrażaniu najlepszych rozwiązań na chmurze AWS, które spełnią wszystkie wymagania biznesowe.
2. About us
• 11+ years of professional experience in Unix
and 7+ years in Cloud Computing administration
• Founder at LCloud – “Linxsys Cloud”, AWS Partner
from 2012, first AWS Partner in Poland
• We are after 150+ AWS projects
• Enterprise experience:
• Email: jacek.biernat@linxsys.pl
3. Design for Failure – High Available
solution
One of the major reasons for migration to Cloud
Computing:
- Avoid single points of failure
- Assume everything fails
Our goal: Application should continue to
function even if the underlying physical
hardware fails or is removed or replicated
7. Stateless solutions
Do not modify the application code:
- Network-Attached Storage (NAS) solution with
Raid 1 via network: DRBD, GlusterFS
8. Stateless solutions
Do not modify the application code:
- Network-Attached Storage (NAS) solution with
Raid 1 via network: DRBD, GlusterFS
- Amazon Elastic File System (EFS)
9. Stateless solutions
Do not modify the application code:
- Network-Attached Storage (NAS) solution with
Raid 1 via network: DRBD, GlusterFS
- Amazon Elastic File System (EFS)
- Mount Amazon S3 bucket as file system: s3fs,
s3ql
10. Stateless solutions
Do not modify the application code:
- Network-Attached Storage (NAS) solution with
Raid 1 via network: DRBD, GlusterFS
- Amazon Elastic File System (EFS)
- Mount Amazon S3 bucket as file system: s3fs,
s3ql
- Amazon Elastic Load Balancer with sticky
session (sometimes is enough)
18. Proposal of solutions when a region is
not available
• RTO and RPO is max. 24 hours
– Amazon Cloudformation templates
– Copy backup to second region
19. Proposal of solutions when a region is
not available
• RTO and RPO is max. 24 hours
– Amazon Cloudformation templates
– Copy backup to second region
• RTO and RPO is max. 5 minutes
– Amazon Cloudformation templates
– Configure Replication data between regions
20. Proposal of solutions when a region is
not available
• RTO and RPO is max. 24 hours
– Amazon Cloudformation templates
– Copy backup to second region
• RTO and RPO is max. 5 minutes
– Amazon Cloudformation templates
– Configure Replication data between regions
• Keep two active environments Master-Master
– Use a queue solution (Amazon DynamoDB, SQS)
31. Micro-services and elastic resource
pools with AWS
• Each service is decoupled from the rest and
deployed individually
• We run multiple services on the same
instances
• An automated deployment system takes care
of all services lifecycle details