Comments on: Big Data at SoftLayer: MongoDB http://blog.softlayer.com/2012/big-data-at-softlayer-mongodb/ A Behind the Scenes Look at the Best Hosting Provider in the World Mon, 20 May 2013 22:26:24 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: Kevin Hazard http://blog.softlayer.com/2012/big-data-at-softlayer-mongodb/comment-page-1/#comment-48199 Kevin Hazard Mon, 20 May 2013 22:26:24 +0000 http://blog.softlayer.com/?p=9955#comment-48199 I'd be happy to get you answers, Greg. Can you explain your question a little more? This post announced the launch of an on-demand MongoDB big data solution at SoftLayer, so it's unclear how your question about IPv4 addresses is related. As far as this product is concerned, each of the servers in the MongoDB environment have to communicate with each other on the back end, but that communication doesn't need happen via a public IPv4 address ... Because the solution was created to streamline the provisioning process of the infrastructure, you don't have to hassle with configuring the communication between servers. With the dwindling pool of IPv4 addresses available worldwide, SoftLayer follows regional Internet registries' guidelines when it comes to provisioning our IPv4 address pool to new customers/servers. Because IPv4 addresses will be exhausted eventually, every server you order in a SoftLayer data center is IPv6-capable ... As IPv6 adoption grows and users begin accessing the Internet from IPv6 addresses, it's important to be able to run a dual-stack environment to provide a consistent experience for all of your customers and potential customers. If those responses don't answer the questions you were asking, please reply again here to provide a little more detail. Thanks! I’d be happy to get you answers, Greg. Can you explain your question a little more? This post announced the launch of an on-demand MongoDB big data solution at SoftLayer, so it’s unclear how your question about IPv4 addresses is related.

As far as this product is concerned, each of the servers in the MongoDB environment have to communicate with each other on the back end, but that communication doesn’t need happen via a public IPv4 address … Because the solution was created to streamline the provisioning process of the infrastructure, you don’t have to hassle with configuring the communication between servers.

With the dwindling pool of IPv4 addresses available worldwide, SoftLayer follows regional Internet registries’ guidelines when it comes to provisioning our IPv4 address pool to new customers/servers. Because IPv4 addresses will be exhausted eventually, every server you order in a SoftLayer data center is IPv6-capable … As IPv6 adoption grows and users begin accessing the Internet from IPv6 addresses, it’s important to be able to run a dual-stack environment to provide a consistent experience for all of your customers and potential customers.

If those responses don’t answer the questions you were asking, please reply again here to provide a little more detail. Thanks!

]]> By: Greg Nachtwey http://blog.softlayer.com/2012/big-data-at-softlayer-mongodb/comment-page-1/#comment-48188 Greg Nachtwey Mon, 20 May 2013 16:32:34 +0000 http://blog.softlayer.com/?p=9955#comment-48188 How does this affect consumption of IPv4 addresses? What does Softlayer do to help my customers get ubiquitious access without these addresses? How does this affect consumption of IPv4 addresses? What does Softlayer do to help my customers get ubiquitious access without these addresses?

]]> By: MongoDB: Architectural Best Practices – SoftLayer Blog http://blog.softlayer.com/2012/big-data-at-softlayer-mongodb/comment-page-1/#comment-45343 MongoDB: Architectural Best Practices – SoftLayer Blog Thu, 06 Dec 2012 21:45:46 +0000 http://blog.softlayer.com/?p=9955#comment-45343 [...] peak MongoDB performance, and the resulting platform is pretty amazing. As Duke mentioned in his blog post, those efforts followed 10Gen’s MongoDB best practices, but what he didn’t mention was [...] [...] peak MongoDB performance, and the resulting platform is pretty amazing. As Duke mentioned in his blog post, those efforts followed 10Gen’s MongoDB best practices, but what he didn’t mention was [...]

]]>