For some time now I am working quite heavily on AWS in my current project. And of course we try and give our systems the shape of micro services (who wouldn't?). When using micro services architecture it is very often a good practice to not use a single database to which every single service is connecting whenever it needs data. Instead it is recommended to give every service which uses data its own database to store its model. AWS give us a very interesting NoSql database named DynamoDb which purpose is...
Strona głównaBazy danych i XML
Bazy danych i XML 2537 dni, 10 godzin, 5 minut temu 27 pokaż kod licznika zwiń
Podobne artykuły:
- Geospatial Indexes in MongoDB
- CI/CD pipeline z użyciem Kubernetesa, AWS, Azure i .NET Core – stawianie klastra na AWS
- AWS goes after Microsoft’s SQL Server with Babelfish for Aurora PostgreSQL – TechCrunch
- RavenDB (cz. 2) - podstawowe operacje na dokumentach
- Modeling version and temporary state in noSQL databases – IndexOutOfRange
- Serverless - Publiczni Dostawcy FaaS - Jakub Gutkowski
- Log data using Serilog, Elasticsearch and Kibana | mpustelak.com
- Diagram Driven Cloud Infrastructure with Cloud Maker - Łukasz Gąsior
- DevReview #2 O NoSQL z Rafałem Kaszczukiem - Forever F[r]ame
- How to choose the partition key in CosmosDB – IndexOutOfRange
- AWS CloudSearch - clear domain using PowerShell | mpustelak.com