Note that it's prospective, not perspective.
I'm reading a blog post and found below paragraph.
It is impossible to resist the urge of exploring in-memory OLTP Engine (code name Hekaton) released as part of SQL Server 2014. This technology can provide you huge performance boost, assuming, of course, that you can live within surface area limitations. Nevertheless, internal implementation of in-memory OLTP is fascinating. Almost everything is done differently than what you get used to with SQL Server Storage Engine. To put things into prospective, I seriously considered to name this post as “Concurrency – upside down”.
There are two places that I can't fully understood.
- that you can live within surface area limitations
- To put things into prospective
I've looked up those corresponding words in dictionary but still have difficulty in understanding them. Can anyone help me on it? Great thanks.
There are some technical terms in the paragraph and you may not understand. Just ignore them and focus on the general parts.