added by Andrés · updated 1y ago
Don't get locked up into avoiding lock-in
- Architecture lock-in : You may also be locked into a specific kind of architecture. For example. when you use Kubernetes extensively, you are likely building small-ish services that expose APIs and can be deployed as containers. If you want to migrate to a serverless architecture, you'll want to change the granularity of your services closer to si
... See morefrom Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Effort : This is the additional work to be done in terms of person-hours. If we opt to deploy in containers on top of Kubernetes in order to reduce cloud provider lock-in, this item would include the effort to learn a new tool, write Docker files, configure Kubernetes, etc.
- Expense : This is the additional cash expense, e.g. for product licenses,
from Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Open source software isn't a magic cure for lock-in.
from Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Legal lock-in : You may be locked into a specific solution for legal reasons, such as compliance. For example, you might not be able to migrate your data to another cloud provider's data center if it's located outside your country. Your software provider's license may also not allow you to move your systems to the cloud even though they'd run perf
... See morefrom Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- For example, many architects favor not being locked into a database vendor or cloud provider. However, how likely is a switch really? Maybe 5%, or even lower? How much will it cost you to bring that switching cost down from let's say $50,000 (for a semi-manual migration) to near zero? Likely a lot more than the $2,500 ($50,000 x 5%) you can expect ... See more
from Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Mental Lock-in : The most subtle, but also the most dangerous type of lock-in is the one that affects your thinking. After working with a certain set of vendors and architectures, you are likely to absorb assumptions into your decision making, which may lead you to reject alternative options. For example, you may reject scale-out architectures as
... See morefrom Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Skills lock-in : As your developers are becoming familiar with a certain type of product or architecture, you'll have skills lock-in: it'll take you time to re-train (or hire) developers for a different product or technology. As skills availability is one of the major constraints in today's IT shops, this type of lock-in is very real. Some niche e
... See morefrom Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- Vendor Lock-in : This is the kind that IT folks generally mean when they mention "lock-in". It describes the difficulty of switching from one vendor to a competitor. For example, if migrating from Siebel CRM to SalesForce CRM or from an IBM DB2 database to an Oracle one will cost you an arm and a leg, you are "locked in". This type of lock-in is c
... See morefrom Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago
- A significant share of architectural energy is spent on reducing or avoiding lock-in. That's a rather noble objective: architecture is meant to give us options and lock-in does the opposite. However, lock-in isn't a simple true-or-false matter: avoiding being locked into one aspect often locks you into another. Also, popular notions, such as open s... See more
from Don't get locked up into avoiding lock-in by Gregor Hohpe
Andrés added 1y ago