Reddit Comments Summary on "AWS Cloud Cost"

AWS Cloud Cost and Replacing Technologies

• Some users question whether rewriting COBOL to Java for AWS is cost-effective given recent outages and log4j issues.
• Mainframes and COBOL are still stable and secure, making it questionable to replace them with newer technologies easily.
• Users advise against rewriting code from Java to Go solely for cost reduction, highlighting that the initial rewrite cost might outweigh potential savings.
• AWS Mainframe alternatives are deemed unlikely to replace established systems due to reliability issues and costs.
• Concern is expressed over AWS understanding certain aviation and banking needs and maintenance requirements.
• The idea of moving from on-premise to cloud-based solutions is discussed, emphasizing calculating costs and trade-offs.
• Some users share their experience with moving from on-premise to AWS, highlighting aspects like cost savings, scaling, and ease of management.

Database Usage Suggestions

• Postgres and MySQL are recommended for on-premise database usage, considering factors like data volume and use cases.
• Users suggest evaluating different database tools, scalability needs, and cost-effective options for managing and backing up data.
• The importance of considering database use cases, integration with other tools, and storage configurations is highlighted.
• Various options like SQL and NoSQL databases are mentioned, emphasizing factors like data retention, scalability, and usage scenarios.
• Different database tools from AWS, Google, and Microsoft are suggested, considering their specific features, costs, and ease of use.

Cloud and Infrastructure Cost Comparison

• Users discuss the cost-effectiveness and complexity of adopting cloud-based solutions like AWS for event streaming and database management.
• Local storage instance types on AWS are compared for their costs and storage capacity.
• Recommendations are given to assess the need for retention and durability and explore cheaper solutions that fulfill the required functionalities.
• Users point out the benefits of cloud services for scalability, flexibility, durability, and quick resource provisioning.

Kafka and Data Streaming Infrastructure

• The cost and complexity of running Kafka on AWS infrastructure are examined, with users debating the alternatives and managed solutions like MSK, Azure Event Hub, Confluent, and Aiven.
• The potential for cost savings and trade-offs in utilizing Kafka for data streaming is explored, considering factors like data ingestion, retention period, and scalability.
• Managing a large Kafka cluster on-premise is discussed, showcasing the strategies, costs, and challenges involved in maintaining such infrastructures.
• Data ingestion speed and the associated costs of processing high data volumes are evaluated, along with the need for durability and resilience in data storage solutions.

Overall, the discussion provides insights into the cost implications of adopting cloud services like AWS, the importance of considering specific use cases and data retention needs, and the potential trade-offs between cloud-based infrastructures and on-premise solutions.