An Architect's vision

Multitenant Database Containers (MDC) Multiple Components One System (MCOS) All the tenant DB sharing the same system HANA revision  Independent HANA revision of each HANA instance No additional SAP HANA License Separate SAP HANA License No additional hypervisor virtualization license and hardware independent No additional hypervisor virtualization license and hardware independent No additional machine for hardware/vm management console No additional machine for hardware/vm management console No support on storage snap shot backup Support on storage snap shot backup Shared SAP HANA Binaries - Yes Shared SAP HANA Binaries - No 1 Linux license 1 Linux license Support > 4 socket hardware Support > 4 socket hardware Support > 1TB memory Support > 1TB memory Tenant DB only can restore to tenant DB No dependency of tenant DB backup/re

The following is a high-level summary of the differences between NAT instances and NAT gateways. Attribute NAT gateway NAT instance Availability Highly available. NAT gateways in each Availability Zone are implemented with redundancy. Create a NAT gateway in each Availability Zone to ensure zone-independent architecture. Use a script to manage failover between instances. Bandwidth Supports bursts of up to 10Gbps. Depends on the bandwidth of the instance type. Maintenance Managed by AWS.You do not need to perform any maintenance. Managed by you, for example, by installing software updates or operating system patches on the instance. Performance Software is optimized for handling NAT traffic. A generic Amazon Linux AMI that's configured to perform NAT. Cost Charged depending on the number of NAT gateways you

Heroku is a platform for building and deploying web apps. A cloud application platform. Building on Heroku enables clients to develop and host all types of application. The platform is owned by Salesforce. By using Heroku, developers spend their time on their application code. They don’t need to worry about managing servers or deployment. Or about ongoing operations, or scaling.

To create a VPC peering connection with another VPC, you need to be aware of the following limitations and rules: You cannot create a VPC peering connection between VPCs that have matching or overlapping CIDR blocks. You cannot create a VPC peering connection between VPCs in different regions. You have a limit on the number active and pending VPC peering connections that you can have per VPC. For more information, see  Amazon VPC Limits  in the  Amazon VPC User Guide . VPC peering does not support transitive peering relationships; in a VPC peering connection, your VPC does not have access to any other VPCs that the peer VPC may be peered with. This includes VPC peering connections that are established entirely within your own AWS account. For more information about unsupported peering relationships, see  Invalid VPC Peering Connection Configurations . For examples of supported peering relationships, see  VPC Peering Scenarios . You cannot have more than one VPC pe

Oracle Database Standard Edition 2 (SE2) streamlines the existing Standard Edition (SE) and Standard Edition One (SE1) offerings into a single offering going forward that continues to provide an affordable enterprise class database for SMB customers. When SE was first introduced single and dual core CPUs were the norm. Today, we have 18 core CPUs and 32 core CPUs are around the corner. Not to mention that per core performance has