Cognizant20-20Insights|May2017COGNIZANT20-20INSIGHTSExecutiveSummaryRapiddigitizationiscausingtectonicshiftsincustomerexpectationsacrossindustries.
Manyarestrugglingtoadapttothisacceleratedchange.
Asaresult,manybusinessesareaggressivelypushingITtocutdeliverytime,reducecostandimprovequality–allsimultaneously.
Microservicesarchitecture(MSA)hasemergedasonewaytoaddressthesechallenges.
MSAdescribesanewwayofdesigningsoftwareapplicationsassuitesofsmall,loosely-coupledindependentservices.
Whilethereisnoprecisedefinitionofthisarchitecturalstyle,thesearchitecturesencompasscertaincommoncharacteristicsaroundorganization,businesscapability,automateddeployment,intelligentserviceendpoints,anddecentralizedcontroloflanguagesanddata.
Liketheirpredecessors,theybringtheirownsetofuniquechallengesthatshouldbeaddressedupfronttopreventthearchitecturefromturningintoatangledmeshofpoint-to-pointcommunicationpaths.
ThiswhitepaperdescribesanapproachtomicroservicesdesignanddevelopmentthatisAcceleratingMicroservicesDesignandDevelopmentToproactivelydealwithchangingbusinessrequirementsinsideandoutsidetheenterprise,ITorganizationsmustembracemoremodularandextensiblesoftwaredevelopmentanddeploymentmethodsbuiltonasolidmicroservicesreferencearchitecture.
2CognizantSolutionsOverviewCognizant20-20InsightsbasedonadoptionofRESTfulservicesdesignbestpractices.
1Ratherthanconformingtoachecklistofdesignanddevelopmentguidelinesandbestpracticesthatencompassourcollectiveknowledgeoftherightwaysofdevelopingmicroservices,werecommendatool-basedapproachthatgeneratescodecompliantwithmicroservicesbestpracticesandthechosentechnologystack.
Webelievethatgiventheirdistributednatureandmyriadmovingparts,microservicescaneasilyturnintoanimplementationnightmare,unlesstheirdesignandprocessesareenforcedandvalidatedonanongoingbasisusingbest-in-classsoftwareengineeringtools.
ThispaperoffersacomprehensivemicroservicesdesignanddevelopmenttechniquethatnotonlyleveragesrapidlyevolvingbestpracticesbutalsosupportsandenforcesthemusingadevelopmentworkbenchthatwecallCognizantCOSMOS.
Itbuildsonourthinkingsharedinpreviousworksonthetopic,"OvercomingOngoingDigitalTransformationalChallenges"and"TheSevenWavesofChangeThatWillPow-er,orCrush,YourDigitalBusiness.
"DEFININGMICROSERVICESARCHITECTUREAmicroservicesarchitectureisanarchitecturalstylefordevelopingsoftwareapplicationsasasuiteofsmall,autonomousservicesthatworktogetherrunninginitsownprocessandthatcommunicatewithotherservicesusingalightweightcommunicationprotocol.
ThetwoprotocolscommonlyusedareHTTPrequest-responseandlightweightmessaging.
Microservicesarchitecturalstyles2arebestunderstoodbycomparingthemtotraditionalmono-lithicarchitecturalstyles–astyleofapplicationdevelopmentwhereanentireapplicationisdeployedandscaledasasingleunit.
Inmonoliths,businesslogicispackagedinasinglebundleandrunasasingleprocess.
Theseapplicationsareusuallyscaledbyrunningmultipleinstanceshorizontally.
Figure1depictsMSA'sarchitecturalimplicationsincom-parisontomonoliths.
LargerServiceCountFast-ChangingSystemLandscapeRemoteServiceCommunicationLargerAttackSurfaceFrequentServiceFailuresAlargernumberofindependentlydeployedservicesincreasesoperationalcomplexity.
Thisshiftscomplexityfromtheapplicationdeveloperstotheoperationsteam.
Thesystemlandscapeisverydynamic,withservicesredeployed,replaced,deprecatedandspawnedonacontinuousbasis.
Modularitylimitstheprivilegesanattackergetsinasingleattack.
Butitalsoincreasestheattacksurface,asmoreservicesareexposedtotheexternalworld.
Higher-servicemodularityandremotecallsincreasetheriskoffailureswhilereducingthefailurecomplexityandresolutiontime.
Servicescommunicateremotelywithoneanother.
Remotecallsimpactserviceperformanceandincreasechattiness.
Microservices:ArchitecturalImplicationsFigure12AcceleratingMicroservicesDesignandDevelopment|3MICROSERVICESARCHITECTUREImplementationChallengesAsITorganizationsmigratetoamicroservicesarchitecture,theytypicallycontendwithanumberofchallenges,mostofwhicharenotapparentinthemonolithicworld.
Asaresult,ITorganizationsneedaprovenmitigationstrategyandareferencearchitectureconsistingofcomponentsthatwebelieveareessentialforimplementingamicroservicesarchitecturefromadesign,deliveryandoperationalperspective.
ManyofthechallengesariseoutoftheverynatureoftheMSAparadigm.
Microservicesusedistributiontoimprovemodularity.
Butdistributedsoftwarehasthefollowinginherentchallenges:Performance:Remotecallsareslowercomparedtoin-processfunctioncalls.
Whilewemaylimitthenumberofremotecalls,collaboratingservicesneedtobecalledatleastonceandinmanycasesasachainofinvocations.
Fromanoperationalstandpoint,amicroservicesimplementationmusthavecomponentsformonitoringserviceperformanceandfortracingtheservice-callchainacrossprocessesandhosts.
Reliability:Remotecallshaveahigherlikelihoodoffailurethanin-processcalls.
Alargenumberofmicroservicesthusmeansmorepotentialfailurepoints.
Healthmonitoringofmicroservicesandtheirhostsarekeyforensuringsystemreliability.
Verificationthatallservicesareupandrunningiscritical.
Componentsformonitoringtheservicehealthandusagecharacteristicsensureaconstantwatchonservicelivenessbycollectingrun-timestatisticsandcreateaconsolidatedpictureofservicehealth.
Besidesservicehealth,componentstomonitorthehealthofthevirtualmachinesarealsoanessentialpartofthereferencearchitecture.
Fordebugging,acomponentforcentralizedloggingofalltheservicesisneeded;thiscanstorelogdatainacentralrepositorywithsearchanddashboardcapabilities.
Resiliency:Eachmicroservicesimplementationshouldnotonlybedesignedforfailuresbutshouldhavebuilt-infallbackmechanismstodegradegracefullywithminimumimpacttotheserviceinvocationchain.
PatternslikeCircuitBreaker3orBulkhead4shouldbeusedtodesignservicestoavoidsuchcascadingfailures.
MitigationStrategies&ReferenceArchitectureAsFigure2(nextpage)shows,amicroservicesreferencearchitecturemusthavecomponentsthataddressissuesthatariseduetoitsdynamicanddistributednature.
Servicediscovery:Trackingmicroservicesendpointsinarapidlychangingsystemlandscapeisacomplexyetnecessarytask.
Suchrapidmicroservicesconfigurationchangesarehardtomanagemanually.
Instead,ITorganizationsneedserviceregistrationandEachmicroservicesimplementationshouldnotonlybedesignedforfailuresbutshouldhavebuilt-infallbackmechanismstodegradegracefullywithminimumimpacttotheserviceinvocationchain.
4discoveryfunctionalitythatenablesmicroservicestoself-registertoacentralserviceregistryonstartup.
ServiceconsumersusethediscoveryAPItolocatetherequestedmicroservicefromtheserviceregistry.
Additionalloadbalancingcomponentscandeterminewhichinstanceofthemicroservicetoroutetherequestto,assumingmultipleinstancesaredeployedfortherequestedservice.
Configurationmanagement:Microservicesarchitectureswiththeirlargenumberofdeployedservicesmakeconfigurationmanagementtediousanderror-prone.
Localfile-basedconfigurationsareineffective.
Instead,acentralizedconfigurationmanagerisanecessity.
Inaddition,theconfigurationmanagershouldprovideAPIsthatthemicroservicescanquerytofetchconfigurationinformation.
Serviceaccessandrouting:Atypicalenterprisesystemlandscapewillcontainmanymicroservices.
Somewillbeexposedexternallyoverpublicnetworks,whileotherswillbeforinternalconsumption.
Allservices,internalandexternal,areexposedthroughtheirrespective(mostlyRESTful)APImodels.
Whilethisunifiedapproachtowrappingallbusinessfunctionalitiesasservicessimplifiesaccess,itdemandsadditionalinfrastructureforaccessmanagement.
Toexposemicroservicesexternallyandtopreventunauthorizedaccess,ITorganizationsneedanAPIgatewaythroughwhichallexternaltrafficisrouted.
Aroutingservice,whichactsasanentrypointtothemicroservicesenvironment,RESILIENCYDASHBOARDLOGANALYSISDASHBOARDSERVICEMONITORINGDASHBOARDPERFORMANCE&TRACINGDASHBOARDMONITORINGIDENTITYMICROSERVICESCONTAINER1EXECUTIONFRAMEWORKINTEGRATIONFRAMEWORKCLIENTLIBRARIESMICROSERVICESCONTAINER2EXECUTIONFRAMEWORKINTEGRATIONFRAMEWORKCLIENTLIBRARIESMICROSERVICESCONTAINERnEXECUTIONFRAMEWORKINTEGRATIONFRAMEWORKCLIENTLIBRARIESDISCOVERYSERVICECONFIGURATIONSERVICEADMINCONSOLEAPISTOREAPIMANAGERAPIGATEWAYROUTINGSERVICEDEPLOYMENTENVIRONMENTDEVELOPERWORKBENCHCONTINUOUSINTEGRATION/DELIVERYPIPELINEMicroservicesReferenceArchitectureFigure25mayoftendoubleupastheAPIgateway.
Theroutingserviceusesdynamicroutingandload-balancingcapabilitiestorouteexternalrequeststotheselectedservicebylookingupservicesfromtheserviceregistry.
Inaddition,anedgemanagementportalmayberequiredforadministeringroutingrules.
TodesigntheAPImodel,withitsconstraintsanddesignattributes,adeveloperworkbenchisneededtosupporttheAPImodelingarchetypes.
TheworkbenchshouldhavefeaturestopublishtheAPImodeltoanAPIstorewithsupportforthefullAPIlifecycle.
TheAPImodelalsoneedstobeaccess-controlledusingstate-of-the-artsecuritystandards.
FromanAPIconsumptionperspective,webelievethatacomponentinthemicroservicesreferencearchitectureisneededtosupportthedefinitionofusagepoliciesanditsassociationwithconsumers.
Infrastructureautomation:DevOpsisakeyingredientofamicroservicesreferencearchitecture.
Microservices,bynature,areagileandrapidlymovefromdevelopmenttodeployment.
Continuousintegration(CI)andcontinuousdelivery(CD)automatetestinganddelivery,ensuringthatthesoftwareisworkingasperexpectationeverytime.
(FormoreonCIandCD,readourwhitepaper,"PatternsforSuccess:LessonsLearnedWhenAdoptingEnterpriseDevOps.
"Datastrategy:Oneofthemajorchallengesofmigratingtoamicroservicesarchitectureistoadoptthedatabase-per-servicedesignpattern.
Inmonolithicservicearchitecture,businesstransactionsconvergeonthedatabaselayer,makingitasharedservice.
Thisgoesagainstthenotionofanend-to-endloosely-coupledcomponent,whichisstronglyadvocatedbymicroservicespurists.
Thebestsolutiontomitigatethischallengeistouseaneventuallyconsistentdatabase.
5OURAPPROACHTOMSAEXCELLENCECOSMOSisanopen-standards-basedsolutionformicroservicesdesignanddelivery(seeFigure3)Figure3ModelingAPIsthatpromoteRESTfuldesignbestpracticesGeneratesoperationalgovernancecomponentsSupportsmultipletechnologyoptionsandinteractionPublishesAPImodeltoAPIstoreGeneratesbusinessservicescomponentsGeneratesdeploymentbundlesfordifferentdeploymentenvironmentsCognizantCOSMOS:Aunifiedsolutionfordevelopingmicroservices;generatingmicroservicesgovernancecomponents;modeling,publishingandmanagingthemicroservices;andbuildingrequiredartifactsforcloud-basedandon-premisesdeployment.
Governancecomponentgeneration:Generatescriticalinfrastructureservicecomponentsrequiredforoperationalgovernance–routingservice,discoveryservice,configurationservice,performancemonitoringandmanagementcomponents.
Deploymentoptions:Supportsongoingservicedeploymentsbypackagingthedevelopedartifactsintoexecutable,deployablebundlesappropriateforthedeploymentenvironment(on-premises,IaaS,PaaS).
Businessservicegeneration:Generatesskeletonprojectsforthecoreandcompositebusinessmicroservices.
PeeringintotheCOSMOS61CognizantSolutionsOverviewEachmicroservicesimplementationshouldnotonlybedesignedforfailuresbutshouldhavebuilt-infallbackmechanismstodegradegracefullywithminimumimpacttotheserviceinvocationchain.
whichimplementsthereferencearchitecturedescribedabove.
Italsoprovidesaunifiedworkbenchforthefollowingactivities:Developingmicroservices:Microservicescharacteristicsincludetheorganizationofalogicalblockoffunctionalityaroundaspecificbusinesscapability,programminglanguageagnosticismanddecentralizedcontrolofdata.
Thus,eachmicroservicesprojectwillhaveitsAPIinterfaceandimplementationclasses,itsowndatapersistenceandmanagementmodule,clientlibrariesrequiredtoefficientlycommunicatewithothermicroservicesandtheoperationalgovernanceinfrastructure.
Optionally,itmayalsoincludetheclientclassesrequiredtoconnectwithback-endresources.
Generatingcomponentsforoperationalgovernance:Thereferencearchitecturerecommendsagroupofcriticalinfrastructureservicecomponentsforoperationalgovernance.
Thesemaybebroadlyclassifiedintothefollowing:Aroutingservicethatactsasareverseproxyattheedgeofthemicroservicesnetworkwithsupportfordynamicroutingrules.
Adiscoveryservicethatallowsindividualmicroservices(andothersupportingcomponents)toregisteratstartup,includingclientlibrariestolookupanddiscovertheserviceinstancesfromtheserviceregistry.
Aconfigurationservicethatcentrallystoresandmanagesallconfigurationdataacrossbusinessandinfrastructureservices.
Performancemonitoringandmanagementcomponentsthatmonitorvirtualmachines,supportlogaggregation,visualizationandanalysis,ensureserviceresiliencythroughintelligentroutingandenabledistributedcalltracing.
ModelingandpublishingAPIsforaccessingmicroservices:OurworkbenchprovidesanintuitiveAPIdesignerinterfacetomodelRESTfulAPIsforthemicroservices.
ThemodelingactivitypromotestheadoptionofbestpracticesandthetypicalconstraintsoftheRESTfuldesignpattern.
Itsupportstheuseofvariousmediatypes,includinghypermediaconstructs,inresponses.
ModelingactivityistypicallyfollowedbyautomatedcodegenerationwiththecapabilitytogenerateaRESTfulservicesinterfaceandimplementationclassesusingmultipletechnologyoptions.
Thelibraries7requiredbythemicroservicestoconnectwithothermicroservicesandtoexchangedatawiththeoperationalgovernanceinfrastructureisalsoinjectedintotheskeletalclasses.
Customservicelogicneedstobeaddedtothegeneratedcode.
Somemicroservicesareexposedforinvocationoverthepublicnetwork.
ThereferencearchitecturerecommendsinclusionofinfrastructurecomponentsforAPImanagement.
ThesecomponentstypicallyconsistofanAPImanagertomanage,anAPIstoretohostandanAPIgatewaytoactasasingleentrypointforthepublicAPIs.
WebelievethatAPImanagementinfrastructureformsanintegralpartofthereferencearchitectureformicroservicesimplementation.
Theconvergenceoftheserelatedyetdistincttechnologyparadigmsisacriticalsuccessfactorformicroservicesarchitecture.
COSMOShassupportfordifferentAPImanagementsolutions,bothopen-sourceandcommercial.
Buildinganddeployingtheartifactstocloudoron-premisesinfrastructure:Theworkbenchsupportsservicedeploymentstobothon-premisesinfrastructuresandcloudbypackagingthedevelopedartifacts(compiledcode,configurations,etc.
)intoexecutable,deployablebundles.
COSMOScanalsobeintegratedwithcontinuousdeliveryinfra-structures(CI/CD)wherebyanychangesmadetocomponentsmaytriggertheCI/CDbuildanddeploymentpipelinedirectlyfromtheworkbench.
IMPLEMENTINGMICROSERVICESVIAOPENSOURCEOneofthekeycharacteristicsofamicroservicesarchitectureistechnologydiversityandthesupportforit.
Thereareavarietyoflibrariesandframeworksavailabletodaythatimplementthevariouscomponentsofthereferencearchitectureshownabove.
Thevarietyexistsnotonlyintermsofprogramminglanguages,butalsointermsofthevariouscommunication8patternsbetweenthesecomponents.
Synchronousinteractionbetweenmicroservicesmaynotalwaysbetheoptimumoption.
Theexchangeofdatawithoperationalcomponentsforperformancemonitoringorcalltracing,forinstance,typicallyadoptstheasynchronousmessageexchangepatternthroughanunder-lyingmessagebroker.
COSMOSsupportstheopen-sourceSpringCloudNetflixstackasoneofitstechnologyoptionsforimplementation.
Figure4depictshowcomponentsoftheSpringCloudNetflixstackmaptoourreferencearchitecture.
ComponentsdepictedinFigure4thatdirectlymaptotheSpringCloudNetflix,SpringFrameworkandotherrecommendedopen-standard,open-sourcestacksarerepresentedinbolditalicizedfont.
COSMOScanalsointegratewithcustom-builtandthird-partysolutionsforimplementingcomponentsofthereferencearchitectureasneeded.
SupportforadditionaltechnologyoptionsarebeingcontinuouslyaddedtoCOSMOS.
ApacheCamelandEclipseVert.
xsupportforimplementingamicroservicesarchitectureareintheworksandplannedforreleaseinthenextversion.
HYSTRIXDASHBOARDELKDASHBOARDCONSULDASHBOARDZIPKINDASHBOARDMONITORINGOAUTH2.
0MICROSERVICESCONTAINER1SPRINGREST/JAX-RSAPACHECAMELRIBBON,HYSTRIXMICROSERVICESCONTAINER2SPRINGREST/JAX-RSAPACHECAMELRIBBON,HYSTRIXMICROSERVICESCONTAINERnSPRINGREST/JAX-RSAPACHECAMELRIBBON,HYSTRIXEUREKAARCHAIUSSPRINGBOOTADMINCONSOLEAPISTOREAPIMANAGERAPIGATEWAYZUULDEPLOYMENTENVIRONMENTECLIPSECOSMOSPLUGINCONTINUOUSINTEGRATION/DELIVERYPIPELINESpringingForwardwithMicroservicesFigure4"Oneofthekeycharacteristicsofamicroservicesarchitectureistechnologydiversityandthesupportforit.
"9LOOKINGFORWARDCOSMOSoffersawidevarietyoftechnologyoptionsandcommunicationpatternstoimplementmicroservicesarchitecture.
Itisenvisionedtobeanextensibledevelopmenttoolinwhichsupportfornewerlibraries,frameworksanddeploymentplatformscanbeaddedincrementallythroughplug-insastheymatureandarereadyforproductionuse.
WebelievethatasolutionlikeCOSMOSprovidesanumberofcompellingbenefits,including:Awidearrayoftechnologyoptionsforimplementingdifferentcomponentsofamicroservicesreferencearchitecture.
Auto-generatingtheplumbingcodebasedonthechosentechnologystack,ensuringahighqualityofcodingstandardcomplianceandconsistencyacrossimplementations.
EnforcingacommonstandardforAPImodelingacrossteams,businessunitsandgeographies.
10DipanjanSenguptaChiefArchitect,SoftwareEngineeringandArchitectureLabDipanjanSenguptaisaChiefArchitectwithintheSoftwareEngineeringandArchitectureLabofCognizant'sGlobalTechnologyOffice.
Hehasextensiveexperienceinservice-orientedintegration,integrationofcloud-basedandon-premisesapplications,APImanagementandmicroservices-basedarchitecture.
Dipanjanhasapost-graduatedegreeinengineeringfromIITKanpur.
HecanbereachedatDipanjan.
Sengupta@cognizant.
com.
ABOUTTHEAUTHORSFOOTNOTESHiteshBagchiPrincipalArchitect,SoftwareEngineeringandArchitectureLabHiteshBagchiisaPrincipalArchitectwithintheSoftwareEngineeringandArchitectureLabofCognizant'sGlobalTechnologyOffice.
Hehasextensiveexperienceinservice-orientedarchitecture,APImanagementandmicroservices-basedarchitecture,distributedapplicationdevelopment,streamcomputing,cloudcomputingandbigdata.
HiteshhasaB.
Tech.
degreeinengineeringfromUniversityofCalcutta.
HecanbereachedatHitesh.
Bagchi@cognizant.
com.
PijushKantiGiriArchitect,SoftwareEngineeringandArchitectureLabPijushKantiGiriisanArchitectwithintheSoftwareEngineeringandArchitectureLabofCognizant'sGlobalTechnologyOffice.
HehasextensiveexperienceinEclipseplug-inarchitectureanddevelopingEclipseRCPapplications,APImanagementandmicroservices-basedarchitecture.
PijushhasaB.
Tech.
degreeincomputersciencefromUniversityofKalyani.
HecanbereachedatPijushkanti.
Giri@cognizant.
com.
1http://www.
drdobbs.
com/web-development/restful-web-services-a-tutorial/240169069.
2JamesLewisandMartinFowler,"Microservices,"http://martinfowler.
com/articles/microservices.
html.
3MartinFowler,"CircuitBreaker,"http://martinfowler.
com/bliki/CircuitBreaker.
html.
4MichaelT.
Nygard,"ReleaseIt!
DesignandDeployProduction-ReadySoftware,"https://pragprog.
com/book/mnee/release-it.
5Vogels,W,"ScalableWebServices:EventuallyConsistent,"ACMQueue,vol.
6,no.
6,pp.
14-16,October2009.
ABOUTCOGNIZANTCognizant(NASDAQ-100:CTSH)isoneoftheworld'sleadingprofessionalservicescompanies,transformingclients'business,operatingandtechnologymodelsforthedigitalera.
Ouruniqueindustry-based,consultativeapproachhelpsclientsenvision,buildandrunmoreinnovativeandefficientbusinesses.
HeadquarteredintheU.
S.
,Cognizantisranked230ontheFortune500andisconsistentlylistedamongthemostadmiredcompaniesintheworld.
LearnhowCognizanthelpsclientsleadwithdigitalatwww.
cognizant.
comorfollowus@Cognizant.
WorldHeadquarters500FrankW.
BurrBlvd.
Teaneck,NJ07666USAPhone:+12018010233Fax:+12018010243TollFree:+18889373277EuropeanHeadquarters1KingdomStreetPaddingtonCentralLondonW26BDEnglandPhone:+44(0)2072977600Fax:+44(0)2071210102IndiaOperationsHeadquarters#5/535OldMahabalipuramRoadOkkiyamPettai,ThoraipakkamChennai,600096IndiaPhone:+91(0)4442096000Fax:+91(0)4442096060Copyright2017,Cognizant.
Allrightsreserved.
Nopartofthisdocumentmaybereproduced,storedinaretrievalsystem,transmittedinanyformorbyanymeans,electronic,mechanical,photocopying,recording,orotherwise,withouttheexpresswrittenpermissionfromCognizant.
Theinformationcontainedhereinissubjecttochangewithoutnotice.
Allothertrademarksmentionedhereinarethepropertyoftheirrespectiveowners.
TLCodex2533
修罗云怎么样?修罗云是一家国内老牌商家,修罗云商家以销售NAT机器起家,国内的中转机相当不错,给的带宽都非常高,此前推荐的也都是国内NAT VPS机器。今天,云服务器网(www.yuntue.com)小编主要介绍一下修罗云的香港云服务器,适合建站,香港沙田cn2云服务器,2核2G,5M带宽仅70元/月起,同时香港香港大带宽NAT VPS低至50元/月起,性价比不错,可以尝试一下!点击进入:修罗云官...
最近看到群里的不少网友在搭建大数据内容网站,内容量有百万篇幅,包括图片可能有超过50GB,如果一台服务器有需要多个站点的话,那肯定默认的服务器50GB存储空间是不够用的。如果单独在购买数据盘会成本提高不少。这里我们看到腾讯云促销活动中有2款带大数据盘的套餐还是比较实惠的,一台是400GB数据盘,一台是800GB数据盘,适合他们的大数据网站。 直达链接 - 腾讯云 大数据盘套餐服务器这里我们看到当前...
易探云怎么样?易探云最早是主攻香港云服务器的品牌商家,由于之前香港云服务器性价比高、稳定性不错获得了不少用户的支持。易探云推出大量香港云服务器,采用BGP、CN2线路,机房有香港九龙、香港新界、香港沙田、香港葵湾等,香港1核1G低至18元/月,183.60元/年,老站长建站推荐香港2核4G5M+10G数据盘仅799元/年,性价比超强,关键是延迟全球为50ms左右,适合国内境外外贸行业网站等,如果需...
springcloud为你推荐
桌面背景图片淡雅电脑自带的桌面背景图片原来合适现在不合适了怎么办法兰绒和珊瑚绒哪个好珊瑚绒和法兰绒哪个暖和录音软件哪个好录音软件哪个好用又简单宝来和朗逸哪个好大众朗逸好还是宝来好等额本息等额本金哪个好等额本金和等额本息的区别哪个好手机炒股软件哪个好什么手机炒股软件好用,你们都用哪个dnf魔枪士转职哪个好dnf平民魔枪士转什么好google广告申请怎样才能申请google广告willyunlee最近开了007系列的第20部电影《择日再死》,看不懂剧情,不知说什么。谁能说给我听,谢谢。首选dns服务器地址首选DNS服务器地址是什么东西
视频空间租用 godaddy域名解析 com域名抢注 国外永久服务器 星星海 winhost tier 主机屋免费空间 轻量 三拼域名 qq云端 linux使用教程 彩虹云 免费的asp空间 新加坡空间 德讯 永久免费空间 测速电信 阿里云邮箱申请 湖南铁通 更多