Live data from Hacker News

AWS Database Migration Service

aws.amazon.com

31–40 of 67 posts

Re: AWS Database Migration Service

#31
post #26

Earlier quoted context omitted.

... with automatically managed updates, backups, monitoring, auto-scaling, auto-replication ... The managed services are a huge part of the lock-in with AWS services, because even though they generally cost more than the competitors, they can often come out equal after accounting for those aggregate hours lost to doing those things.

That's what you call "paying for a service." Lock-In is an entirely different matter.

[deleted]

Re: AWS Database Migration Service

#32
post #15

What are my chances of a relatively successful SQL Server migration with several hundred tables and complex views to PostgreSQL using their migration tool?

Postgres and SQL Server have different concurrency semantics, unlikely that you won't have subtle bugs unless your updates are very straightforward.

Re: AWS Database Migration Service

#33
post #30

Earlier quoted context omitted.

That's what you call "paying for a service." Lock-In is an entirely different matter.

Lock-in happens when migrating would be expensive, too. And leaving a managed service like this could introduce substantial cost.

When the vendor lets you export your data in a form that you can easily import into your own copy of the exact same software, I fail to see how that is "lock-in". If the vendor increase the cost of the service or changes other terms in a way that's unfavorable to you, you can easily leave, that's the opposite of lock-in.

You can't really accuse a vendor of lock in just because his product is priced lower than it would cost you to do it yourself.

Re: AWS Database Migration Service

#34
post #8

The truly interesting thing to me about this product is the pricing. Competitors in this space sell software starting at ~$5,000 all the way up into 5, and I presume 6 figures. AWS is giving away their software and only charging for the hardware to run this migration software on. The catch is that you need to be migrating to AWS resources which you are paying for. I'm sure this tool will have less features than the m…

You can migrate in our out of AWS, but one or both of your endpoints needs to be on AWS.

I wonder if you could realistically do a two stage migration, X -> Amazon -> Y

Re: AWS Database Migration Service

#35
One feature that I wish was supported in RDS is to migrate from a MySQL engine to Aurora engine without having to create new database instance at all. It looks like Amazon DMS makes this process easier, but since Aurora is fully compatible with MySQL, I don't see why I have to create a new database instance and point my application to talk to the new server when Amazon DMS could do this behind the scenes on the one I already have.

Or am I allowed to set the source and target databases to be the one and the same?

Re: AWS Database Migration Service

#37
post #30

Earlier quoted context omitted.

Lock-in happens when migrating would be expensive, too. And leaving a managed service like this could introduce substantial cost.

When the vendor lets you export your data in a form that you can easily import into your own copy of the exact same software, I fail to see how that is "lock-in". If the vendor increase the cost of the service or changes other terms in a way that's unfavorable to you, you can easily leave, that's the opposite of lock-in. You can't really accuse a vendor of lock in just because his product is priced lower than it woul…

I think that's a very rigid definition of "lock-in" that implies it must be done with some anti-competitive malice. That's not how I've encountered the term in my past, so I'm welcome to other interpretations.

Per (not authoritative, obviously) wiki:

"In economics, vendor lock-in, also known as proprietary lock-in or customer lock-in, makes a customer dependent on a vendor for products and services, unable to use another vendor without substantial switching costs."

I agree with this. It shouldn't require that the service is purposefully preventing you from changing; lock-in can occur because a service offers advantages that prevent changing by virtue of some other cost.

Re: AWS Database Migration Service

#38

Hearing a few mixed things and the page doesn't make it clear so can someone clear it up for me, please; if you wanted to, could you migrate _away_ from AWS using this service?

Yes, you could migrate away. As long as either the source or the target is within AWS, you can use this.

Re: AWS Database Migration Service

#39

One feature that I wish was supported in RDS is to migrate from a MySQL engine to Aurora engine without having to create new database instance at all. It looks like Amazon DMS makes this process easier, but since Aurora is fully compatible with MySQL, I don't see why I have to create a new database instance and point my application to talk to the new server when Amazon DMS could do this behind the scenes on the one I…

You can snapshot your RDS database and restore it as an Aurora DB. Only caveat is it has to be MySQL 5.6.

http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Aurora...

Re: AWS Database Migration Service

#40
post #37

Earlier quoted context omitted.

When the vendor lets you export your data in a form that you can easily import into your own copy of the exact same software, I fail to see how that is "lock-in". If the vendor increase the cost of the service or changes other terms in a way that's unfavorable to you, you can easily leave, that's the opposite of lock-in. You can't really accuse a vendor of lock in just because his product is priced lower than it woul…

I think that's a very rigid definition of "lock-in" that implies it must be done with some anti-competitive malice. That's not how I've encountered the term in my past, so I'm welcome to other interpretations. Per (not authoritative, obviously) wiki: "In economics, vendor lock-in, also known as proprietary lock-in or customer lock-in, makes a customer dependent on a vendor for products and services, unable to use ano…

"lock-in" implies some sort of lock. "I don't won't to leave because the service saves me so much money" is not a lock, you can leave, you just choose not to because it's better for you to stay. And if the vendor increases his price you can just take your data and go - your same application will run on another vendor's hosted MySQL instance.

If I say I'll pay you $1 if you sit in my office for an hour, you can't say that you were "locked in" by me, if Mary offers you $2 to sit in her office, you can walk over to her office and get more money.

Post reply on HN